Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize dormeo.co.uk
Your LCP image takes 12.4 seconds to load and is lazy-loaded, severely delaying page render.
Remove loading='lazy' from your hero banner image (m1_sleep-event_03-26_5.webp). Add fetchpriority='high' attribute to prioritize loading. Ensure the LCP image is discoverable in initial HTML without JavaScript.
A score of 39 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 website has severe performance issues with a score of just 39/100. The biggest problem is extremely slow loading of the main content, taking 12.4 seconds for users to see the largest image on the page - that's about 10 seconds longer than Google recommends. The site is loading massive unoptimized images (639KB could be saved through compression and modern formats like WebP), executing too much JavaScript (4.4 seconds of processing time), and has render-blocking CSS files that delay the initial paint by 2.5 seconds. Fixing the image optimization alone and deferring non-critical JavaScript could improve the performance score by 30+ points and dramatically speed up the user experience.
Why It Matters:
Images waste 639 KiB of bandwidth with oversized dimensions and outdated formats.
How to Fix:
Convert JPEG images to WebP format for 30-50% size reduction. Implement responsive images using srcset with appropriate sizes (330px instead of 544px). Use image optimization tools like ImageOptim or TinyPNG for compression.
Why It Matters:
CSS files block page rendering for 2.47 seconds, preventing users from seeing content quickly.
How to Fix:
Inline critical CSS for above-the-fold content directly in HTML head. Defer non-critical CSS using media='print' onload="this.media='all'" technique. Consider splitting large CSS bundles and loading progressively.
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
The main container causes a 0.131 CLS score due to content moving during page load.
Critical CSS files block initial render for 900ms, significantly delaying both FCP and LCP.
The redirect from root domain delays LCP by 750ms and adds unnecessary server round trips.
CSS files block page rendering for 2.47 seconds, preventing users from seeing content quickly.