Scanned on July 28, 2026
Your site has fundamental security and accessibility issues. Prioritize adding HTTPS protection (HSTS) across all pages. On the bright side, your SEO and GDPR compliance are solid.
Sorted by score impact — each fix moves your overall grade up.
Weight: 25% · 4 passed · 10 warnings · 2 failed · 1 SPA (verify manually)
Why it matters: Pages over 3 MB take 12+ seconds on 3G. The average e-commerce page is around 2 MB — you're well above that. Even small latency increases measurably reduce sales.
How to fix: Critical: your page is over 3 MB. 1) Convert all images to WebP/AVIF, 2) Lazy load everything below the fold, 3) Remove unused plugins, 4) Combine and minify CSS/JS, 5) Enable brotli compression.
Evidence: PSI-lab · Confidence: high
What we found: 4.1 MB, 334 requests — too heavy!
Why it matters: Pages over 3 MB take 12+ seconds on 3G. The average e-commerce page is around 2 MB — you're well above that. Even small latency increases measurably reduce sales.
Why it matters: Over 200 KB of unused code significantly slows parsing and execution. This is one of the easiest performance wins — removing dead code requires no trade-offs.
How to fix: You're loading 1109 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.
Evidence: PSI-lab · Confidence: low
What we found: 1109 KB wasted on unused code!
Why it matters: Over 200 KB of unused code significantly slows parsing and execution. This is one of the easiest performance wins — removing dead code requires no trade-offs.
Note: This check uses heuristic detection and may produce false positives. Manual verification recommended.
Why it matters: LCP is a Core Web Vital that directly impacts Google rankings. Sites failing LCP are demoted in search results. The most common cause of slow LCP is unoptimized hero images.
How to fix: Optimize your largest element (usually hero image or product image): preload it with <link rel='preload'>, use WebP/AVIF format, set explicit width/height, and serve from CDN.
Evidence: PSI-lab · Confidence: high
What we found: 2.61s (good: <2.5s) — Core Web Vital
Why it matters: LCP is a Core Web Vital that directly impacts Google rankings. Sites failing LCP are demoted in search results. The most common cause of slow LCP is unoptimized hero images.
Why it matters: 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.
How to fix: 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.
Evidence: PSI-lab · Confidence: high
What we found: 560ms (good: <200ms)
Why it matters: 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.
Why it matters: Speed Index captures the overall visual loading experience. A slow Speed Index means users watch content load piece by piece instead of seeing a complete page.
How to fix: Speed Index measures visual completeness over time. Improve it by: prioritizing above-fold content, preloading critical resources, and minimizing render-blocking assets.
Evidence: PSI-lab · Confidence: high
What we found: 3.56s (good: <3.4s)
Why it matters: Speed Index captures the overall visual loading experience. A slow Speed Index means users watch content load piece by piece instead of seeing a complete page.
Why it matters: Preconnect saves 100-500ms per third-party origin by establishing connections early. Preload starts downloading critical resources before the browser discovers them in CSS/JS.
How to fix: Add resource hints: <link rel='preconnect' href='https://fonts.googleapis.com'> for third-party origins, <link rel='preload' as='image' href='hero.webp'> for critical resources.
Evidence: HTML-heuristic · Confidence: high
Why it matters: Preconnect saves 100-500ms per third-party origin by establishing connections early. Preload starts downloading critical resources before the browser discovers them in CSS/JS.
Why it matters: Without lazy loading, ALL images download on page load — even those never scrolled to. On a product page with 20 images, lazy loading can save most of the initial download.
How to fix: Add loading='lazy' to all images below the fold. Keep the hero/LCP image eager-loaded. Native lazy loading is supported by all modern browsers.
Evidence: HTML-heuristic · Confidence: high
What we found: 606 images without lazy loading
Why it matters: Without lazy loading, ALL images download on page load — even those never scrolled to. On a product page with 20 images, lazy loading can save most of the initial download.
Why it matters: no-cache/no-store forces browsers to re-download resources on every visit. Repeat visitors load your entire site from scratch every time.
How to fix: 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.
Evidence: HTTP-header · Confidence: high
What we found: no-store, no-cache, must-revalidate
Why it matters: no-cache/no-store forces browsers to re-download resources on every visit. Repeat visitors load your entire site from scratch every time.
Why it matters: Synchronous scripts block HTML parsing — the browser stops rendering until each script downloads and executes. Async/defer allows parallel downloading without blocking.
How to fix: Add 'defer' to scripts that don't need to run immediately, 'async' for independent scripts. Use type='module' for modern ES modules. Only critical inline scripts should be synchronous.
Evidence: HTML-heuristic · Confidence: high
What we found: Only 43% of 7 scripts use async/defer
Why it matters: Synchronous scripts block HTML parsing — the browser stops rendering until each script downloads and executes. Async/defer allows parallel downloading without blocking.
Why it matters: Each render-blocking CSS file adds network latency. Consolidating CSS from 8 to 2 files can save 200-400ms on first load.
How to fix: Consolidate CSS files by bundling them into 1-3 files. Each CSS file is a separate HTTP request that blocks rendering until downloaded.
Evidence: HTML-heuristic · Confidence: high
What we found: 7 CSS files loaded
Why it matters: Each render-blocking CSS file adds network latency. Consolidating CSS from 8 to 2 files can save 200-400ms on first load.
Why it matters: Render-blocking CSS delays first paint. Inlining critical CSS eliminates the render-blocking round trip — the biggest FCP improvement for CSS-heavy sites.
How to fix: 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"'>.
Evidence: PSI-lab · Confidence: high
What we found: 7 CSS files without critical CSS extraction
Why it matters: Render-blocking CSS delays first paint. Inlining critical CSS eliminates the render-blocking round trip — the biggest FCP improvement for CSS-heavy sites.
Why it matters: Third-party connections require DNS lookup, TCP handshake, and TLS negotiation. Preconnect performs these in parallel with HTML parsing, saving 100-300ms per origin.
How to fix: Add <link rel='preconnect'> for key third-party domains: sub3.tpd.sk, www.google.com, cdn.luigisbox.com. Preconnect saves 100-300ms per domain by starting DNS+TCP+TLS early.
Evidence: PSI-lab · Confidence: high
What we found: 4 external domains without preconnect
Why it matters: Third-party connections require DNS lookup, TCP handshake, and TLS negotiation. Preconnect performs these in parallel with HTML parsing, saving 100-300ms per origin.
How to fix: Re-run the scan, or test directly at PageSpeed Insights. This metric needs a successful Lighthouse lab run.
Evidence: PSI-lab · Confidence: high
Your store doesn't qualify for the Zulien Score Badge yet. Score 80+ to earn it!
Your store is losing customers every day. The issues above are costing you sales.
Hands-on review by our team: we identify root causes, prioritize fixes, and hand you an action plan. We'll send a tailored quote within 48h.
| Kategória | Skóre | Váha | Chyby | Upozornenia | OK |
|---|---|---|---|---|---|
| Performance | 58/100 | 25% | 2 | 10 | 4 |
| SEO | 73/100 | 20% | 3 | 6 | 14 |
| Security | 53/100 | 15% | 3 | 9 | 6 |
| Mobile | 58/100 | 10% | 2 | 11 | 4 |
| AI Readiness | 58/100 | 10% | 6 | 14 | 10 |
| GDPR | 74/100 | 10% | 0 | 5 | 5 |
| Vulnerability | 59/100 | 10% | 3 | 5 | 8 |
| Accessibility | 33/100 | — | 3 | 3 | 2 |
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/andreashop.sk