Below Average

Score Report

pilulka.sk

Scanned on July 28, 2026

Magento
Vue.js
Nuxt.js
Font Awesome
PhotoSwipe
Vite
Company:Pilulka Lékárny a.s.· NACE 47730
NIS2: out of scope
Risk:30/100medium
Credit:B
Shell address
Full company profile →
Last scanned: July 28, 2026
AI verdict

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.

Not subject to NIS2 cybersecurity duties.Based on NACE sector + company size, Article 21 compliance is not mandatory. Security best practices still recommended.
Supplying a NIS2-regulated company?Even outside direct scope you may inherit supply-chain duties — regulated companies cascade them to suppliers by contract (security, incident reporting, encryption). ICT and managed-service providers are in scope regardless of size.
Check supplier obligations Legal basis: NIS2 Art. 21 · CZ 264/2025 §11 · NIS2 Art. 21(2)(d)
Possible IČO mismatch

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.

Action plan

Fix these 3 things first

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

+15potential gain

Performance

Weight: 25% · 7 passed · 5 warnings · 5 failed · 1 SPA (verify manually)

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.

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

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

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

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

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

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

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

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: 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: 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: 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: 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

10 issues found in Performance. This is hurting your store.

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

📧 Re-scan reminders

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

🚀 Improve your score

Our PrestaShop modules can fix most of these issues automatically.

Free 15-min consultation · No commitment

Share & Export

This is an automated heuristic estimate, not a professional audit. Findings reflect publicly observable signals at scan time and may include false positives.Learn about our methodologyReport inaccuracyRemove this report