Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize medipost.shop
Poor cache policies waste 187KB on repeat visits and slow returning user experience.
Set cache headers for Facebook scripts to 1 year instead of 20 minutes. Configure CDN caching for static assets like Doofinder loader. Add versioning to your own CSS/JS files to enable long-term caching while allowing updates.
A score of 56 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.
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 e-commerce product page has poor performance with a score of 56/100, indicating significant user experience issues. The biggest problem is massive amounts of unused CSS (895 KiB) and JavaScript (1,820 KiB) that are blocking the page from rendering quickly, causing extremely slow load times with First Contentful Paint at 7.7 seconds and Largest Contentful Paint at 11.4 seconds. The site is also loading oversized images without proper dimensions and using inefficient caching strategies for Facebook tracking scripts and other third-party resources. Removing unused code, optimizing images, and implementing better caching could potentially improve the performance score by 30+ points and dramatically reduce load times from over 11 seconds to under 3 seconds.
Why It Matters:
Unused code accounts for 2.7 MB and delays LCP by 5.7 seconds with blocking render.
How to Fix:
Remove unused CSS rules from web.assets_frontend.min.css (900KB waste). Code-split the frontend_lazy.min.js file to load only required components. Defer non-critical third-party scripts like Facebook Pixel and Doofinder until after page load.
Why It Matters:
Main product image is lazy-loaded and not discoverable, causing 11.4s LCP delay.
How to Fix:
Remove loading='lazy' from the main product image. Add fetchpriority='high' attribute to prioritize loading. Preload the LCP image in the HTML head using <link rel='preload' as='image'>. Add explicit width and height attributes to prevent layout shifts.
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
91% of CSS (44 KiB) is unused and blocks initial render, delaying FCP by 100ms.
The hero background image is oversized (1182x1168 for 721x712 display) adding 600ms to LCP.
Unused JavaScript (452 KiB) delays LCP by 1.5 seconds and blocks main thread execution.
Over 316KB of unused JavaScript is loaded, wasting bandwidth and blocking the main thread.