Posledný sken: 20. júna 2026

C0/100

Priemerné

Výsledky skóre

hetzner.truckershop.sk

Skenované 20. júna 2026

PrestaShop

jQuery

Font Awesome

Toastr

Turnstile

Posledný sken: 20. júna 2026

Akčný plán

Opravte týchto 3 vecí ako prvé

Zoradené podľa dopadu na skóre — každá oprava posunie celkové hodnotenie nahor.

+15potenciálny zisk

63/100

Výkon

Váha: 25% · 9 prešlo · 4 upozornenia · 4 zlyhalo · 1 SPA (overte manuálne)

Čo sme zistili: 4.80s (good: <2.5s) — Core Web Vital FAILING

Prečo na tom záleží: LCP >4s fails Core Web Vitals — Google actively demotes these pages. Each 100ms improvement in LCP correlates with 1.7% higher conversion rate (Vodafone study).

Ako to opraviť: Urgent: your largest content element loads too slowly. 1) Preload hero image, 2) Convert to WebP/AVIF, 3) Serve from CDN, 4) Remove render-blocking JS before it, 5) Consider lazy loading all other images.

Dôkaz:PSI-lab· Spoľahlivosť: high

Fix with Performance module →

Čo sme zistili: 7.0 MB, 194 requests — too heavy!

Prečo na tom záleží: 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 to 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.

Dôkaz:PSI-lab· Spoľahlivosť: high

Get Performance Optimization →

Čo sme zistili: 663 KB wasted on unused code!

Prečo na tom záleží: 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.

Poznámka: Táto kontrola používa heuristickú detekciu a môže vrátiť aj falošné pozitíva. Odporúčame manuálne overenie.

Ako to opraviť: You're loading 663 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.

Dôkaz:PSI-lab· Spoľahlivosť: low

Čo sme zistili: Only 25% of 4 scripts optimized — most are render-blocking

Prečo na tom záleží: 3 render-blocking scripts can add 1-3 seconds to page load. Each synchronous script creates a sequential download-parse-execute chain.

Ako to 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.

Dôkaz:HTML-heuristic· Spoľahlivosť: high

Get Performance Optimization →

Čo sme zistili: 284ms (good: <200ms)

Prečo na tom záleží: TBT measures how long the main thread is blocked. During this time, clicks and taps don't respond — your store feels frozen. This directly impacts perceived quality.

Ako to opraviť: Reduce JavaScript execution: defer non-critical scripts, code-split large bundles, remove unused plugins. Third-party scripts (analytics, chat, ads) are often the biggest offenders.

Dôkaz:PSI-lab· Spoľahlivosť: high

Požiadať o audit rýchlosti

Čo sme zistili: Google Fonts detected without font-display

Prečo na tom záleží: Without font-display, custom fonts cause Flash of Invisible Text (FOIT) — text is completely hidden during font download. On slow connections this can last 3+ seconds.

Ako to opraviť: Add &display=swap to your Google Fonts URL, or add font-display: swap to your @font-face declarations.

Dôkaz:HTML-heuristic· Spoľahlivosť: high

Požiadať o audit rýchlosti

Čo sme zistili: no-store, no-cache, must-revalidate

Prečo na tom záleží: no-cache/no-store forces browsers to re-download resources on every visit. Repeat visitors load your entire site from scratch every time.

Ako to opraviť: Set appropriate cache headers: static assets should have max-age=31536000 with versioned filenames. HTML pages can use max-age=0 with ETag for revalidation.

Dôkaz:HTTP-header· Spoľahlivosť: high

Požiadať o audit rýchlosti

Čo sme zistili: Custom fonts detected without preload hints

Prečo na tom záleží: 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 to 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.

Dôkaz:HTML-heuristic· Spoľahlivosť: high

Požiadať o audit rýchlosti

8 problémov v kategórii Výkon. Je tu priestor na zlepšenie.

Váš e-shop zatiaľ nespĺňa podmienky pre odznak Zulien Score. Získajte skóre 80+!

📧 Pripomienky opätovného skenu

Raz mesačne vám napíšeme, kedy urobiť nový sken a sledovať vaše zlepšenia.

Súhlasím s Ochrana súkromia. Pošleme vám report a voliteľné upozornenia na opätovný sken.

🚀 Zlepšite svoje skóre

Naše PrestaShop moduly dokážu automaticky opraviť väčšinu týchto problémov.

Bezplatná 15-min konzultácia · Bez záväzku

Zdieľať a exportovať

Pripravení zlepšiť svoje skóre?

Opravte si sami

Prejdite si naše moduly a opravte problémy na 2 kliknutia.

Prejsť moduly Zulien

Nechajte to na nás

Opíšte váš cieľ a do 48 h vám pošleme cenovú ponuku. Bez telefonátu.

Získať cenovú ponuku

Odpoveď do 48 h · Bez telefonátu

Toto je automatizovaný heuristický odhad, nie profesionálny audit. Zistenia odrážajú verejne pozorovateľné signály v čase skenu a môžu obsahovať aj nesprávne nálezy.Prečítajte si o našej metodikeNahlásiť nepresnosťOdstrániť tento report

Zulien Score

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

75/100

Grade C

hetzner.truckershop.sk

Dátum auditu: 20. júna 2026

Platforma: PrestaShop

Online report: https://score.zulien.sk/r/hetzner.truckershop.sk

Executive summary

Chýb

Upozornení

144

Spolu kontrol

Skóre po kategóriách

Kategória	Skóre	Váha	Chyby	Upozornenia	OK
Výkon	63/100	25%	4	4	9
SEO	95/100	20%	0	3	19
Bezpečnosť	77/100	15%	1	4	10
Mobil	57/100	10%	1	7	9
AI pripravenosť	81/100	10%	0	19	20
GDPR	78/100	10%	1	4	9
Zraniteľnosť	75/100	10%	3	3	6

Kritické zistenia

Largest Contentful Paint (LCP)· Performance

LCP >4s fails Core Web Vitals — Google actively demotes these pages. Each 100ms improvement in LCP correlates with 1.7% higher conversion rate (Vodafone study).

Celková váha stránky· 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.

Nevyužitý kód (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.

Stratégia načítania skriptov· Performance

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

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.

Mobilný performance skóre· 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.

Google Consent Mode v2· GDPR

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.

CSRF ochrana formulárov· Vulnerability

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.

SPF záznam (e-mail security)· Vulnerability

Without SPF, anyone can send emails that appear to come from your domain. Since 2024, Google and Yahoo reject email from domains without SPF. Your transactional emails may land in spam.

DMARC policy (e-mail auth)· Vulnerability

Without DMARC, attackers can send perfectly spoofed emails as your brand. Since May 2025, Google, Yahoo, and Microsoft require DMARC for bulk senders. Missing DMARC = email deliverability problems.

Výkon

63/100

Váha: 25% · 9 OK · 4 upozornení · 4 chýb · spolu 18

Largest Contentful Paint (LCP)Zlyhalo

4.80s (good: <2.5s) — Core Web Vital FAILING

Prečo je to dôležité: LCP >4s fails Core Web Vitals — Google actively demotes these pages. Each 100ms improvement in LCP correlates with 1.7% higher conversion rate (Vodafone study).

Ako opraviť: Urgent: your largest content element loads too slowly. 1) Preload hero image, 2) Convert to WebP/AVIF, 3) Serve from CDN, 4) Remove render-blocking JS before it, 5) Consider lazy loading all other images.

Celková váha stránkyZlyhalo

7.0 MB, 194 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.

Nevyužitý kód (CSS + JS)Zlyhalo

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

Stratégia načítania skriptovZlyhalo

Only 25% of 4 scripts optimized — most are render-blocking

Prečo je to dôležité: 3 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.

Total Blocking Time (TBT)Upozornenie

284ms (good: <200ms)

Prečo je to dôležité: TBT measures how long the main thread is blocked. During this time, clicks and taps don't respond — your store feels frozen. This directly impacts perceived quality.

Ako opraviť: Reduce JavaScript execution: defer non-critical scripts, code-split large bundles, remove unused plugins. Third-party scripts (analytics, chat, ads) are often the biggest offenders.

Stratégia načítania fontovUpozornenie

Google Fonts detected without font-display

Prečo je to dôležité: Without font-display, custom fonts cause Flash of Invisible Text (FOIT) — text is completely hidden during font download. On slow connections this can last 3+ seconds.

Ako opraviť: Add &display=swap to your Google Fonts URL, or add font-display: swap to your @font-face declarations.

Cache-Control stratégiaUpozornenie

no-store, no-cache, must-revalidate

Prečo je to dôležité: no-cache/no-store forces browsers to re-download resources on every visit. Repeat visitors load your entire site from scratch every time.

Ako opraviť: Set appropriate cache headers: static assets should have max-age=31536000 with versioned filenames. HTML pages can use max-age=0 with ETag for revalidation.

Preload fontovUpozornenie

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.

Server response time (TTFB)Prešlo

24ms

First Contentful Paint (FCP)Prešlo

0.96s

Cumulative Layout Shift (CLS)Prešlo

0.058 — Core Web Vital ✓

Speed IndexPrešlo

2.01s

Kompresia textu (gzip/brotli)Prešlo

All text resources properly compressed

Resource hints (preload/preconnect)Prešlo

0 preload, 5 preconnect hint(s)

Lazy loadingPrešlo

87% of images use native lazy loading (232/267)

HTTP/3 (QUIC) podporaPrešlo

HTTP/3 enabled via Alt-Svc header

Počet CSS súborovPrešlo

3 CSS file(s) — well consolidated

Render-blokujúce zdrojeInfo

Not measured — PageSpeed did not return the render-blocking audit for this URL

Ako opraviť: Re-run the scan, or test directly at PageSpeed Insights. This metric needs a successful Lighthouse lab run.

SEO

95/100

Váha: 20% · 19 OK · 3 upozornení · 0 chýb · spolu 23

Optimalizácia formátov obrázkovUpozornenie

Only 11% next-gen formats — 237 legacy images remain

Prečo je to dôležité: WebP/AVIF images are 30-70% smaller than JPEG/PNG with the same quality. This directly improves page speed, LCP, and mobile experience.

Ako opraviť: Convert remaining JPEG/PNG images to WebP (30-50% smaller) or AVIF (50-70% smaller). Use <picture> element for browser fallback.

Prázdne / mŕtve odkazyUpozornenie

10 dead links (7 empty, 3 hash-only, 0 javascript:void)

Prečo je to dôležité: Dead links waste crawl budget and confuse search engines. They also create poor user experience — users click expecting navigation and nothing happens.

Ako opraviť: Replace empty href='', href='#', and href='javascript:void(0)' with actual URLs. If interactive, use <button> instead of <a>.

Nefunkčné src obrázkovUpozornenie

1 image(s) with empty src attribute

Prečo je to dôležité: Empty src attributes cause extra HTTP requests to the page URL, waste bandwidth, and show broken image icons to users.

Ako opraviť: Fix images with empty src=''. Either add proper URLs or use loading='lazy' with valid data-src for lazy-loaded images.

Meta TitlePrešlo

47 chars — "TRUCKERSHOP.SK - Vybavenie pre nákladnú dopravu"

Meta popisPrešlo

157 chars

H1 nadpisPrešlo

"TRUCKERSHOP.SK – Vybavenie, doplnky a náhradné diely pre kam…"

Štruktúra obsahu (H2 nadpisy)Prešlo

8 H2 subheadings found

Open Graph tagyPrešlo

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

Open Graph Image FormatPrešlo

image/jpeg

Twitter/X CardsPrešlo

Card type: summary_large_image

Kanonická URLPrešlo

https://hetzner.truckershop.sk/

Štruktúrované dáta (JSON-LD)Prešlo

6 block(s): Organization, ImageObject, WebPage, WebSite

robots.txtPrešlo

Present, references sitemap

XML sitemapPrešlo

Found with ~105+ URLs

HTML atribút jazykaPrešlo

lang="sk-SK"

Alt atribúty obrázkovPrešlo

100% of 267 images have alt text

FaviconPrešlo

Favicon detected

Sémantická HTML štruktúraPrešlo

5/6 semantic elements: <article>, <nav>, <main>, <header>, <footer>

Hĺbka obsahuPrešlo

3066 words — sufficient content

Hlboká hierarchia nadpisovPrešlo

H2: 8, H3: 6 — well-structured content

Interné prelinkovaniePrešlo

351 internal links — strong site navigation

Základy prístupnostiPrešlo

3/4 a11y signals: 157 ARIA roles, 207 ARIA labels, lang="sk-SK"

Pomer textu k HTMLInfo

3% ratio but 3066 words — content is substantial; the low ratio is markup/inline-JS bloat, not thin content

Prečo je to dôležité: Text-to-HTML ratio is only a thin-content signal when actual word count is also low. With 500+ words, search engines have plenty to rank on.

Ako opraviť: Your text content is sufficient. To raise the ratio, move inline <script>/<style> to external files and trim template bloat — this is a performance/cleanliness win, not a content gap.

Bezpečnosť

77/100

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

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.

DNSSEC podpísanie zónyUpozornenie

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 záznam (autorizácia CA)Upozornenie

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.

Subresource Integrity (SRI)Upozornenie

Only 0/2 SRI-eligible third-party scripts have integrity hashes (1 auto-updating provider script(s) excluded — SRI not applicable)

Prečo je to dôležité: Without SRI, if a version-pinned 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' to version-pinned third-party <script> tags (use srihash.org). Auto-updating provider scripts (analytics, payment SDKs, consent tools) are correctly excluded — they can't use SRI.

CDN / WAF ochranaUpozornenie

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 certifikátPrešlo

Valid HTTPS connection established

HTTP → HTTPS presmerovaniePrešlo

HTTP properly redirects to HTTPS

HSTS (Strict-Transport-Security)Prešlo

max-age=31536000, includeSubDomains

Ochrana pred clickjackingomPrešlo

X-Frame-Options: SAMEORIGIN

X-Content-Type-OptionsPrešlo

nosniff

Referrer-PolicyPrešlo

strict-origin-when-cross-origin

Permissions-PolicyPrešlo

geolocation=(), microphone=(), camera=()

Bezpečnostné flagy cookiesPrešlo

2 cookie(s) — all have Secure, HttpOnly, SameSite

Odhalenie technológiePrešlo

Server identity hidden

security.txt (RFC 9116)Prešlo

Present at /.well-known/security.txt

Iframe sandboxingInfo

1 trusted provider embed(s) without sandbox — expected (sandbox would break YouTube/Maps/Stripe/reCAPTCHA)

Bezpečnostný prefix cookiesInfo

2 session cookie(s) already have Secure + HttpOnly + SameSite; adding the __Host- prefix is a cosmetic hardening nicety

Prečo je to dôležité: With Secure, HttpOnly and SameSite already set, the prefix adds only host-only enforcement — low marginal benefit.

Ako opraviť: Optional: rename to __Host-session (Secure; Path=/; no Domain) for defence-in-depth against subdomain cookie injection.

Mobil

57/100

Váha: 10% · 9 OK · 7 upozornení · 1 chýb · spolu 19

Mobilný performance skóreZlyhalo

42/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.

Veľkosť tap cieľaUpozornenie

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.

Čitateľnosť veľkosti písmaUpozornenie

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 funkcieUpozornenie

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.

Typy form inputovUpozornenie

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.

Pretečenie textuUpozornenie

No word-break/overflow-wrap CSS detected

Prečo je to dôležité: Long strings without word-break cause horizontal overflow on mobile — the #1 cause of 'content wider than viewport' failures. German/Finnish compound words and URLs are common culprits.

Ako opraviť: Add 'overflow-wrap: break-word' to your body or main content container. Without it, long URLs, product SKUs, or German compound words can break mobile layouts.

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.

Hierarchia nadpisov (WCAG 1.3.1)Upozornenie

Preskočené úrovne: h1→h3

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.

Viewport konfiguráciaPrešlo

width=device-width, initial-scale=1

Obsah sa zmestí do viewportuPrešlo

No horizontal scrolling needed

Responsívny dizajnPrešlo

Media queries detected

Theme colorPrešlo

theme-color meta tag present

Mobilná navigácia (sémantická)Prešlo

<nav> element present — proper navigation landmark

Responsívne obrázky (srcset)Prešlo

58 image(s) use srcset for responsive sizing

Payment Methods DetectedPrešlo

1 method(s): Stripe

Form labels (WCAG 3.3.2)Prešlo

31/31 inputs majú label

Kvalita textu odkazov (WCAG 2.4.4)Prešlo

Všetky odkazy majú popisný text

Express checkout (Apple Pay + Google Pay)Info

Apple Pay / Google Pay nedetekované na homepage — express checkout sa zvyčajne zobrazí až v košíku/checkoute

Prečo je to dôležité: Mobile conversion pri express checkout je +15-25 % oproti klasickej karte. V SK/CZ trend roku 2025+. (Sken vidí iba homepage, takže toto je hint, nie verdikt.)

Ako opraviť: Ak express checkout nemáš, pridaj Apple Pay + Google Pay cez Stripe/Adyen/Mollie. Biometric auth = -1 click checkout = vyšší conversion.

Lokálne SK/CZ platbyInfo

Žiadna SK/CZ local payment metóda nedetekovaná na homepage — bankové tlačidlá/QR sa zvyčajne zobrazia až v checkoute

Prečo je to dôležité: SK/CZ shop bez bankových tlačidiel a QR platby = masívny cart abandonment. Priemerný SK e-shop má 6-8 payment metód. (Sken vidí iba homepage — over manuálne v checkoute.)

Ako opraviť: Ak SK/CZ local platby nemáš, integruj GoPay alebo ComGate — obe podporujú Tatra Pay, VÚB Pay, ČSOB Pay, Raiffeisen, QR platba v jednom API. Alternatívne Barion pre CZ trh.

AI pripravenosť

81/100

Váha: 10% · 20 OK · 19 upozornení · 0 chýb · spolu 40

FAQ schema (priame AI odpovede)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).

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.

Štruktúrovaný obsah (zoznamy & tabuľky)Upozornenie

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

Signály čerstvosti obsahuUpozornenie

Visible date found but not in structured data

Prečo je to dôležité: 76.4% of ChatGPT's top 1000 cited pages were updated within 30 days. AI-cited content is 25.7% fresher than traditional organic results. Freshness signals tell AI your content is current and reliable.

Ako opraviť: Add both: 1) dateModified and datePublished in your Article/Product JSON-LD schema, 2) A visible 'Last updated: [date]' on the page. Both signals reinforce content freshness for AI.

Signály autorskej expertízy (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.

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. Tip: validate your Heureka / Zboží / Glami / Merchant feeds for free with Mergado's audit.

Heureka XML feed (SK/CZ marketplace)Upozornenie

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.

Extrahovateľné bloky odpovedíUpozornenie

51 paragraphs, avg 15 words — too short for citation

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.

Ako opraviť: Optimal paragraphs for AI citation are 40-80 words. Break long paragraphs into focused, self-contained answer blocks. Each should make one clear point that AI can extract and quote.

Optimalizácia dĺžky sekciíUpozornenie

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

Canonical tag pre AI deduplikáciuUpozornenie

Canonical points to different URL: https://hetzner.truckershop.sk/

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.

Čitateľnosť obsahu pre 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.

Kvalita alt textov pre AIUpozornenie

76% good, 63 poor, 1 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'.

Expertné citácieUpozornenie

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 oprávnenia)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 pripravenosťUpozornenie

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.

Politika prístupu AI botovPrešlo

Explicitly allowed: GPTBot, ChatGPT-User, anthropic-ai, ClaudeBot, PerplexityBot

llms.txt (AI site descriptor)Prešlo

Valid llms.txt with 2133 chars — proper format with H1, summary

llms-full.txt (kompletný AI content)Prešlo

Full content file found (4 KB) — comprehensive AI feed

Prístupnosť obsahu pre AIPrešlo

3066 words in raw HTML (3.2% text ratio) — readable by AI crawlers without executing JS

Základ štruktúrovaných dátPrešlo

6 JSON-LD blocks with 8 schema types: Organization, ImageObject, WebPage, WebSite, SearchAction, AggregateRating

Organization schema + entity linkingPrešlo

Organization found with 5 sameAs links — strong entity identity

Site Search schema (SearchAction)Prešlo

WebSite SearchAction configured — AI can search your store

Hĺbka obsahu pre AIPrešlo

3066 words — rich content for AI analysis and citation

Answer-first formát obsahuPrešlo

First paragraph: 159 words — good content density above the fold

Hierarchia nadpisov pre AIPrešlo

Proper structure: 1 H1 → 8 H2s → 6 H3s — clear content outline

Sémantická HTML štruktúraPrešlo

5/6 semantic elements: <article>, <nav>, <main>, <header>, <footer>

Jasnosť entity & brand signályPrešlo

OG tags complete + 5 sameAs links: Facebook, Instagram, YouTube

Reviews & Ratings schemaPrešlo

AggregateRating/Review data found — social proof for AI

Prítomnosť štatistík & dátPrešlo

6 data points found — strong citation magnet

Nadpisy vo Q&A formátePrešlo

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

Hustota interných odkazovPrešlo

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

Pripravenosť na Knowledge GraphPrešlo

3/4 entity signals — strong Knowledge Graph presence

Pomer obsahu k boilerplatePrešlo

70% of text in <main>/<article> — clean content signal

AggregateRating schemaPrešlo

Review aggregate rating schema present

Customer Reviews — AggregatePrešlo

1 source: AggregateRating schema — ★ 4.9 · 123 reviews

Prečo je to dôležité: Multi-source reviews with published counts compound trust: AI assistants (ChatGPT/Perplexity) and Google SGE cite shops with verifiable AggregateRating schema first; SK/CZ buyers cross-check Heureka against Trustpilot before purchase.

Product Schema CompletenessInfo

No Product schema on this homepage — Product schema lives on product detail pages, which this single-URL scan didn't visit

Prečo je to dôležité: Product schema only belongs on product pages, so its absence on this page is expected — not a defect. Scan a product URL to evaluate it.

Ako opraviť: To audit Product schema, run the scan on a product detail URL. On product pages add: name, description, image, offers (price, priceCurrency, availability), brand, sku, aggregateRating.

GDPR

78/100

Váha: 10% · 9 OK · 4 upozornení · 1 chýb · spolu 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

Zásady cookiesUpozornenie

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.

Právo na vymazanie (GDPR Art. 17)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.

Mechanizmus odvolania súhlasuUpozornenie

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.

Platnosť cookies (compliance)Upozornenie

1 cookie(s) with >1 year expiry

Prečo je to dôležité: French CNIL and other EU DPAs recommend maximum 13-month cookie lifetime. Excessive cookie durations violate data minimization (GDPR Art. 5c). Belgian DPA fined IAB €250K partly for disproportionate cookie retention.

Ako opraviť: Reduce cookie lifetimes to maximum 13 months (CNIL recommendation) or 6 months for marketing cookies. Session cookies should expire when the browser closes.

Cookie consent banner (CMP)Prešlo

CookieYes detected

Tracking skripty & súhlasPrešlo

1 tracker(s) detected with CMP: Google Analytics/GTM

Stránka ochrany súkromiaPrešlo

//hetzner.truckershop.sk/content/2-ochrana-osobnych-udajov

Právny kontakt / impressumPrešlo

//hetzner.truckershop.sk/content/4-o-nas

Obchodné podmienkyPrešlo

//hetzner.truckershop.sk/content/3-obchodne-podmienky

Šifrovanie dát (žiadny mixed content)Prešlo

All resources loaded over HTTPS

Zdieľanie dát s treťou stranouPrešlo

3 third-party domain(s)

Newsletter súhlasPrešlo

Newsletter form with consent mechanism detected

Kontakt na DPOPrešlo

DPO / data protection contact found

Zraniteľnosť

75/100

Váha: 10% · 6 OK · 3 upozornení · 3 chýb · spolu 13

CSRF ochrana formulárovZlyhalo

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

SPF záznam (e-mail security)Zlyhalo

Prečo je to dôležité: Without SPF, anyone can send emails that appear to come from your domain. Since 2024, Google and Yahoo reject email from domains without SPF. Your transactional emails may land in spam.

Ako opraviť: Add an SPF TXT record to your DNS: v=spf1 include:_spf.google.com ~all (adjust for your email provider). This tells receiving servers which IPs can send email for your domain.

DMARC policy (e-mail auth)Zlyhalo

Prečo je to dôležité: Without DMARC, attackers can send perfectly spoofed emails as your brand. Since May 2025, Google, Yahoo, and Microsoft require DMARC for bulk senders. Missing DMARC = email deliverability problems.

Ako opraviť: Add a DMARC TXT record at _dmarc.yourdomain.com: v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com — start with quarantine, then move to reject.

Odhalené source mapyUpozornenie

JavaScript source maps (.js.map) are publicly accessible

Prečo je to dôležité: Source maps reveal your original source code, variable names, comments, and application logic. Attackers use this to find vulnerabilities, API keys in code, and understand your authentication flow.

Ako opraviť: Remove source maps from production or block access via server config. In Vite/Webpack: set sourcemap: false for production builds.

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.

Inline event handlersUpozornenie

30 inline event handlers (onclick, onmouseover, etc.)

Prečo je to dôležité: Inline event handlers are a legacy pattern that prevents Content Security Policy enforcement. They also make XSS attacks easier — injected HTML attributes can execute JavaScript immediately.

Ako opraviť: Move inline event handlers to external JavaScript files using addEventListener(). Inline handlers prevent proper CSP implementation (require 'unsafe-inline') and increase XSS attack surface.

Odhalenie verzie CMSPrešlo

No generator tag — CMS identity hidden

Odhalené citlivé súboryPrešlo

.env, .git, composer.json — all properly blocked

Odhalený inštalačný scriptPrešlo

No /install/ or /setup/ paths accessible

Directory listingPrešlo

Disabled — file structure hidden

Admin panel na predvolenej URLPrešlo

Not found at common paths (/admin, /wp-admin, /administrator, /backoffice)

Debug mód / odhalenie chýbPrešlo

No debug indicators found in page output

Email InfrastructureInfo

No MX records — domain does not receive email

Ď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/hetzner.truckershop.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