Scanned on July 28, 2026
Your store has solid foundations, but important gaps remain. Prioritize adding Open Graph tags and XML sitemap to improve search visibility. Security and SEO are your strongest areas.
The IČO in your site footer (03615278) differs from the IČO our autocomplete found for the domain (47235225). Often a copy-pasted template footer or a recent legal entity change — verify the IČO in your footer matches your actual operating entity. Informational only, doesn't affect score.
Sorted by score impact — each fix moves your overall grade up.
Weight: 25% · 7 passed · 5 warnings · 5 failed · 1 SPA (verify manually)
Why it matters: TBT over 600ms means your page is unresponsive for over half a second. Users who can't interact within 100ms perceive the site as broken. This kills conversions.
How to fix: Critical: audit all JavaScript. 1) Remove unused plugins/modules, 2) Defer analytics and chat widgets, 3) Code-split large bundles, 4) Move heavy computation to web workers.
Evidence: PSI-lab · Confidence: high
What we found: 608ms (good: <200ms)
Why it matters: TBT over 600ms means your page is unresponsive for over half a second. Users who can't interact within 100ms perceive the site as broken. This kills conversions.
Why it matters: CLS >0.25 fails Core Web Vitals. Users experience constant content jumping — extremely frustrating on mobile where accidental clicks lead to unwanted purchases or page changes.
How to fix: Urgent layout stability issues. 1) Add width/height to all <img> and <video>, 2) Reserve space for ads with min-height, 3) Use font-display: swap for web fonts, 4) Don't dynamically inject content above visible area.
Evidence: PSI-lab · Confidence: high
What we found: 0.453 (good: <0.1) — Core Web Vital FAILING
Why it matters: CLS >0.25 fails Core Web Vitals. Users experience constant content jumping — extremely frustrating on mobile where accidental clicks lead to unwanted purchases or page changes.
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.5 MB, 199 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 419 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: 419 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: Each CSS file blocks rendering. With 22 files, the browser must download all of them before painting anything. This can add 1-2+ seconds on mobile networks.
How to fix: Bundle your CSS files into 1-3 files maximum. Use a build tool (Webpack, Vite, Gulp) to concatenate and minify. Critical CSS should be inlined, the rest deferred.
Evidence: HTML-heuristic · Confidence: high
What we found: 22 CSS files — too many!
Why it matters: Each CSS file blocks rendering. With 22 files, the browser must download all of them before painting anything. This can add 1-2+ seconds on mobile networks.
Why it matters: TTFB is the foundation — every other metric is delayed by a slow server. A 200ms vs 600ms TTFB means 400ms added to FCP, LCP, and everything else.
How to fix: Optimize server response: enable opcode caching (OPcache), add Redis/Memcached for database caching, use a CDN. Check slow database queries.
Evidence: PSI-lab · Confidence: high
What we found: 525ms (optimal: <200ms)
Why it matters: TTFB is the foundation — every other metric is delayed by a slow server. A 200ms vs 600ms TTFB means 400ms added to FCP, LCP, and everything else.
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-cache
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: 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: 22 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: sdp-api.lnd.bz, translate.google.com, pilulkask.vshcdn.net. 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.
Why it matters: Large inline scripts cannot be cached separately — they're re-downloaded with every page load. Moving them to external files with defer enables HTTP caching and parallel downloads.
How to fix: Move large inline scripts to external files. Inline JS over 100 KB inflates HTML, prevents caching, and blocks the parser. External files can be cached, compressed, and deferred.
Evidence: PSI-lab · Confidence: high
What we found: 770 KB of inline JavaScript
Why it matters: Large inline scripts cannot be cached separately — they're re-downloaded with every page load. Moving them to external files with defer enables HTTP caching and parallel downloads.
How to fix: 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 | 45/100 | 25% | 5 | 5 | 7 |
| SEO | 71/100 | 20% | 3 | 9 | 13 |
| Security | 71/100 | 15% | 1 | 8 | 7 |
| Mobile | 49/100 | 10% | 2 | 8 | 6 |
| AI Readiness | 60/100 | 10% | 5 | 19 | 12 |
| GDPR | 66/100 | 10% | 1 | 8 | 6 |
| Vulnerability | 58/100 | 10% | 5 | 6 | 9 |
| Accessibility | 59/100 | — | 1 | 3 | 4 |
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/pilulka.sk