Average

Score Report

kolibahoreca.sk

Scanned on July 2, 2026

WordPress
jQuery
Font Awesome
Swiper
Webpack
Vite
Company:KOLIBA HORECA s.r.o.· NACE 8299
NIS2: out of scope
Risk:30/100medium
Credit:E
VAT registered
Full company profile →
Last scanned: July 2, 2026
AI verdict

Your site has a solid foundation but needs stronger security measures. Priority: enable HTTPS protection (HSTS) and security headers immediately. Your SEO and GDPR compliance are strong points.

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 · SK 366/2024 §21 · NIS2 Art. 21(2)(d)
Action plan

Fix these 3 things first

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

+15potential gain

Performance

Weight: 25% · 11 passed · 3 warnings · 2 failed · 2 SPA (verify manually)

What we found: Only 11% of 18 scripts optimized — most are render-blocking

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

How to fix: 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.
Evidence:HTML-heuristic· Confidence: high

What we found: 30 CSS files — too many!

Why it matters: Each CSS file blocks rendering. With 30 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: 1.9 MB, 72 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.
Evidence:PSI-lab· Confidence: high

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.
Evidence:HTML-heuristic· Confidence: high

What we found: 30 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

5 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