Below Average

Score Report

www.eset.com

Scanned on June 18, 2026

Unknown
jQuery
Swiper
Vite
Company:ESET, spol. s r.o.· NACE 6209
NIS2: important entity · Digital Providers
Risk:5/100low
Credit:A+
VAT registered
Top 20% in sector
Full company profile →
Last scanned: June 18, 2026

NIS2: important entity — Digital Providers

NIS2 readiness: 3/7 · 43%

Your shop falls under NIS2. The directive requires documented technical measures. These 5 shop-side signals are what we can verify externally:

✓Valid SSL/TLS certificateNIS2 Art. 21(2)(c)
—DMARC email authentication (anti-phishing)NIS2 Art. 21(2)(g)
!Incident reporting contact (security.txt)NIS2 Art. 21(2)(b), Art. 23
✗Content Security Policy (XSS protection)NIS2 Art. 21(2)(c)
!HSTS (forced HTTPS)NIS2 Art. 21(2)(c)
✓Vulnerability management (no known CVEs)NIS2 Art. 21(2)(e), 21(2)(g)
✓Data protection (cookie consent + privacy policy)NIS2 Art. 21(2)(j)
Check full NIS2 compliance → Legal basis: NIS2 Art. 21 · SK 366/2024
Action plan

Fix these 3 things first

Sorted by score impact — each fix moves your overall grade up.

+15potential gain

Performance

Weight: 25% · 8 passed · 3 warnings · 4 failed

What we found: 5918ms (good: <200ms)

Why it matters: TBT over 600ms means your page is unresponsive for over half a second. Users who can't interact within 100ms perceive the site as broken. This kills conversions.

How to fix: Critical: audit all JavaScript. 1) Remove unused plugins/modules, 2) Defer analytics and chat widgets, 3) Code-split large bundles, 4) Move heavy computation to web workers.
Request quote for speed audit

What we found: 5.8 MB, 161 requests — too heavy!

Why it matters: Pages over 3 MB take 12+ seconds on 3G. The average e-commerce page is 2.2 MB — you're well above that. Amazon found every 100ms of latency costs 1% of sales.

How to fix: Critical: your page is over 3 MB. 1) Convert all images to WebP/AVIF, 2) Lazy load everything below the fold, 3) Remove unused plugins, 4) Combine and minify CSS/JS, 5) Enable brotli compression.
Get Performance Optimization →

What we found: 1305 KB wasted on unused code!

Why it matters: Over 200 KB of unused code significantly slows parsing and execution. This is one of the easiest performance wins — removing dead code requires no trade-offs.

Note: This check uses heuristic detection and may produce false positives. Manual verification recommended.

How to fix: You're loading 1305 KB of code that isn't used on this page. 1) Audit plugins and remove unused ones, 2) Use code-splitting for page-specific JS, 3) Run PurgeCSS on your stylesheets.

What we found: Only 18% of 11 scripts optimized — most are render-blocking

Why it matters: 9 render-blocking scripts can add 1-3 seconds to page load. Each synchronous script creates a sequential download-parse-execute chain.

How to fix: Add defer or async to all <script src='...'> tags. Render-blocking scripts are the #1 cause of slow FCP. Defer maintains execution order, async does not.
Get Performance Optimization →

What we found: 3.56s (good: <2.5s) — Core Web Vital

Why it matters: LCP is a Core Web Vital that directly impacts Google rankings. Sites failing LCP are demoted in search results. The #1 cause of slow LCP is unoptimized hero images.

How to fix: Optimize your largest element (usually hero image or product image): preload it with <link rel='preload'>, use WebP/AVIF format, set explicit width/height, and serve from CDN.
Request quote for speed audit

Why it matters: Preconnect saves 100-500ms per third-party origin by establishing connections early. Preload starts downloading critical resources before the browser discovers them in CSS/JS.

How to fix: Add resource hints: <link rel='preconnect' href='https://fonts.googleapis.com'> for third-party origins, <link rel='preload' as='image' href='hero.webp'> for critical resources.
Request quote for speed audit

What we found: 544 KB of inline JavaScript

Why it matters: Large inline scripts cannot be cached separately — they're re-downloaded with every page load. Moving them to external files with defer enables HTTP caching and parallel downloads.

How to fix: Move large inline scripts to external files. Inline JS over 100 KB inflates HTML, prevents caching, and blocks the parser. External files can be cached, compressed, and deferred.
Request quote for security audit

7 issues found in Performance. Room for improvement.

Your store doesn't qualify for the Zulien Score Badge yet. Score 80+ to earn it!

📧 Re-scan reminders

We'll email you monthly when it's time to re-scan and track your improvements.

🚀 Improve your score

Our PrestaShop modules can fix most of these issues automatically.

Free 15-min consultation · No commitment

Share & Export

Ready to improve your score?

Your store is losing customers every day. The issues above are costing you sales.

Fix it yourself

Browse our modules to fix these issues in 2 clicks.

Browse Zulien Modules

Let us fix it for you

Describe your goal and we'll send a quote within 48h — no call needed.

Get a written quote

Reply within 48h · No sales call

This is an automated heuristic estimate, not a professional audit. Findings reflect publicly observable signals at scan time and may include false positives.Learn about our methodologyReport inaccuracyRemove this report
Komplexný audit e-shopu — 50+ kontrol v 7 kategóriách
67/100
Grade D
www.eset.com
ESET, spol. s r.o.
Dátum auditu: June 18, 2026
NACE: 6209
Online report: https://score.zulien.sk/r/eset.com
Vygenerované 29. 7. 2026 11:10:11 · score.zulien.sk · by Zulien

Executive summary

16
Chýb
53
Upozornení
69
OK
140
Spolu kontrol

Skóre po kategóriách

KategóriaSkóreVáhaChybyUpozorneniaOK
Performance55/10025%438
SEO87/10020%1518
Security57/10015%2104
Mobile57/10010%279
AI Readiness63/10010%42114
GDPR84/10010%048
Vulnerability65/10010%338

Kritické zistenia

Total Blocking Time (TBT)· Performance
TBT over 600ms means your page is unresponsive for over half a second. Users who can't interact within 100ms perceive the site as broken. This kills conversions.
Total Page Weight· Performance
Pages over 3 MB take 12+ seconds on 3G. The average e-commerce page is 2.2 MB — you're well above that. Amazon found every 100ms of latency costs 1% of sales.
Unused Code (CSS + JS)· Performance
Over 200 KB of unused code significantly slows parsing and execution. This is one of the easiest performance wins — removing dead code requires no trade-offs.
Script Loading Strategy· Performance
9 render-blocking scripts can add 1-3 seconds to page load. Each synchronous script creates a sequential download-parse-execute chain.
Text-to-HTML Ratio· SEO
Google's Helpful Content Update specifically targets thin content pages. This significantly hurts your rankings.
Content-Security-Policy (CSP)· Security
CSP is the most powerful defense against XSS attacks. Without it, any injected script runs with full privileges. CSP blocks inline script injection, the #1 web attack vector.
Clickjacking Protection· Security
Clickjacking overlays your site in a hidden iframe. Attackers trick users into clicking buttons (like 'Confirm Purchase') without knowing it.
Mobile Performance Score· Mobile
A mobile score below 50 means your store takes 5+ seconds to become usable on a phone. 53% of mobile users abandon sites that take over 3 seconds. You're losing the majority of mobile visitors.
Form Input Labels (WCAG 3.3.2)· Mobile
EAA 2026 (European Accessibility Act) vstupuje do platnosti 28.6.2025. E-shopy nad 10 zamestnancov alebo €2M obrat musia byť WCAG 2.1 AA kompatibilné — chýbajúce labely sú jedna z najčastejších žalovateľných chýb.
llms.txt (AI Site Descriptor)· AI Readiness
llms.txt is the emerging standard for AI-readable site descriptions — like robots.txt was for search engines. Early adopters (Yoast, Cloudflare, Stripe) are already using it. Without it, AI assistants have no guided overview of your store.
Content Accessibility for AI· AI Readiness
AI crawlers see only raw HTML. The LLMClicks audit tool found that JS-dependent pages score 70% lower in AI readiness. Server-rendered content is the #1 prerequisite for AI visibility.
Product Schema Completeness· AI Readiness
No Product schema = invisible to AI shopping. 58% of consumers now use AI for product discovery (Adobe 2025). Without Product schema, your products don't exist in this channel.

Performance

55/100
Váha: 25% · 8 OK · 3 upozornení · 4 chýb · spolu 15
Total Blocking Time (TBT)Zlyhalo
5918ms (good: <200ms)
Prečo je to dôležité: TBT over 600ms means your page is unresponsive for over half a second. Users who can't interact within 100ms perceive the site as broken. This kills conversions.
Ako opraviť: Critical: audit all JavaScript. 1) Remove unused plugins/modules, 2) Defer analytics and chat widgets, 3) Code-split large bundles, 4) Move heavy computation to web workers.
Total Page WeightZlyhalo
5.8 MB, 161 requests — too heavy!
Prečo je to dôležité: Pages over 3 MB take 12+ seconds on 3G. The average e-commerce page is 2.2 MB — you're well above that. Amazon found every 100ms of latency costs 1% of sales.
Ako opraviť: Critical: your page is over 3 MB. 1) Convert all images to WebP/AVIF, 2) Lazy load everything below the fold, 3) Remove unused plugins, 4) Combine and minify CSS/JS, 5) Enable brotli compression.
Unused Code (CSS + JS)Zlyhalo
1305 KB wasted on unused code!
Prečo je to dôležité: Over 200 KB of unused code significantly slows parsing and execution. This is one of the easiest performance wins — removing dead code requires no trade-offs.
Ako opraviť: You're loading 1305 KB of code that isn't used on this page. 1) Audit plugins and remove unused ones, 2) Use code-splitting for page-specific JS, 3) Run PurgeCSS on your stylesheets.
Script Loading StrategyZlyhalo
Only 18% of 11 scripts optimized — most are render-blocking
Prečo je to dôležité: 9 render-blocking scripts can add 1-3 seconds to page load. Each synchronous script creates a sequential download-parse-execute chain.
Ako opraviť: Add defer or async to all <script src='...'> tags. Render-blocking scripts are the #1 cause of slow FCP. Defer maintains execution order, async does not.
Largest Contentful Paint (LCP)Upozornenie
3.56s (good: <2.5s) — Core Web Vital
Prečo je to dôležité: LCP is a Core Web Vital that directly impacts Google rankings. Sites failing LCP are demoted in search results. The #1 cause of slow LCP is unoptimized hero images.
Ako opraviť: Optimize your largest element (usually hero image or product image): preload it with <link rel='preload'>, use WebP/AVIF format, set explicit width/height, and serve from CDN.
Resource Hints (Preload/Preconnect)Upozornenie
Prečo je to dôležité: Preconnect saves 100-500ms per third-party origin by establishing connections early. Preload starts downloading critical resources before the browser discovers them in CSS/JS.
Ako opraviť: Add resource hints: <link rel='preconnect' href='https://fonts.googleapis.com'> for third-party origins, <link rel='preload' as='image' href='hero.webp'> for critical resources.
Inline JavaScript SizeUpozornenie
544 KB of inline JavaScript
Prečo je to dôležité: Large inline scripts cannot be cached separately — they're re-downloaded with every page load. Moving them to external files with defer enables HTTP caching and parallel downloads.
Ako opraviť: Move large inline scripts to external files. Inline JS over 100 KB inflates HTML, prevents caching, and blocks the parser. External files can be cached, compressed, and deferred.
Server Response Time (TTFB)Prešlo
16ms
First Contentful Paint (FCP)Prešlo
1.07s
Cumulative Layout Shift (CLS)Prešlo
0.030 — Core Web Vital ✓
Speed IndexPrešlo
1.97s
Render-blocking ResourcesPrešlo
No render-blocking resources found
Text Compression (gzip/brotli)Prešlo
All text resources properly compressed
Lazy LoadingPrešlo
80% of images use native lazy loading (4/5)
CSS File CountPrešlo
2 CSS file(s) — well consolidated
Kategória 1 / 7 · www.eset.com · Zulien Score

SEO

87/100
Váha: 20% · 18 OK · 5 upozornení · 1 chýb · spolu 24
Text-to-HTML RatioZlyhalo
3% — very thin content (4414 words)
Prečo je to dôležité: Google's Helpful Content Update specifically targets thin content pages. This significantly hurts your rankings.
Ako opraviť: Your page is almost entirely HTML/CSS/JS with very little actual content. Add substantial product descriptions, content blocks, and informational text.
Meta TitleUpozornenie
72 chars (optimal: 30-60)
Prečo je to dôležité: Truncated titles reduce click-through rate by 10-20% according to Moz research.
Ako opraviť: Shorten your title to under 60 characters. Google truncates longer titles with '…' which loses your message.
Twitter/X CardsUpozornenie
Prečo je to dôležité: Twitter Cards make your links stand out in X/Twitter feeds. Without them, shared links appear as plain text URLs.
Ako opraviť: Add <meta name='twitter:card' content='summary_large_image'>, twitter:title, and twitter:image tags.
Image Alt AttributesUpozornenie
Only 60% of 5 images have alt text
Prečo je to dôležité: Missing alt text means zero visibility in Google Image Search (which drives 20%+ of total search traffic for e-commerce).
Ako opraviť: 2 images are missing alt attributes. Add descriptive, keyword-rich alt text to every image.
Image Format OptimizationUpozornenie
0% next-gen formats — 0 JPEG, 4 PNG images
Prečo je to dôležité: Your images are using legacy formats only. Switching to WebP typically reduces page weight by 30-50% — one of the highest-impact performance optimizations.
Ako opraviť: Convert all images to WebP format. Most CMS platforms have plugins for automatic WebP conversion. Use AVIF for even better compression.
Canonical URL ConsistencyUpozornenie
Canonical points to different URL: https://www.eset.com/us/
Prečo je to dôležité: A mismatched canonical tells Google this page is a duplicate of another URL. If unintentional, Google may ignore this page entirely in favor of the canonical target.
Ako opraviť: Your canonical URL doesn't match the current page URL. Ensure the canonical points to the preferred version (with or without trailing slash, www vs non-www). Inconsistent canonicals confuse search engines.
Meta DescriptionPrešlo
152 chars
H1 HeadingPrešlo
"AI-Native Prevention for Tomorrow's Threats"
Content Structure (H2 Headings)Prešlo
3 H2 subheadings found
Open Graph TagsPrešlo
og:title, og:description, og:image
Open Graph Image FormatPrešlo
image/jpeg
Canonical URLPrešlo
https://www.eset.com/us/
Structured Data (JSON-LD)Prešlo
2 block(s): BreadcrumbList, ListItem, Organization, ContactPoint
robots.txtPrešlo
Present, references sitemap
XML SitemapPrešlo
Found with ~214+ URLs
HTML Language AttributePrešlo
lang="en-US"
Hreflang Tags (Multilingual)Prešlo
85 language(s): en-US, sk-SK, cs-CZ, en-CA, fr-CA
Meta Robots TagPrešlo
index,follow
FaviconPrešlo
Favicon detected
Semantic HTML StructurePrešlo
4/6 semantic elements: <nav>, <header>, <footer>, <aside>
Content DepthPrešlo
4414 words — sufficient content
Deep Heading HierarchyPrešlo
H2: 3, H3: 6 — well-structured content
Internal LinkingPrešlo
87 internal links — strong site navigation
Accessibility FundamentalsPrešlo
3/4 a11y signals: 112 ARIA roles, 17 ARIA labels, lang="en-US"
Kategória 2 / 7 · www.eset.com · Zulien Score

Security

57/100
Váha: 15% · 4 OK · 10 upozornení · 2 chýb · spolu 16
Content-Security-Policy (CSP)Zlyhalo
Prečo je to dôležité: CSP is the most powerful defense against XSS attacks. Without it, any injected script runs with full privileges. CSP blocks inline script injection, the #1 web attack vector.
Ako opraviť: Implement a CSP header. Start with: Content-Security-Policy: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: — then gradually tighten.
Clickjacking ProtectionZlyhalo
Prečo je to dôležité: Clickjacking overlays your site in a hidden iframe. Attackers trick users into clicking buttons (like 'Confirm Purchase') without knowing it.
Ako opraviť: Add X-Frame-Options: DENY (or SAMEORIGIN if iframes are needed). Better: use CSP frame-ancestors 'self'.
DNSSECUpozornenie
No DNSKEY records — zone is unsigned
Prečo je to dôležité: Without DNSSEC, attackers controlling intermediate resolvers can forge responses for your domain — sending users to phishing sites with valid HTTPS that match your name. EU national CSIRTs (SK-CERT, NÚKIB) recommend DNSSEC for all in-scope entities.
Ako opraviť: Enable DNSSEC at your DNS host (most modern registrars offer 1-click activation: Cloudflare, Route 53, Google Cloud DNS, web.sk, websupport.sk). Verify via dnsviz.net afterwards.
CAA DNS RecordUpozornenie
No CAA records — any CA can issue certificates for this domain
Prečo je to dôležité: CAA records limit which Certificate Authorities can issue certificates for your domain. Without CAA, a compromised or rogue CA can issue valid certs that browsers will trust — a documented breach pattern (DigiNotar 2011, Symantec 2017).
Ako opraviť: Publish CAA TXT records pinning your CA. For Let's Encrypt: `0 issue "letsencrypt.org"`. For multiple CAs add additional `0 issue "..."` records. Add `0 iodef "mailto:security@yourdomain.tld"` for misissuance reports.
HSTS (Strict-Transport-Security)Upozornenie
missing includeSubDomains
Prečo je to dôležité: Weak HSTS can still allow SSL stripping attacks in the first connection. Full HSTS with preload makes your site HTTPS-only in every browser.
Ako opraviť: Set: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload — then submit to hstspreload.org for browser preloading.
X-Content-Type-OptionsUpozornenie
Prečo je to dôležité: Without nosniff, browsers may execute uploaded files as scripts. An attacker could upload a .jpg that's actually JavaScript and trick the browser into running it.
Ako opraviť: Add header: X-Content-Type-Options: nosniff
Referrer-PolicyUpozornenie
Prečo je to dôležité: Without a referrer policy, browsers send the full URL to third parties. This can leak sensitive data like session tokens in URLs or internal page paths.
Ako opraviť: Add header: Referrer-Policy: strict-origin-when-cross-origin — this is the best balance between functionality and privacy.
Permissions-PolicyUpozornenie
Prečo je to dôležité: Without Permissions-Policy, any third-party script (ads, analytics, chat widgets) can access camera, microphone, and geolocation without your knowledge.
Ako opraviť: Add: Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=() — disable APIs your site doesn't need.
Subresource Integrity (SRI)Upozornenie
Only 0/11 external scripts have integrity hashes
Prečo je to dôležité: Without SRI, if a third-party CDN is compromised, attackers can inject malicious code into your site. The British Airways breach (£20M fine) was exactly this attack vector.
Ako opraviť: Add integrity='sha384-...' and crossorigin='anonymous' attributes to all third-party <script> tags. Use srihash.org to generate hashes.
security.txt (RFC 9116)Upozornenie
Prečo je to dôležité: security.txt lets ethical hackers report vulnerabilities responsibly. Without it, they may disclose publicly or not report at all. Required by ISO 27001 and SOC 2.
Ako opraviť: Create /.well-known/security.txt with Contact, Expires, and Preferred-Languages fields. See securitytxt.org for the generator.
CDN / WAF ProtectionUpozornenie
Prečo je to dôležité: Without a CDN/WAF, your origin server is directly exposed to DDoS attacks, bot traffic, and brute-force attempts. Cloudflare blocks 150+ billion daily threats.
Ako opraviť: Add a CDN/WAF like Cloudflare (free tier), Sucuri, or Fastly. They provide DDoS protection, bot filtering, and SSL management.
Iframe SandboxingUpozornenie
2/2 iframe(s) without sandbox attribute
Prečo je to dôležité: Unsandboxed iframes can access your DOM, run scripts, and navigate the top window. Third-party iframes (ads, widgets) should always be sandboxed to prevent clickjacking and XSS.
Ako opraviť: Add sandbox attribute to all <iframe> elements. Use sandbox='allow-scripts allow-same-origin' for third-party embeds. This restricts iframe capabilities to only what's needed.
SSL/TLS CertificatePrešlo
Valid HTTPS connection established
HTTP → HTTPS RedirectPrešlo
HTTP properly redirects to HTTPS
Cookie Security FlagsPrešlo
No cookies set on initial response
Technology DisclosurePrešlo
Server identity hidden
Kategória 3 / 7 · www.eset.com · Zulien Score

Mobile

57/100
Váha: 10% · 9 OK · 7 upozornení · 2 chýb · spolu 19
Mobile Performance ScoreZlyhalo
45/100 — critically slow
Prečo je to dôležité: A mobile score below 50 means your store takes 5+ seconds to become usable on a phone. 53% of mobile users abandon sites that take over 3 seconds. You're losing the majority of mobile visitors.
Ako opraviť: Your mobile experience is severely degraded. Priority fixes: 1) Reduce JavaScript by 50%+, 2) Convert all images to WebP with responsive sizing, 3) Enable aggressive caching, 4) Use a CDN.
Form Input Labels (WCAG 3.3.2)Zlyhalo
Iba 9/12 inputs má label (75%)
Prečo je to dôležité: EAA 2026 (European Accessibility Act) vstupuje do platnosti 28.6.2025. E-shopy nad 10 zamestnancov alebo €2M obrat musia byť WCAG 2.1 AA kompatibilné — chýbajúce labely sú jedna z najčastejších žalovateľných chýb.
Ako opraviť: 3 input elementov nemá label. Každý input musí mať priradený <label for="id">Text</label> alebo aria-label. Placeholder NIE je label (WCAG 3.3.2). Ak je checkout/registrácia formulár — toto znižuje konverziu a porušuje EN 301 549 (EAA 2026).
Touch Target SizeUpozornenie
Prečo je to dôležité: Small tap targets cause 37% more mis-taps on mobile (Google UX research). In e-commerce, a mis-tap on 'Remove from cart' instead of 'Checkout' directly loses revenue.
Ako opraviť: Ensure ALL interactive elements (buttons, links, form fields) are at least 48×48px with 8px minimum spacing between them. Pay special attention to: navigation menus, filter buttons, product variant selectors, and footer links.
Font Size ReadabilityUpozornenie
Prečo je to dôležité: Text smaller than 16px forces mobile users to pinch-zoom. This breaks the responsive layout and creates a frustrating experience. Users over 40 are especially affected — and they have the highest purchasing power.
Ako opraviť: Set minimum 16px font size for body text. Use relative units (rem/em) instead of px for scalability. Product titles: 18px+, prices: 20px+, CTAs: 16px+ with bold.
PWA FeaturesUpozornenie
Has manifest, missing service worker
Prečo je to dôležité: PWA-enabled stores see 52% higher engagement and 36% higher conversion rates (Google case studies). Users can install the store as an app on their home screen.
Ako opraviť: Add a service worker to enable PWA features. Register a service worker for offline caching and faster repeat visits.
Inline CSS SizeUpozornenie
81 KB of inline CSS
Prečo je to dôležité: Large inline CSS blocks increase initial HTML download and parsing time — especially painful on mobile with limited CPU and slower connections.
Ako opraviť: Extract inline styles to external CSS files. Inline CSS larger than 50 KB increases HTML payload and cannot be cached separately. Keep only critical above-the-fold CSS inline.
Print StylesheetUpozornenie
Order/invoice page without print styles
Prečo je to dôležité: Customers print order confirmations and invoices. Without print styles, they get navigation bars, cookie banners, and broken layouts. This is a common usability complaint for e-commerce.
Ako opraviť: Add @media print CSS rules to hide navigation, ads, and non-essential elements. Ensure order details, prices, and company info are visible when printed.
Fixed Width ElementsUpozornenie
Large fixed-width elements detected — may cause horizontal scroll
Prečo je to dôležité: Fixed-width elements wider than the viewport cause horizontal scrolling on mobile. Google's mobile-friendly test specifically checks for this.
Ako opraviť: Replace fixed pixel widths with max-width: 100% or use relative units (%, vw). Add 'overflow-x: hidden' to body as a safety net.
Express Checkout (Apple Pay + Google Pay)Upozornenie
Prečo je to dôležité: Mobile conversion pri express checkout je +15-25 % oproti klasickej karte. V SK/CZ trend roku 2025+.
Ako opraviť: Pridaj Apple Pay + Google Pay cez Stripe/Adyen/Mollie. Biometric auth = -1 click checkout = vyšší conversion.
Viewport ConfigurationPrešlo
width=device-width, initial-scale=1
Content Fits ViewportPrešlo
No horizontal scrolling needed
Responsive Design TechniquesPrešlo
Flexbox, Media queries detected
Theme ColorPrešlo
theme-color meta tag present
Mobile Navigation (Semantic)Prešlo
<nav> element present — proper navigation landmark
Responsive Images (srcset)Prešlo
6 image(s) use srcset for responsive sizing
Apple Mobile Web AppPrešlo
2/3 Apple mobile meta tags configured
Heading Hierarchy (WCAG 1.3.1)Prešlo
Žiadne preskočené úrovne
Link Text Quality (WCAG 2.4.4)Prešlo
Všetky odkazy majú popisný text
Payment Methods DetectedInfo
Žiadna známa platobná brána nedetekovaná na homepage
Prečo je to dôležité: Viditeľné platobné ikony (Apple Pay, Google Pay, Klarna, Tatra Pay) v headeri/footeri zvyšujú conversion o 5-10 %. Trust signal pred checkoutom.
Ako opraviť: Payment gateway detection scanuje iba homepage. Ak sú platby na /checkout alebo sú načítané JS-om až po interakcii, neuvidíme ich. Zváž pridať platobné ikony do footer-u.
Kategória 4 / 7 · www.eset.com · Zulien Score

AI Readiness

63/100
Váha: 10% · 14 OK · 21 upozornení · 4 chýb · spolu 39
llms.txt (AI Site Descriptor)Zlyhalo
Prečo je to dôležité: llms.txt is the emerging standard for AI-readable site descriptions — like robots.txt was for search engines. Early adopters (Yoast, Cloudflare, Stripe) are already using it. Without it, AI assistants have no guided overview of your store.
Ako opraviť: Create /llms.txt in Markdown format: # Your Store Name > One-line summary of your business and key offerings. Detailed description paragraph. ## Products - [Product Category](URL): Description ## About - [About Us](URL): Company history and values See llmstxt.org for the full specification.
Content Accessibility for AIZlyhalo
Only 4414 words visible in HTML — content may be JS-dependent
Prečo je to dôležité: AI crawlers see only raw HTML. The LLMClicks audit tool found that JS-dependent pages score 70% lower in AI readiness. Server-rendered content is the #1 prerequisite for AI visibility.
Ako opraviť: Your page has very little content in the HTML source. If you're using a JavaScript framework (React, Vue, Angular), implement Server-Side Rendering (SSR) or Static Site Generation (SSG).
Product Schema CompletenessZlyhalo
Prečo je to dôležité: No Product schema = invisible to AI shopping. 58% of consumers now use AI for product discovery (Adobe 2025). Without Product schema, your products don't exist in this channel.
Ako opraviť: Add complete Product JSON-LD schema: name, description, image, sku, brand, offers (price, priceCurrency, availability, seller), aggregateRating, review. This is mandatory for AI-powered commerce.
Content Freshness SignalsZlyhalo
Prečo je to dôležité: No freshness signals = AI assumes your content is stale. ChatGPT and Perplexity both weight recency in their citation algorithms. Competitors who show recent updates will be cited instead of your static pages.
Ako opraviť: Add dateModified and datePublished to your JSON-LD schema, and display a visible 'Last updated' date on the page. Update content quarterly at minimum. AI heavily favors fresh, maintained content.
llms-full.txt (Complete AI Content)Upozornenie
Prečo je to dôležité: llms-full.txt provides AI models with your entire site content in one parseable file. It's the difference between an AI having a brief overview vs. deep knowledge of your products and services.
Ako opraviť: Create /llms-full.txt containing your complete site documentation in a single Markdown file — product catalog summaries, FAQs, policies, brand story. This gives AI models maximum context about your store.
FAQ Schema (Direct AI Answers)Upozornenie
Prečo je to dôležité: FAQ schema provides 30% higher AI citation rates (LLMClicks research). ChatGPT, Perplexity, and Google AI Overviews pull FAQ answers verbatim. It's the fastest way to get your content cited by AI.
Ako opraviť: Add FAQPage schema to every product page and category page. Include 3-5 Q&As per page covering: product specifications, shipping, returns, usage instructions. Format: question (full sentence) + answer (75-150 words).
Site Search Schema (SearchAction)Upozornenie
Prečo je to dôležité: SearchAction enables Google's sitelinks search box and allows AI shopping assistants to search your catalog directly. It's how AI agents find specific products in your store.
Ako opraviť: Add WebSite schema with potentialAction: SearchAction. Define your search URL template so AI assistants and Google can search your store programmatically.
Structured Content (Lists & Tables)Upozornenie
29 lists found — consider adding comparison tables
Prečo je to dôležité: AI models are biased toward extracting data from HTML lists and tables. Perplexity and ChatGPT pull bullet points and table data with much higher accuracy than paragraph text. Structured content = more AI citations.
Ako opraviť: Add comparison tables to your content. Use <ul>/<ol> for feature lists, specifications, and benefits. Use <table> for product comparisons, pricing tiers, and specifications. AI extracts structured content exponentially faster than paragraphs.
Author Expertise Signals (E-E-A-T)Upozornenie
Prečo je to dôležité: AI models weight author expertise heavily. Pages from identified experts get cited 3x more than anonymous content. This is especially important for product guides, reviews, and advice content.
Ako opraviť: For content pages (blog, guides, about): add Article/BlogPosting schema with author property linking to Person schema. Include the author's jobTitle, credentials, and social profiles.
Reviews & Ratings SchemaUpozornenie
Prečo je to dôležité: Products with star ratings appear in Google's rich results and get 35% more clicks. AI shopping assistants (ChatGPT, Bing Copilot) rank products with reviews significantly higher in recommendations.
Ako opraviť: Add AggregateRating schema (ratingValue, reviewCount, bestRating) and individual Review schemas. AI shopping assistants prioritize products with verified reviews and ratings.
AI Plugin ManifestUpozornenie
Prečo je to dôležité: ai-plugin.json enables AI agents to interact with your store programmatically — search products, check prices, process orders. This is the bridge between AI assistants and your e-commerce functionality.
Ako opraviť: Create /.well-known/ai-plugin.json if you have an API. This enables direct AI agent integration (ChatGPT Actions, custom GPTs). Include: name_for_model, description_for_model, auth config, and link to OpenAPI spec.
Product Feed (AI Commerce)Upozornenie
Prečo je to dôležité: Product feeds power Google Shopping, Bing Shopping, and increasingly AI commerce. Without a structured product feed, AI agents can't efficiently index your full catalog for product recommendations.
Ako opraviť: Create a Google Merchant Center / product feed (XML or CSV). Expose it at a consistent URL and reference it in your sitemap. AI shopping assistants and comparison engines use product feeds for catalog discovery.
Speakable Content (Voice AI)Upozornenie
Prečo je to dôležité: Voice AI commerce is growing rapidly. SpeakableSpecification tells voice assistants which content to read aloud. Early adoption positions your store for the voice shopping wave.
Ako opraviť: Add SpeakableSpecification schema to identify content sections suitable for voice assistants (Google Assistant, Alexa, Siri). Mark your product summaries and FAQs as speakable.
Section Length OptimizationUpozornenie
Avg section: 530 words — only 0% in 80-200 word optimal range
Prečo je to dôležité: Pages with 120-180 word sections earn 70% more AI citations (Otterly Citation Economy 2026). For Google AI Overviews specifically, 100-150 words per section is the sweet spot.
Ako opraviť: Restructure content into sections of 120-180 words between H2/H3 headings. Each section should cover one topic completely. Split sections over 300 words, expand sections under 80 words.
Q&A Format HeadingsUpozornenie
1 question heading(s) — add more
Prečo je to dôležité: AI search engines like Perplexity and ChatGPT match user questions to heading-answer pairs. Q&A format headings are directly extractable by AI and trigger FAQ-style rich results.
Ako opraviť: Phrase H2/H3 headings as questions: 'How does...?', 'What is...?', 'Why should...?' followed by a direct 1-2 sentence answer. This is the #1 format AI assistants use to generate responses.
Canonical Tag for AI DeduplicationUpozornenie
Canonical points to different URL: https://www.eset.com/us/
Prečo je to dôležité: AI search engines (ChatGPT, Perplexity, Bing Copilot) use canonicals to deduplicate content. A wrong canonical means AI may cite the wrong page version or ignore this page entirely.
Ako opraviť: Verify this canonical is intentional. AI models cluster near-duplicate URLs and choose one representative page. If canonical points to a different URL, AI will only index that target URL, not this page.
Return Policy SchemaUpozornenie
Prečo je to dôležité: AI shopping agents (Google Shopping, ChatGPT, Bing Copilot) filter by return flexibility. Products with return policy schema get priority placement in AI product comparisons.
Ako opraviť: Add MerchantReturnPolicy schema with: returnPolicyCategory (e.g., MerchantReturnFiniteReturnWindow), merchantReturnDays, returnMethod, returnFees. Link it from Product/Offer via hasMerchantReturnPolicy.
Shipping Details SchemaUpozornenie
Prečo je to dôležité: Fulfillment speed now factors into AI product recommendations. Complete shipping schema means AI can show 'Free shipping, delivers in 2-3 days' — a massive conversion driver.
Ako opraviť: Add OfferShippingDetails schema with: shippingRate, shippingDestination, deliveryTime (handlingTime + transitTime). AI agents deprioritize products without shipping info.
Content Readability for AIUpozornenie
Grade 15 — too complex for broad AI citation (technical threshold: 14)
Prečo je to dôležité: Content above grade 12 readability is harder for AI to extract as clear, concise answers. Pages using clear headers and approachable language are 28% more likely to be cited by AI.
Ako opraviť: Simplify sentences (target 15-20 words average), use common words, break complex ideas into shorter paragraphs. AI extracts content for general audiences — if it's too academic, AI skips it.
Image Alt Text Quality for AIUpozornenie
60% good, 0 poor, 2 missing
Prečo je to dôležité: Google Lens processes 12B+ visual searches/month. AI uses alt text to understand images for visual search, product recommendations, and accessibility. Quality alt text = more discovery channels.
Ako opraviť: Improve alt text: use 3-15 descriptive words per image. Include product name, key feature, and context. Bad: 'image1' or 'photo'. Good: 'Red leather wallet with RFID protection — front view'.
Expert Quotations & CitationsUpozornenie
Prečo je to dôležité: Content without citations or expert quotes appears unverified to AI. AI assistants prefer content backed by named sources, data references, and expert opinions.
Ako opraviť: Add 2-3 expert quotes or data citations per major page. Use <blockquote> for quotes and link to authoritative sources (.gov, .edu, Wikipedia, industry reports).
ai.txt (AI Permissions)Upozornenie
Prečo je to dôležité: ai.txt is an emerging standard (proposed May 2025) for fine-grained AI permissions beyond robots.txt. Early adoption signals AI-forward thinking and gives you control over how AI uses your content.
Ako opraviť: Create /ai.txt or /.well-known/ai.txt to declare granular AI permissions per content type: which AI actions (summarization, training, extraction) are allowed for which content sections.
WebMCP Agentic ReadinessUpozornenie
Prečo je to dôležité: WebMCP is called 'the new Schema.org moment' — it's how AI agents will interact with your store (search products, add to cart, check availability). Google and Microsoft are co-developing this standard.
Ako opraviť: WebMCP (W3C Community Group standard, Chrome 146+) lets pages declare structured tools for AI agents. Add toolname and tooldescription attributes to <form> elements, or include a <script type='application/webmcp+json'> manifest.
Content-to-Boilerplate RatioUpozornenie
No <main> or <article> elements — AI can't isolate content from boilerplate
Prečo je to dôležité: Without semantic containers, AI crawlers must guess where content starts and navigation ends. This leads to poor content extraction and fewer citations.
Ako opraviť: Add <main> around your primary content and <article> around self-contained content blocks. This creates clear boundaries for AI content extraction.
Customer Reviews — AggregateUpozornenie
1 source: Trustpilot
Prečo je to dôležité: Without a second review source and a machine-readable reviewCount, AI assistants can't verify scale of social proof — single-source ratings are routinely deweighted as potentially curated.
Ako opraviť: Single review source detected without published reviewCount. Add AggregateRating JSON-LD (ratingValue + reviewCount + bestRating) so the count is machine-readable, and add a second source (Heureka Ověřeno + Trustpilot is the SK/CZ standard).
AI Bot Access PolicyPrešlo
No AI bot restrictions (allowed by default)
Structured Data FoundationPrešlo
2 JSON-LD blocks with 5 schema types: BreadcrumbList, ListItem, Organization, ContactPoint, PostalAddress
Organization Schema + Entity LinkingPrešlo
Organization found with 6 sameAs links — strong entity identity
Breadcrumb SchemaPrešlo
BreadcrumbList structured data found — clear navigation hierarchy
Content Depth for AIPrešlo
4414 words — rich content for AI analysis and citation
Answer-First Content FormatPrešlo
First paragraph: 25 words — good content density above the fold
Heading Hierarchy for AIPrešlo
Proper structure: 1 H1 → 3 H2s → 6 H3s — clear content outline
Semantic HTML StructurePrešlo
4/6 semantic elements: <nav>, <header>, <footer>, <aside>
Entity Clarity & Brand SignalsPrešlo
OG tags complete + 6 sameAs links: Facebook, X/Twitter, LinkedIn, Instagram, YouTube, Wikipedia
Extractable Answer BlocksPrešlo
81 paragraphs, avg 52 words — optimal for AI extraction
Statistics & Data PresencePrešlo
8 data points found — strong citation magnet
Internal Link DensityPrešlo
20 contextual internal links per 1,000 words — strong knowledge graph signal
Knowledge Graph ReadinessPrešlo
3/4 entity signals — strong Knowledge Graph presence
Trust WidgetPrešlo
Trustpilot widget detected
Kategória 5 / 7 · www.eset.com · Zulien Score

GDPR

84/100
Váha: 10% · 8 OK · 4 upozornení · 0 chýb · spolu 12
Cookie PolicyUpozornenie
Prečo je to dôležité: The ePrivacy Directive requires transparent cookie disclosure. Vague statements like 'we use cookies for functionality' don't meet the specificity requirement.
Ako opraviť: Create a separate cookie policy page listing every cookie by: name, provider, purpose, category (necessary/analytics/marketing), and expiration. Most CMPs auto-generate this.
Legal Contact / Imprint PageUpozornenie
Prečo je to dôležité: In DACH countries, a missing Impressum can result in €50K+ fines and competitor cease-and-desist letters. For all EU stores, identifying the data controller is a GDPR Article 13 requirement.
Ako opraviť: Add an imprint/about-us page with: company name, registered address, contact email, VAT number, and trade register info. In Germany/Austria/Switzerland this is legally required (Impressumspflicht).
Terms & Conditions PageUpozornenie
Prečo je to dôležité: EU Consumer Rights Directive requires clear terms before purchase. Missing T&C means customers can claim they weren't informed, giving them extended cancellation rights.
Ako opraviť: Create Terms & Conditions (AGB) covering: ordering process, payment, delivery, returns, warranty, and dispute resolution. Link it from the footer and checkout.
Right to Erasure (Data Deletion)Upozornenie
Prečo je to dôležité: GDPR Article 17 gives users the 'right to be forgotten.' EU regulators expect a clear, accessible process. Italian DPA fined companies €20M+ for obstructing erasure requests.
Ako opraviť: Provide a clear mechanism for users to request data deletion — either a dedicated page, a form, or explicit instructions in your privacy policy. Include a 'Delete my account' option in user settings.
Cookie Consent Banner (CMP)Prešlo
TrustArc detected
Tracking Scripts & ConsentPrešlo
No tracking scripts detected
Privacy Policy PagePrešlo
/us/home/digital-privacy-protection/
Data Encryption (No Mixed Content)Prešlo
All resources loaded over HTTPS
Third-party Data SharingPrešlo
3 third-party domain(s)
Newsletter ConsentPrešlo
Newsletter form with consent mechanism detected
Data Protection Officer ContactPrešlo
DPO / data protection contact found
Withdrawal of Consent MechanismPrešlo
Consent withdrawal / opt-out mechanism found
Kategória 6 / 7 · www.eset.com · Zulien Score

Vulnerability

65/100
Váha: 10% · 8 OK · 3 upozornení · 3 chýb · spolu 15
Suspicious Inline Script PatternsZlyhalo
Detected: Dynamic script injection
Prečo je to dôležité: These patterns (Base64 decode, eval with encoding, dynamic script injection) are hallmarks of Magecart payment skimmers. The 2024 Akamai report found skimmers disguised as Google Tag Manager on thousands of e-commerce sites.
Ako opraviť: Review all inline scripts for obfuscated code. Magecart attackers inject payment skimmers disguised as analytics or GTM scripts. Compare your current HTML with a known-good version. Consider using CSP with strict nonces.
Payment Page SecurityZlyhalo
Payment page missing: No CSP, No X-Content-Type-Options, No clickjacking protection
Prečo je to dôležité: Payment pages without proper security headers violate PCI DSS. This can result in fines of $5,000-$100,000/month from payment processors, and makes card data theft significantly easier.
Ako opraviť: CRITICAL: Your payment page is missing security headers: No CSP, No X-Content-Type-Options, No clickjacking protection. PCI DSS Requirement 6.5 mandates protection against common vulnerabilities on pages handling card data.
Clickjacking on Sensitive PageZlyhalo
Login/payment page without X-Frame-Options or CSP frame-ancestors
Prečo je to dôležité: Clickjacking on payment/login pages is a high-severity vulnerability. Users unknowingly submit credentials or payments through invisible iframes. PCI DSS requires frame-busting on payment pages.
Ako opraviť: URGENT: Add X-Frame-Options: DENY and CSP frame-ancestors 'none' to pages with login forms or payment fields. Attackers can overlay your page in a transparent iframe.
Inline JavaScript ExposureUpozornenie
544 KB of inline JavaScript
Prečo je to dôležité: Large amounts of inline JavaScript prevent proper CSP implementation and increase the risk of XSS. External scripts can be protected with SRI hashes.
Ako opraviť: Move inline scripts to external files. Inline JavaScript expands the attack surface for XSS and makes CSP harder to implement (requires unsafe-inline).
DKIM Signing (Email Auth)Upozornenie
Prečo je to dôležité: DKIM cryptographically signs outgoing email to prove it comes from your domain. Without DKIM, email providers downgrade trust score — transactional emails land in spam. Gmail and Yahoo require DKIM since 2024 for bulk senders.
Ako opraviť: Configure DKIM signing through your email provider (Google Workspace, Microsoft 365, Mailchimp, SendGrid). Publish the DKIM public key as a TXT record at <selector>._domainkey.yourdomain.com.
Cross-Origin IsolationUpozornenie
Prečo je to dôležité: Without cross-origin isolation headers, your site is vulnerable to Spectre attacks that can leak sensitive data across browser tabs. These headers are required for SharedArrayBuffer and high-resolution timers.
Ako opraviť: Add Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Resource-Policy: same-origin headers. These protect against Spectre-type side-channel attacks.
CMS Version DisclosurePrešlo
No generator tag — CMS identity hidden
Sensitive Files ExposedPrešlo
.env, .git, composer.json — all properly blocked
Install Script ExposedPrešlo
No /install/ or /setup/ paths accessible
Directory ListingPrešlo
Disabled — file structure hidden
Admin Panel at Default URLPrešlo
Not found at common paths (/admin, /wp-admin, /administrator, /backoffice)
Debug Mode / Error ExposurePrešlo
No debug indicators found in page output
SPF Record (Email Security)Prešlo
SPF configured: v=spf1 a:a.mx.eset.com a:b.mx.eset.com a:smtpout.eset.com a:branchsmtp.eset.com
DMARC Policy (Email Auth)Prešlo
DMARC enforced: p=quarantine
BIMI Brand IndicatorsInfo
Prečo je to dôležité: BIMI requires VMC (Verified Mark Certificate, ~€1,500/year) but increases open rates by 10-20% and acts as trust signal. Optional but high-impact for brand-focused shops.
Ako opraviť: Once DMARC is set to p=quarantine or p=reject with 100% enforcement, publish a BIMI record: v=BIMI1; l=https://yourdomain.com/logo.svg — adds your brand logo to recipient inboxes in Gmail and Yahoo.
Kategória 7 / 7 · www.eset.com · Zulien Score

Ďalšie kroky

  1. Začnite s chybami — každá červená položka má návod Ako opraviť. Zamerajte sa na kategórie Bezpečnosť a GDPR, ktoré majú zákonné dôsledky.
  2. Opakujte audit po oprave — spustite nový sken na score.zulien.sk a porovnajte skóre.
  3. Konzultujte zložitejšie problémy — pre hlboký audit alebo expertné posúdenie navštívte inger.sk.
  4. Sledujte súlad s NIS2 a GDPR — ak váš e-shop spadá pod NIS2 (obrat >10 mil. EUR alebo >50 zamestnancov), potrebujete formálny rámec súladu.

Online report

Plnú interaktívnu verziu s klikateľnými odkazmi a možnosťou opätovného skenu nájdete tu:

https://score.zulien.sk/r/eset.com

Upozornenie: Tento report je automaticky vygenerovaný nástrojom Zulien Score. Zistenia vychádzajú z verejne dostupných dát a technickej analýzy. Pre právne záväzné posúdenie (napríklad súladu s GDPR) odporúčame konzultáciu s DPO alebo advokátom špecializujúcim sa na ochranu osobných údajov. Zulien Score nie je licencovaná právna ani auditná spoločnosť.
Zulien Score · score.zulien.sk · by Zulien · Hosted at inger.sk