Ostatnie skanowanie: June 13, 2026

D0/100

Poniżej średniej

Wyniki oceny

www.zlatnictvohorvath.sk

Przeskanowano June 13, 2026

Magento

Vue.js

Nuxt.js

Swiper

Toastr

Vite

Ostatnie skanowanie: June 13, 2026

Plan działania

Napraw najpierw te 3 rzeczy

Posortowane według wpływu na wynik — każda poprawka podnosi ogólną ocenę.

+15potencjalny zysk

67/100

Performance

Waga: 25% · 10 zaliczonych · 4 ostrzeżenia · 3 nieudanych

Co znaleźliśmy: 947ms (good: <200ms)

Dlaczego to ma znaczenie: 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.

Jak to naprawić: 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

Co znaleźliśmy: 4.0 MB, 186 requests — too heavy!

Dlaczego to ma znaczenie: 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.

Jak to naprawić: 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 →

Co znaleźliśmy: 592 KB wasted on unused code!

Dlaczego to ma znaczenie: 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.

Uwaga: Ta kontrola wykorzystuje detekcję heurystyczną i może zwracać również fałszywe alarmy. Zalecamy ręczną weryfikację.

Jak to naprawić: You're loading 592 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.

Co znaleźliśmy: 8 CSS files loaded

Dlaczego to ma znaczenie: Each render-blocking CSS file adds network latency. Consolidating CSS from 8 to 2 files can save 200-400ms on first load.

Jak to naprawić: Consolidate CSS files by bundling them into 1-3 files. Each CSS file is a separate HTTP request that blocks rendering until downloaded.

Co znaleźliśmy: Custom fonts detected without preload hints

Dlaczego to ma znaczenie: Fonts are discovered late in the render pipeline (after CSS is parsed). Preloading tells the browser to download them immediately, reducing Flash of Invisible Text (FOIT) by 200-500ms.

Jak to naprawić: Preload your primary font: <link rel='preload' href='/fonts/main.woff2' as='font' type='font/woff2' crossorigin>. For Google Fonts: preconnect to fonts.gstatic.com.

Request quote for speed audit

Co znaleźliśmy: 8 CSS files without critical CSS extraction

Dlaczego to ma znaczenie: Render-blocking CSS delays first paint. Inlining critical CSS eliminates the render-blocking round trip — the biggest FCP improvement for CSS-heavy sites.

Jak to naprawić: Extract critical above-the-fold CSS and inline it in <head>. Load remaining CSS asynchronously: <link rel='preload' href='styles.css' as='style' onload='this.rel="stylesheet"'>.

Request quote for speed audit

Co znaleźliśmy: 468 KB of inline JavaScript

Dlaczego to ma znaczenie: 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.

Jak to naprawić: 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 problemów w kategorii Performance. Jest miejsce na poprawę.

Twój sklep na razie nie spełnia warunków dla odznaki Zulien Score. Uzyskaj ocenę 80+!

📧 Przypomnienia o ponownym skanowaniu

Raz w miesiącu napiszemy do Ciebie, kiedy zrobić nowe skanowanie i śledzić swoje postępy.

Zgadzam się z Polityka prywatności. Wyślemy Ci raport i opcjonalne powiadomienia o ponownym skanowaniu.

🚀 Popraw swoją ocenę

Nasze moduły PrestaShop potrafią automatycznie naprawić większość tych problemów.

Bezpłatna 15-min konsultacja · Bez zobowiązań

Udostępnij i eksportuj

Gotowy, by poprawić swoją ocenę?

Twój sklep internetowy traci klientów każdego dnia. Powyższe problemy kosztują Cię sprzedaż.

Napraw samodzielnie

Przejrzyj nasze moduły i napraw problemy w 2 kliknięciach.

Przeglądaj moduły Zulien

Zostaw to nam

Opisz swój cel, a w ciągu 48 h prześlemy Ci wycenę. Bez rozmów telefonicznych.

Uzyskaj wycenę

Odpowiedź w ciągu 48 h · Bez rozmowy telefonicznej

To zautomatyzowany szacunek heurystyczny, nie profesjonalny audyt. Wykryte zagadnienia odzwierciedlają publicznie obserwowalne sygnały w momencie skanowania i mogą zawierać również nieprawidłowe wskazania.Przeczytaj o naszej metodologiiZgłoś nieścisłośćUsuń ten raport

Zulien Score

Komplexný audit e-shopu — 50+ kontrol v 7 kategóriách

64/100

Grade D

www.zlatnictvohorvath.sk

Dátum auditu: June 13, 2026

Platforma: Magento

Online report: https://score.zulien.sk/r/zlatnictvohorvath.sk

Executive summary

Chýb

Upozornení

148

Spolu kontrol

Skóre po kategóriách

Kategória	Skóre	Váha	Chyby	Upozornenia	OK
Performance	67/100	25%	3	4	10
SEO	91/100	20%	1	2	17
Security	55/100	15%	3	9	5
Mobile	46/100	10%	2	11	5
AI Readiness	53/100	10%	3	19	5
GDPR	52/100	10%	2	7	4
Vulnerability	59/100	10%	4	4	8

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.

XML Sitemap· SEO

Sitemaps help Google discover and index pages 3-5x faster, especially for large stores with deep category structures.

HSTS (Strict-Transport-Security)· Security

Without HSTS, attackers can intercept the first HTTP request and downgrade the connection. This is the #1 way to steal session cookies on public WiFi.

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.

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.

Image Alt Text Quality for AI· AI Readiness

Poor alt text means your product images are invisible to AI visual search (Google Lens, Bing Visual Search). This is also an accessibility requirement (WCAG 2.1 AA) — many regions enforce this legally.

Performance

67/100

Váha: 25% · 10 OK · 4 upozornení · 3 chýb · spolu 17

Total Blocking Time (TBT)Zlyhalo

947ms (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

4.0 MB, 186 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

592 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 592 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.

CSS File CountUpozornenie

8 CSS files loaded

Prečo je to dôležité: Each render-blocking CSS file adds network latency. Consolidating CSS from 8 to 2 files can save 200-400ms on first load.

Ako opraviť: Consolidate CSS files by bundling them into 1-3 files. Each CSS file is a separate HTTP request that blocks rendering until downloaded.

Font PreloadingUpozornenie

Custom fonts detected without preload hints

Prečo je to dôležité: Fonts are discovered late in the render pipeline (after CSS is parsed). Preloading tells the browser to download them immediately, reducing Flash of Invisible Text (FOIT) by 200-500ms.

Ako opraviť: Preload your primary font: <link rel='preload' href='/fonts/main.woff2' as='font' type='font/woff2' crossorigin>. For Google Fonts: preconnect to fonts.gstatic.com.

Critical CSS StrategyUpozornenie

8 CSS files without critical CSS extraction

Prečo je to dôležité: Render-blocking CSS delays first paint. Inlining critical CSS eliminates the render-blocking round trip — the biggest FCP improvement for CSS-heavy sites.

Ako opraviť: Extract critical above-the-fold CSS and inline it in <head>. Load remaining CSS asynchronously: <link rel='preload' href='styles.css' as='style' onload='this.rel="stylesheet"'>.

Inline JavaScript SizeUpozornenie

468 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

108ms

First Contentful Paint (FCP)Prešlo

1.08s

Largest Contentful Paint (LCP)Prešlo

1.70s — Core Web Vital ✓

Cumulative Layout Shift (CLS)Prešlo

0.000 — Core Web Vital ✓

Speed IndexPrešlo

2.27s

Render-blocking ResourcesPrešlo

No render-blocking resources found

Text Compression (gzip/brotli)Prešlo

All text resources properly compressed

Resource Hints (Preload/Preconnect)Prešlo

4 preload, 0 preconnect hint(s)

Lazy LoadingPrešlo

32% of images use native lazy loading (112/348)

Script Loading StrategyPrešlo

100% of scripts use async/defer/module (1 async, 0 defer, 1 module)

SEO

91/100

Váha: 20% · 17 OK · 2 upozornení · 1 chýb · spolu 25

XML SitemapZlyhalo

Prečo je to dôležité: Sitemaps help Google discover and index pages 3-5x faster, especially for large stores with deep category structures.

Ako opraviť: Generate an XML sitemap at /sitemap.xml listing all important pages. Exclude noindex pages, filters, and duplicate URLs. Reference it in robots.txt.

Canonical URL ConsistencyUpozornenie

Canonical points to different URL: https://zlatnictvohorvath.sk

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.

Color Contrast SignalUpozornenie

89 very light text colors found — potential contrast issues

Prečo je to dôležité: Low contrast text is the #1 accessibility issue found on 83.6% of home pages (WebAIM Million 2024). It affects 8% of men with color vision deficiency and everyone in bright sunlight.

Ako opraviť: Ensure text has minimum 4.5:1 contrast ratio against background (WCAG AA). Use tools like WebAIM Contrast Checker. Light gray text on white is the most common violation.

Meta TitlePrešlo

46 chars — "Zlatníctvo Horváth | E-shop a Kamenná Predajňa"

Meta DescriptionPrešlo

160 chars

H1 HeadingPrešlo

"Homepage"

Content Structure (H2 Headings)Prešlo

11 H2 subheadings found

Open Graph TagsPrešlo

og:title, og:description, og:image, og:type

Open Graph Image FormatPrešlo

image/webp

Canonical URLPrešlo

https://zlatnictvohorvath.sk

robots.txtPrešlo

Present

HTML Language AttributePrešlo

lang="sk"

Hreflang Tags (Multilingual)Prešlo

2 language(s): sk-SK, x-default

Meta Robots TagPrešlo

index, follow

FaviconPrešlo

Favicon detected

Image Format OptimizationPrešlo

53% next-gen formats (185 WebP, 0 AVIF)

Content DepthPrešlo

1456 words — sufficient content

Deep Heading HierarchyPrešlo

H2: 11, H3: 3 — well-structured content

Internal LinkingPrešlo

86 internal links — strong site navigation

Accessibility FundamentalsPrešlo

3/4 a11y signals: 3 ARIA roles, 4 ARIA labels, lang="sk"

Twitter/X CardsInfo

SPA detected — see note below

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ť: JS-renderovaná stránka (Nuxt) — obsah sa načítava cez JavaScript a nie je viditeľný nášmu skeneru. Overte manuálne. JS-rendered site detected (Nuxt) — content is loaded client-side and not visible to our raw-HTML scanner. Verify manually or re-run with a headless browser.

Structured Data (JSON-LD)Info

SPA detected — see note below

Prečo je to dôležité: Pages with structured data get rich snippets in Google — star ratings, prices, availability — increasing CTR by 20-30%.

Image Alt AttributesInfo

Only 64% of 348 images have alt text · SPA detected — see note below

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).

Text-to-HTML RatioInfo

1% — very thin content (1456 words) · SPA detected — see note below

Prečo je to dôležité: Google's Helpful Content Update specifically targets thin content pages. This significantly hurts your rankings.

Semantic HTML StructureInfo

Only 3/6 semantic elements — missing: <article>, <main>, <aside> · SPA detected — see note below

Prečo je to dôležité: Semantic HTML gives search engines clear signals about content structure. Pages with proper semantic markup earn more featured snippets and knowledge panel appearances.

Security

55/100

Váha: 15% · 5 OK · 9 upozornení · 3 chýb · spolu 17

HSTS (Strict-Transport-Security)Zlyhalo

Prečo je to dôležité: Without HSTS, attackers can intercept the first HTTP request and downgrade the connection. This is the #1 way to steal session cookies on public WiFi.

Ako opraviť: Add header: Strict-Transport-Security: max-age=31536000; includeSubDomains; preload — then submit to hstspreload.org.

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'.

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.

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.

Technology DisclosureUpozornenie

Server: nginx/1.29.4, X-Powered-By: Nuxt

Prečo je to dôležité: Exposing exact server/PHP versions lets attackers search CVE databases for specific exploits. This is the first step in most automated attacks.

Ako opraviť: Hide server version: set ServerTokens Prod (Apache) or server_tokens off (Nginx). Remove X-Powered-By header completely.

Subresource Integrity (SRI)Upozornenie

Only 0/2 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.

Server Version DisclosureUpozornenie

Nginx 1.29.4 exposed in headers

Prečo je to dôležité: Exposing "Nginx 1.29.4" lets attackers search for version-specific exploits. Hide it to add a layer of defense.

Ako opraviť: Hide server version. Apache: add 'ServerTokens Prod' and 'ServerSignature Off' to httpd.conf. Nginx: add 'server_tokens off;' to nginx.conf.

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.

SSL/TLS CertificatePrešlo

Valid HTTPS connection established

DNSSECPrešlo

Zone is DNSSEC-signed (DNSKEY published)

Prečo je to dôležité: DNSSEC protects against DNS cache poisoning and on-path attackers redirecting your domain. Required by some sector regulators for NIS2 essential/important entities.

HTTP → HTTPS RedirectPrešlo

HTTP properly redirects to HTTPS

Cookie Security FlagsPrešlo

No cookies set on initial response

Password Field SecurityPrešlo

1 password field(s) — allow password manager autofill

Mobile

46/100

Váha: 10% · 5 OK · 11 upozornení · 2 chýb · spolu 18

Mobile Performance ScoreZlyhalo

36/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 0/3 inputs má label (0%)

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).

Viewport ConfigurationUpozornenie

Present, but maximum-scale=1 disables pinch-to-zoom

Prečo je to dôležité: Preventing pinch-to-zoom is an accessibility violation (WCAG 1.4.4). Users with vision impairments need zoom. Google penalizes sites that disable zoom.

Ako opraviť: Remove 'maximum-scale=1' and 'user-scalable=no' from your viewport meta tag. Use: <meta name='viewport' content='width=device-width, initial-scale=1'>

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

Prečo je to dôležité: PWAs combine the best of web and native apps. Starbucks' PWA doubled daily active users. For e-commerce, PWAs enable push notifications, offline browsing, and home screen access.

Ako opraviť: Consider adding Progressive Web App features: 1) Create manifest.json with app name, icons, and theme color, 2) Register a service worker for offline caching. This makes your store installable on mobile.

Theme ColorUpozornenie

Prečo je to dôležité: Theme-color creates a polished, branded mobile experience. It makes your site look native and professional — small detail, big perception impact.

Ako opraviť: Add <meta name='theme-color' content='#your-brand-color'> to match your brand. Browsers use this to color the address bar, task switcher, and PWA chrome.

Inline CSS SizeUpozornenie

441 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.

Responsive Images (srcset)Upozornenie

348 images without responsive sizing

Prečo je to dôležité: Without srcset, mobile users download full-size desktop images — wasting 50-80% of bandwidth. Responsive images are the single biggest mobile performance win for image-heavy sites.

Ako opraviť: Add srcset and sizes attributes to <img> tags to serve appropriately sized images for each screen. Mobile devices shouldn't download 1920px desktop images.

Form Input TypesUpozornenie

phone fields use type='text' instead of type='tel'

Prečo je to dôležité: Correct input types show specialized mobile keyboards — email keyboard with @, phone with number pad. This reduces input errors by 30% and speeds up form completion (Baymard Institute).

Ako opraviť: Use semantic input types: type='email' for email (shows @ keyboard), type='tel' for phone (shows number pad), type='search' for search (shows search button). These trigger optimized mobile keyboards.

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.

SK/CZ Local Payment MethodsUpozornenie

Iba 2 SK/CZ metód (Tatra Pay, QR platba / Pay by square)

Prečo je to dôležité: 48 % SK online platieb ide cez lokálne banky alebo QR platbu (Tatrabanka study 2024). Iba karta = 50 % cart abandonment na SK trhu.

Ako opraviť: Pridaj ďalšie SK/CZ local methods: ComGate, GoPay, Barion, Besteron, PayU. SK zákazníci preferujú bankové tlačidlá a QR platbu pred kartou.

Heading Hierarchy (WCAG 1.3.1)Upozornenie

Preskočené úrovne: h2→h4, h2→h6

Prečo je to dôležité: Preskočené heading levely (napr. h1 priamo na h3) zlomia navigáciu pre screen reader používateľov a signalizujú Googlu zlú štruktúru dokumentu. Aj SEO je negatívne ovplyvnené.

Ako opraviť: Dodržuj poradie nadpisov h1 → h2 → h3 → h4 bez preskočenia. Screen readers používajú hierarchiu nadpisov na navigáciu. Ak potrebuješ menšie písmo ale rovnakú úroveň, použi CSS triedu, nie nižší heading tag.

Content Fits ViewportPrešlo

No horizontal scrolling needed

Responsive Design TechniquesPrešlo

Flexbox, CSS Grid, Media queries detected

Mobile Navigation (Semantic)Prešlo

<nav> element present — proper navigation landmark

Payment Methods DetectedPrešlo

2 method(s): Tatra Pay, QR platba / Pay by square

Link Text Quality (WCAG 2.4.4)Prešlo

Všetky odkazy majú popisný text

AI Readiness

53/100

Váha: 10% · 5 OK · 19 upozornení · 3 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.

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.

Image Alt Text Quality for AIZlyhalo

Only 38% quality alt text — 126 missing, 90 poor

Prečo je to dôležité: Poor alt text means your product images are invisible to AI visual search (Google Lens, Bing Visual Search). This is also an accessibility requirement (WCAG 2.1 AA) — many regions enforce this legally.

Ako opraviť: Audit all images: add descriptive alt text (3-15 words) to every <img>. Include product names, features, materials, colors. This is critical for visual AI search and accessibility compliance.

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.

Breadcrumb SchemaUpozornenie

Prečo je to dôležité: AI assistants use breadcrumbs to understand product categorization and site structure. Without it, AI can't contextualize where products fit in your catalog — e.g., 'Running Shoes' under 'Sports > Footwear > Running'.

Ako opraviť: Add BreadcrumbList schema reflecting your category hierarchy: Home → Category → Subcategory → Product. Each item needs name and URL.

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.

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.

Heureka XML FeedUpozornenie

Prečo je to dôležité: Heureka.sk a Heureka.cz sú dominantné cenové porovnávače na SK/CZ trhu (40%+ all e-com discovery traffic). Bez XML feedu nie ste viditeľní na hlavnom trhovisku — strata 20-30 % potenciálneho traffic. Žiaden generický audit tool toto nekontroluje.

Ako opraviť: Vygeneruj Heureka XML feed na /feed/heureka.xml (alebo /export/heureka.xml). PrestaShop má modul Heureka.cz, WooCommerce má pluginy. Štruktúra: <SHOP><SHOPITEM>...</SHOPITEM></SHOP> s ITEM_ID/PRODUCTNAME/URL/PRICE_VAT/CATEGORYTEXT (povinné) + EAN/PARAM/DELIVERY_DATE (highly recommended pre ranking).

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.

Statistics & Data PresenceUpozornenie

Only 1 data point(s) — add more

Prečo je to dôležité: Princeton/Georgia Tech study found that adding statistics to content improves AI visibility by 41% — the single most effective GEO optimization. AI assistants prefer content with verifiable data points.

Ako opraviť: Add specific statistics, percentages, dollar amounts, and quantified claims. E.g., '93% of customers report...', 'saves an average of €200/year', '3x faster than...' Data makes content citable.

Section Length OptimizationUpozornenie

Avg section: 77 words — only 17% 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.

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.

Knowledge Graph ReadinessUpozornenie

1/4 signals — missing: @id in JSON-LD, sameAs links (Wikipedia, LinkedIn), Organization schema

Prečo je to dôležité: Brands with verified Knowledge Graph presence receive 3.1x more AI citations. @id creates a persistent entity identifier that connects your schema across pages and platforms.

Ako opraviť: Add: @id in JSON-LD, sameAs links (Wikipedia, LinkedIn), Organization schema. Use @id in JSON-LD to create a unique node identifier. Ensure your brand name is identical in title, schema, and OG tags. Link to Wikipedia/Wikidata via sameAs.

Content Readability for AIUpozornenie

Grade 20 — 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.

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.

Trust WidgetUpozornenie

Žiaden trust widget (Heureka / Trustpilot / AggregateRating) nedetekovaný

Prečo je to dôležité: SK/CZ kupujúci majú 2× vyššiu dôveru k Heureka Ověřeno ako k iným trust signálom (Heureka research 2024). LLM-y (ChatGPT, Perplexity) a Google SGE citujú shopy s AggregateRating schema prednostne.

Ako opraviť: Pre SK/CZ shopy: inštaluj Heureka Ověřeno zákazníky widget (zadarmo pre overených predajcov — https://sluzby.heureka.sk). Alternatívne: Trustpilot, Google Reviews s AggregateRating schema. Trust widget na product + kategória + footer.

AI Bot Access PolicyPrešlo

No AI bot restrictions (allowed by default)

Content Depth for AIPrešlo

1456 words — rich content for AI analysis and citation

Heading Hierarchy for AIPrešlo

Proper structure: 1 H1 → 11 H2s → 3 H3s — clear content outline

Q&A Format HeadingsPrešlo

3 question-format headings — excellent for AI Q&A extraction

Internal Link DensityPrešlo

59 contextual internal links per 1,000 words — strong knowledge graph signal

Content Accessibility for AIInfo

Only 1456 words visible in HTML — content may be JS-dependent · SPA detected — see note below

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.

Structured Data FoundationInfo

SPA detected — see note below

Prečo je to dôležité: Without structured data, your store is invisible to AI commerce. Google AI Overviews, ChatGPT Shopping, Perplexity, and Bing Copilot all rely on schema markup to understand and recommend products.

Organization Schema + Entity LinkingInfo

SPA detected — see note below

Prečo je to dôležité: Organization schema is the foundation of your AI identity. Without it, AI assistants can't confidently attribute information to your brand, verify your legitimacy, or show your Knowledge Panel.

FAQ Schema (Direct AI Answers)Info

SPA detected — see note below

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.

Answer-First Content FormatInfo

Content doesn't start with a strong summary paragraph · SPA detected — see note below

Prečo je to dôležité: AI assistants extract content from the first 100 words to generate summaries. The LLMClicks analyzer found pages with answer-first format get 40% more AI citations. Most AI systems read top-down.

Semantic HTML StructureInfo

3/6 elements — missing: <article>, <main>, <aside> · SPA detected — see note below

Prečo je to dôležité: AI crawlers don't see your CSS. They rely on semantic HTML to distinguish main content from navigation, ads, and boilerplate. The WordLift AI Audit weights semantic HTML as a primary machine-readability signal.

Structured Content (Lists & Tables)Info

27 lists found — consider adding comparison tables · SPA detected — see note below

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.

Content Freshness SignalsInfo

SPA detected — see note below

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.

Entity Clarity & Brand SignalsInfo

OG tags complete but no sameAs entity links · SPA detected — see note below

Prečo je to dôležité: AI needs to confidently identify your brand entity. Open Graph + sameAs create a cross-platform identity that AI models recognize. The HubSpot AEO Grader found entity clarity is a top-3 factor for AI brand recognition.

Extractable Answer BlocksInfo

44 paragraphs, avg 10 words — too short for citation · SPA detected — see note below

Prečo je to dôležité: Pages with 40-80 word paragraphs earn 70% more AI citations (Otterly 2026 data). AI extracts individual paragraphs as answer snippets — dense walls of text get skipped.

Canonical Tag for AI DeduplicationInfo

Canonical points to different URL: https://zlatnictvohorvath.sk · SPA detected — see note below

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.

Content-to-Boilerplate RatioInfo

No <main> or <article> elements — AI can't isolate content from boilerplate · SPA detected — see note below

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.

GDPR

52/100

Váha: 10% · 4 OK · 7 upozornení · 2 chýb · spolu 16

Tracking Scripts Without ConsentZlyhalo

1 tracker(s) loading without consent: Google Analytics/GTM

Prečo je to dôležité: Loading ANY tracking before consent is a direct GDPR/ePrivacy violation. This is the most commonly fined offense — French CNIL issued €150M+ in fines for this in 2022 alone.

Ako opraviť: These tracking scripts fire before user consent: Google Analytics/GTM. Configure your CMP to block them until explicit opt-in. Use Tag Manager's consent mode or CMP script blocking.

GDPR Art. 6(1)(a) · GDPR Art. 7 · SK 18/2018 § 14

Google Consent Mode v2Zlyhalo

Prečo je to dôležité: Google requires Consent Mode v2 for all EU traffic since March 2024. Without it, Google Ads remarketing and conversion data will not function, and you lose measurement data.

Ako opraviť: Implement Google Consent Mode v2 with gtag('consent', 'default', { ad_storage: 'denied', analytics_storage: 'denied', ad_user_data: 'denied', ad_personalization: 'denied' }). Required since March 2024 for EU audiences.

GDPR Art. 6(1)(a) · GDPR Art. 7 · SK 18/2018 § 14

Personal Data Exposure in SourceUpozornenie

1 email(s) found in page source: obchod@zlatnictvohorvath.sk

Prečo je to dôležité: Exposing personal email addresses in HTML violates the data minimization principle (GDPR Art. 5). It also invites spam harvesting.

Ako opraviť: Remove plain-text email addresses from HTML source. Use contact forms instead, or obfuscate emails with JavaScript encoding.

International Data TransfersUpozornenie

1 US-based tracker(s) without consent: Google Analytics/GTM

Prečo je to dôležité: The EU-US Data Privacy Framework covers some transfers, but loading US trackers without consent remains a violation. Austrian and French DPAs have ruled Google Analytics non-compliant without proper safeguards.

Ako opraviť: US-based trackers transfer personal data outside the EU. Under GDPR, this requires: 1) User consent via CMP, 2) Standard Contractual Clauses (SCCs) with each provider, 3) Data Transfer Impact Assessment.

Forms Without Privacy NoticeUpozornenie

1 form(s) on page with no privacy policy link

Prečo je to dôležité: GDPR Article 13 requires informing users about data processing at the point of collection. Forms without privacy notices violate the transparency principle.

Ako opraviť: Add a link to your privacy policy next to or below every form that collects personal data (contact, registration, newsletter). Include a checkbox for consent where required.

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.

Newsletter ConsentUpozornenie

Newsletter signup found without visible consent checkbox

Prečo je to dôležité: GDPR requires 'freely given, specific, informed' consent for marketing emails. A newsletter form without explicit opt-in violates Article 7. Italian DPA fined companies for pre-checked newsletter boxes.

Ako opraviť: Add an unchecked consent checkbox to your newsletter form: 'I agree to receive marketing emails and have read the Privacy Policy [link].' Pre-checked boxes are not valid consent under GDPR.

Data Protection Officer ContactUpozornenie

Prečo je to dôležité: GDPR Article 37 requires a DPO for organizations processing personal data at scale. Even if not mandatory, having a designated privacy contact builds trust and is expected by regulators.

Ako opraviť: Add DPO contact details (or privacy contact if DPO not required) to your privacy policy and footer. Include: name/title, email (e.g., dpo@yourdomain.com), and postal address.

Withdrawal of Consent MechanismUpozornenie

Prečo je to dôležité: GDPR Article 7(3): 'It shall be as easy to withdraw as to give consent.' If users can subscribe in one click, unsubscribing must be equally simple. Missing this is a common regulatory finding.

Ako opraviť: Provide a clear way to withdraw consent: an 'unsubscribe' link in emails, a 'cookie settings' button in the footer, and a 'revoke consent' section in your privacy policy.

Legal Contact / Imprint PagePrešlo

/o-nas

Terms & Conditions PagePrešlo

/obchodne-podmienky

Data Encryption (No Mixed Content)Prešlo

All resources loaded over HTTPS

Third-party Data SharingPrešlo

1 third-party domain(s)

Cookie Consent Banner (CMP)Info

SPA detected — see note below

Prečo je to dôležité: Since 2024, EU regulators actively enforce cookie consent. CNIL fined Google €150M and Amazon €35M for non-compliant cookie banners. Fines can reach 4% of global annual revenue.

Privacy Policy PageInfo

SPA detected — see note below

Prečo je to dôležité: A missing privacy policy is the #1 most cited GDPR violation. Every EU data protection authority considers this a basic requirement — and fines start at €5,000 for small businesses.

Cookie PolicyInfo

SPA detected — see note below

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.

Vulnerability

59/100

Váha: 10% · 8 OK · 4 upozornení · 4 chýb · spolu 16

Form CSRF ProtectionZlyhalo

1 form(s) without CSRF tokens

Prečo je to dôležité: CSRF is in the OWASP Top 10. Without tokens, attackers can craft pages that automatically submit forms on your site as the victim's browser session.

Ako opraviť: Add CSRF token validation to every form. Most CMS frameworks have built-in CSRF protection — make sure it's enabled on all forms, including search and newsletter signup.

Suspicious Inline Script PatternsZlyhalo

Detected: Payment data exfiltration pattern

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 HSTS, 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 HSTS, 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

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.

X-Powered-By HeaderUpozornenie

Nuxt

Prečo je to dôležité: "Nuxt" reveals your server technology and version. Attackers use this to find matching CVEs.

Ako opraviť: Remove the X-Powered-By header. PHP: add 'expose_php = Off' to php.ini. Express.js: app.disable('x-powered-by').

Inline JavaScript ExposureUpozornenie

468 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).

DMARC Policy (Email Auth)Upozornenie

DMARC set to p=none (monitoring only, no enforcement)

Prečo je to dôležité: DMARC p=none provides zero protection against email spoofing. It only generates reports. Move to p=quarantine to actually block forged emails from reaching your customers' inboxes.

Ako opraviť: Upgrade DMARC policy from p=none to p=quarantine or p=reject. p=none only monitors — it doesn't block spoofed emails. Start with quarantine, then move to reject after verifying legitimate emails pass.

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 mx include:_spf.nameserver.sk -all

DKIM Signing (Email Auth)Prešlo

DKIM configured (selectors: default)

Ďalšie kroky

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.
Opakujte audit po oprave — spustite nový sken na score.zulien.sk a porovnajte skóre.
Konzultujte zložitejšie problémy — pre hlboký audit alebo expertné posúdenie navštívte inger.sk.
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/zlatnictvohorvath.sk

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