Below Average

Score Report

www.muziker.sk

Scanned on June 7, 2026

Unknown
Font Awesome
Swiper
Stimulus
Turbo
Cloudflare
Last scanned: June 7, 2026
Action plan

Fix these 3 things first

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

+18potential gain

Performance

Weight: 25% · 12 passed · 3 warnings · 3 failed

What we found: 652ms (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.

What we found: 0.271 (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.

What we found: 746 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 ${unusedTotalKB} 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.

What we found: 2.6 MB, 162 requests (optimal: <1.5 MB, <50 req)

Why it matters: A 3 MB page takes 6+ seconds on 3G mobile. Over 50% of global e-commerce traffic is mobile — heavy pages lose customers in emerging markets and poor connectivity areas.

How to fix: Reduce page weight: compress images to WebP (saves 30-50%), enable text compression (gzip/brotli), lazy load below-fold images, remove unused CSS/JS.

What we found: no-store

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.

What we found: Custom fonts detected without preload hints

Why it matters: 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.

How to fix: 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.

6 issues found in Performance. Room for improvement.

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