Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize heylow.world
The hero image uses lazy loading and lacks priority hints, potentially delaying LCP and creating suboptimal user experience.
Remove loading='lazy' from the hero image and add fetchpriority='high' attribute. Replace the CSS calc() width value with explicit pixel dimensions. Preload the hero image using <link rel='preload' as='image'> in the HTML head to start downloading immediately.
A score of 94 falls in the "Good" 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 achieves a strong performance score of 94/100, indicating excellent optimization overall. The biggest issue affecting load times is render-blocking resources (CSS and JavaScript files) that delay the initial page display by an estimated 1.1 seconds, particularly impacting First Contentful Paint. The main image on the page is also problematic - it's lazy-loaded when it should load immediately since it's the largest visual element, and it's oversized for its display dimensions, wasting 41 KB of bandwidth. Quick wins include removing lazy-loading from the hero image, adding fetchpriority="high" to prioritize it, properly sizing the image, and deferring non-critical JavaScript to eliminate render-blocking behavior.
Why It Matters:
JavaScript and CSS files are blocking initial render, delaying FCP by 1.1 seconds and creating a poor loading experience.
How to Fix:
Move the hexfilter.js and Brevo popup script to load after page content using async or defer attributes. Inline critical CSS for above-the-fold content and load the full stylesheet asynchronously. Consider removing non-essential third-party scripts from the critical path.
Why It Matters:
Custom fonts are causing 180ms delay in text visibility, hurting First Contentful Paint and user experience.
How to Fix:
Add font-display: swap to your @font-face declarations to show fallback text immediately. Preload critical fonts using <link rel='preload' as='font'> tags. Consider using font metric overrides in CSS to reduce layout shift when custom fonts load.
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
Images waste 82 KiB due to oversized dimensions and poor compression, slowing down page rendering.
The main product image uses lazy loading and lacks priority hints, delaying the largest contentful paint.
Google Fonts CSS is blocking initial render and delaying FCP by 750ms.
The LCP image takes 9.6 seconds to load and could be optimized for 550KB savings and 2.95s improvement.