Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize store.mudita.com
Document latency of 5.3 seconds indicates severe server performance issues that delay all content loading.
Optimize your Magento server configuration and database queries. Implement server-side caching (Redis/Varnish). Consider upgrading hosting infrastructure or using a CDN. Remove the unnecessary redirect from www.store.mudita.com to store.mudita.com.
A score of 48 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This Mudita store website has severe performance issues with a score of just 48/100, indicating a very slow user experience. The biggest problem is render-blocking JavaScript files that are delaying page rendering by over 17 seconds, making visitors wait nearly 27 seconds before they can interact with the page. The site is also suffering from inefficient caching (wasting 66KB), unused CSS code (163KB that could be removed), and a slow initial server response that adds 5+ seconds to load times. Fixing these JavaScript blocking issues and implementing proper caching would dramatically improve the user experience and could easily boost the performance score by 30+ points.
Why It Matters:
Critical JavaScript files are blocking page rendering for 17.8 seconds, severely delaying both FCP and LCP.
How to Fix:
Move non-essential JavaScript bundles (bundle4.min.js, bundle9.min.js) to load asynchronously using async or defer attributes. Consider code splitting to load only critical JavaScript inline. Use dynamic imports for features not needed on initial page load.
Why It Matters:
96% of your CSS (163 KiB) and significant JavaScript (114 KiB) are unused, wasting bandwidth and blocking rendering.
How to Fix:
Audit your Magento theme to remove unused CSS rules from the merged stylesheet. Eliminate or defer unused third-party scripts like Google Tag Manager and Cookiebot until after page load. Use tree-shaking to remove unused JavaScript from bundles.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Oversized images waste 263KB and poor cache headers force unnecessary re-downloads.
The redirect chain from pulumi.com to www.pulumi.com adds 780ms delay to every Core Web Vital.
CSS files are blocking page rendering for 4.8 seconds, severely delaying both FCP and LCP.
96% of your CSS (163 KiB) and significant JavaScript (114 KiB) are unused, wasting bandwidth and blocking rendering.