LCP
Largest Contentful Paint
11.2s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Enormous Video File Sizes
How to optimize rwl.fitness
Reduce Enormous Video File Sizes
High Impact+25 points estimated
Why It Matters
Video files totaling 27MB are crushing your LCP score and causing the 6.5-second Speed Index.
How to Fix
In Webflow's Assets panel, compress testimonial videos to under 2MB each using H.264 codec with 720p resolution. Consider switching to poster images with play buttons that load videos on-demand. Use Vimeo or YouTube embeds for better compression and CDN delivery.
0Needs Improvement
What This Score Means
A score of 53 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
151ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Webflow site has poor performance with a score of 53/100, primarily due to massive video files that are severely impacting load times. The biggest problem is an enormous 73MB total payload dominated by three large video testimonials (11MB, 8.5MB, and 7.4MB each), causing the Largest Contentful Paint to reach a sluggish 11.2 seconds. Additionally, the site suffers from 461KB of unused JavaScript, poor caching policies, and render-blocking resources that delay initial content display by over 3 seconds. Compressing or replacing these videos with lighter alternatives, implementing proper caching, and removing unused code could dramatically improve the score by 30+ points and transform the user experience from frustratingly slow to acceptably fast.
Other Optimization Recommendations
Optimize Render-Blocking CSS Resources
High Impact+20 points estimatedWhy It Matters:
Critical CSS is blocking First Contentful Paint for 3 seconds, delaying when users see content.
How to Fix:
In Webflow's Designer, go to Project Settings > Custom Code and inline critical CSS in the head section. Remove unused CSS rules (currently 83% unused) by cleaning up unused classes and components. Use Webflow's built-in purge feature or manually audit your stylesheet.
Fix jQuery-Caused Forced Reflows
Medium Impact+10 points estimatedWhy It Matters:
jQuery operations are causing 57ms of forced layout recalculations, blocking user interactions.
How to Fix:
In Webflow's Custom Code section, batch DOM reads and writes to avoid layout thrashing. Replace jQuery animations with CSS transforms where possible. Use requestAnimationFrame for smooth animations instead of direct DOM manipulation in custom scripts.
Keep Your Site Fast After Optimization
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.
Explore DeployHQ →Trusted by engineering teams shipping high-performance sites
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Webflow Speed Tests
Webflow Performance Resources
Add Image Dimensions and Optimize Delivery
Missing image dimensions cause layout shifts and poor CLS, while oversized images waste 22KB and delay LCP by 150ms.
Fix Render-Blocking Resources
Critical resources are blocking initial render for 3.7 seconds, directly delaying both FCP (4.6s) and LCP (10.4s).
Optimize JavaScript Execution and Bundle Size
JavaScript execution takes 1.9 seconds and blocks the main thread, severely impacting TBT (678ms) and TTI (14.6s).
Fix jQuery-Caused Forced Reflows
jQuery operations are causing 57ms of forced layout recalculations, blocking user interactions.