Eliminate Render-Blocking CSS Resources

How to optimize zadom.hr

Generic SiteScore: 66/100Analyzed December 2025

Eliminate Render-Blocking CSS Resources

High Impact+12 points estimated

Why It Matters

CSS files are blocking page rendering for 790ms, directly delaying First Contentful Paint and user experience.

How to Fix

Inline critical above-the-fold CSS directly in the HTML head. Use media='print' onload='this.media="all"' to defer non-critical CSS like quill.snow.css. Consider splitting the large compresed.css (84KB) into critical and non-critical portions.

0Needs Improvement

What This Score Means

A score of 66 falls in the "Needs Improvement" range (50-89). While it is better than poor (0-49), you should aim for 90+ to provide an optimal user experience and maximize SEO benefits.

This site is slower than approximately 35% of similar sites. The main issues affecting performance are image optimization, JavaScript execution time, and layout stability.

Addressing these issues could improve your conversion rate by 15-20% and boost your search engine rankings.

Core Web Vitals Analysis

LCP

Largest Contentful Paint

7.6s
Poor

Good: < 2.5s

Measures how long it takes for the main content to appear on screen

INP

Interaction to Next Paint

181ms
Good

Good: < 200ms

Measures how quickly the page responds to user interactions

CLS

Cumulative Layout Shift

0.01
Good

Good: < 0.1

Measures visual stability - how much content shifts during page load

AI Performance Analysis

This website has poor performance with a score of 66/100, primarily due to extremely slow loading times - it takes 7.6 seconds for the largest content to appear on screen. The biggest issue is a redirect from the non-www to www version that wastes 780ms before the page even starts loading, combined with massive amounts of unused CSS (104 KiB) and JavaScript (519 KiB) that aren't needed for the initial page view. The site also serves oversized images that could be reduced by 841 KiB using modern formats like WebP and proper sizing. Fixing the redirect, removing unused code, and optimizing images could dramatically improve loading speeds and boost the performance score by 30+ points.

Other Optimization Recommendations

Remove Unused CSS and JavaScript

High Impact+18 points estimated

Why It Matters:

1MB of unused code is downloaded unnecessarily, wasting 1050ms and slowing LCP by 900ms.

How to Fix:

Use PurgeCSS to remove 96% unused CSS from compresed.css (80KB savings). Tree-shake JavaScript bundles to eliminate 519KB unused code from vendors~app.bundle.js. Consider code splitting to load only necessary components per page.

Fix Redirect Chain Performance

Medium Impact+8 points estimated

Why It Matters:

Page redirect from zadom.hr to www.zadom.hr wastes 780ms before content loading even begins.

How to Fix:

Update all internal links to point directly to https://www.zadom.hr/. Configure server redirect to be a 301 permanent redirect. Consider implementing HSTS headers to force HTTPS without redirects for returning visitors.

Want to Analyze YOUR Website?

Get AI-powered performance insights with actionable fixes in 30 seconds

More Generic Speed Tests

Generic Performance Resources

Frequently Asked Questions

Keep Your Site Fast After Optimization

Once your site is optimized, maintain that speed. Use DeployHQ for zero-downtime, automated deployments—so performance fixes and updates go live safely every time, without breaking your site.

Explore DeployHQ →Trusted by engineering teams shipping high-performance sites