Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize rwl.fitness
Missing image dimensions cause layout shifts and poor CLS, while oversized images waste 22KB and delay LCP by 150ms.
In Webflow Designer, set explicit width and height on all image elements including logos and accreditation badges. Use Webflow's responsive image settings to serve appropriately sized images. Enable WebP format in Project Settings if available, or manually upload WebP versions.
A score of 40 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 40/100. The biggest problem is excessive JavaScript execution time (1.9 seconds) from Webflow's own scripts, which is blocking the page from becoming interactive for nearly 15 seconds and delaying the first content paint to 4.6 seconds. The site is also loading enormous video files (over 70MB total) without proper caching, and has significant amounts of unused CSS and JavaScript that could be removed. Optimizing the JavaScript delivery, implementing proper caching for video content, and removing unused code could potentially improve the score by 30+ points and dramatically reduce load times.
Why It Matters:
JavaScript execution takes 1.9 seconds and blocks the main thread, severely impacting TBT (678ms) and TTI (14.6s).
How to Fix:
In Webflow Project Settings, enable 'Minify HTML/CSS/JS' if not already done. Remove unused third-party scripts like excess Facebook Pixel configs and ClickCease if unnecessary. Consider moving non-critical tracking scripts to load after user interaction using Google Tag Manager's trigger delays.
Why It Matters:
Critical resources are blocking initial render for 3.7 seconds, directly delaying both FCP (4.6s) and LCP (10.4s).
How to Fix:
In Webflow Designer, move custom CSS to the head using embed elements for critical styles only. Defer non-essential Webflow interactions until after page load. Use resource hints like preload for critical fonts in the head section of Page Settings.
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
Critical resources are blocking initial render for 3.7 seconds, directly delaying both FCP (4.6s) and LCP (10.4s).
JavaScript execution takes 1.9 seconds and blocks the main thread, severely impacting TBT (678ms) and TTI (14.6s).
jQuery operations are causing 57ms of forced layout recalculations, blocking user interactions.
Critical CSS is blocking First Contentful Paint for 3 seconds, delaying when users see content.