Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize rwl.fitness
Critical CSS and JavaScript are blocking page rendering for 3 seconds, severely delaying First Contentful Paint.
In Webflow Project Settings > Custom Code, move non-critical scripts to the footer. Inline critical CSS for above-the-fold content. Use async/defer attributes for third-party scripts like Google Analytics and Facebook Pixel. Remove unused Webflow interactions that aren't needed for initial page load.
A score of 52 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 Webflow site has poor performance with a score of 52/100. The biggest problem is render-blocking resources that are delaying the page's initial display by nearly 3 seconds, combined with extremely slow loading times - your Largest Contentful Paint takes 13 seconds and Time to Interactive is 15.3 seconds. The main culprits are oversized JavaScript files (470KB of unused code), unoptimized images (392KB could be saved), and blocking CSS/scripts that prevent the page from rendering quickly. Prioritizing the removal of render-blocking resources and optimizing images could dramatically improve your Core Web Vitals and user experience.
Why It Matters:
Images are oversized and unoptimized, wasting 392 KB and delaying LCP by 1 second.
How to Fix:
In Webflow Designer, resize hero images to match actual display dimensions (506x551 instead of 1500x1632). Enable Webflow's automatic image optimization in Project Settings. Convert background images to WebP format using external tools before upload. Add fetchpriority='high' to LCP image through custom attributes.
Why It Matters:
470 KB of unused JavaScript is increasing load time by 2 seconds and blocking user interactions.
How to Fix:
Remove unused third-party scripts from Project Settings > Integrations. Audit Google Tag Manager to eliminate redundant tracking codes. Use Webflow's built-in analytics instead of multiple tracking solutions. Defer Convert Experiences A/B testing script to load after page interactive using custom code.
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 Webflow Speed Tests
Missing image dimensions cause layout shifts and hurt user experience during page load.
59 KiB of unused CSS is blocking initial render and delaying FCP by 750ms.
470 KiB of unused JavaScript is delaying LCP by 1.7 seconds and blocking user interactions.
470 KB of unused JavaScript is increasing load time by 2 seconds and blocking user interactions.