LCP
Largest Contentful Paint
25.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Hero Images Delivery
How to optimize mudita.com
Optimize Hero Images Delivery
High Impact+25 points estimated
Why It Matters
Images waste 4.2MB with poor compression and oversized dimensions, delaying LCP by 7.3 seconds.
How to Fix
Reduce image quality from q=100 to q=75-80 in Contentful settings. Generate responsive image sizes (372px, 640px, 1024px) instead of serving 670x670 images at 372px display size. Enable automatic WebP optimization with proper fallbacks for older browsers.
0Poor
What This Score Means
A score of 45 falls in the "Poor" 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
INP
Interaction to Next Paint
253ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
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 45/100, indicating significant issues that need immediate attention. The biggest problem is excessive unused JavaScript (552 KiB) combined with oversized, unoptimized images that are causing extremely slow loading times - your Largest Contentful Paint takes a painful 25.9 seconds, which will frustrate users and hurt search rankings. The site is loading unnecessary code from libraries like react-hook-form and pako compression, while images are being served at much higher resolutions than needed and with poor compression. Removing unused JavaScript, properly sizing and compressing images, and implementing better caching could potentially improve your performance score by 30+ points and reduce loading times by over 10 seconds.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+18 points estimatedWhy It Matters:
552KB of unused JavaScript blocks rendering for 3.3 seconds and delays user interactions.
How to Fix:
Code-split React components to load only required functionality per page. Remove unused form libraries like react-hook-form from non-form pages. Defer third-party scripts (GTM, Omniconvert) using async/defer attributes or load them after user interaction.
Fix Render Blocking Resources
Medium Impact+12 points estimatedWhy It Matters:
Critical resources block initial page render for 1.2 seconds, preventing users from seeing content.
How to Fix:
Move Omniconvert script to load asynchronously after page load. Inline critical CSS for above-the-fold content. Use font-display: swap for Google Fonts and preload the most important font files (Montserrat 500) with rel=preload.
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
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Generic Speed Tests
Generic Performance Resources
Optimize Image Dimensions and Caching
Oversized images waste 263KB and poor cache headers force unnecessary re-downloads.
Fix Multiple Page Redirects
The redirect chain from pulumi.com to www.pulumi.com adds 780ms delay to every Core Web Vital.
Eliminate Render-Blocking CSS Resources
CSS files are blocking page rendering for 4.8 seconds, severely delaying both FCP and LCP.
Remove Unused CSS and JavaScript
96% of your CSS (163 KiB) and significant JavaScript (114 KiB) are unused, wasting bandwidth and blocking rendering.