Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize rwl.fitness
83% of your CSS is unused, wasting 59 KiB and delaying LCP by 700ms.
In Webflow Designer, audit your style panel and remove unused classes and interactions. Use Chrome DevTools Coverage tab to identify unused styles. Split critical above-the-fold CSS from non-critical styles and load them separately.
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 Webflow site has severe performance issues with a score of just 39/100. The biggest problem is massive amounts of unused CSS (59 KiB wasted, 84% unused) that's blocking the page from rendering quickly and delaying your Largest Contentful Paint to a painful 14.8 seconds. Combined with 361 KiB of unused JavaScript and poorly optimized images, visitors are waiting nearly 15 seconds before your page becomes interactive. Cleaning up unused CSS rules, removing unnecessary JavaScript, and properly sizing images could dramatically improve your Core Web Vitals and potentially increase your performance score by 40+ points.
Why It Matters:
Oversized images waste 590 KiB and delay LCP by 1.35 seconds, especially your hero image.
How to Fix:
In Webflow, regenerate responsive images for your hero section background and main content images. Use WebP format in your asset panel. Set proper responsive breakpoints to serve appropriately sized images for mobile devices.
Why It Matters:
Legacy JavaScript polyfills and Facebook Pixel add unnecessary 51 KiB and block rendering.
How to Fix:
Move Facebook Pixel and tracking scripts to fire after page load using Webflow's custom code in the footer. Remove unnecessary polyfills by updating your browser support targets. Use async/defer attributes for third-party scripts like Convert Experiments.
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.