LCP
Largest Contentful Paint
5.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Video Content Delivery
How to optimize flowcode.may.launch.webflow.io
Optimize Video Content Delivery
High Impact+20 points estimated
Why It Matters
Vimeo video chunks consume 5.6MB of the 10MB total payload, severely impacting load times and Core Web Vitals.
How to Fix
In Webflow, replace auto-playing background videos with optimized poster images on mobile. Use Vimeo's adaptive streaming with lower quality settings for mobile devices. Consider moving videos below the fold and implementing intersection observer-based loading.
0Poor
What This Score Means
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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
196ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.05
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Webflow site has severe performance issues with a score of 39/100. The biggest problem is an enormous network payload of 10MB, primarily from large Vimeo video files that are loading immediately rather than being deferred, causing your Largest Contentful Paint to take 5.4 seconds and First Contentful Paint to reach 4.3 seconds. The site also suffers from 616 KB of unused JavaScript and 77 KB of unused CSS that are blocking the initial render. Implementing video lazy loading, removing unused code, and optimizing the massive image files could improve your score by 30+ points and dramatically reduce loading times for users.
Other Optimization Recommendations
Remove Lazy Loading from LCP Image
High Impact+25 points estimatedWhy It Matters:
The hero image has lazy loading enabled, preventing immediate discovery and delaying LCP by several seconds.
How to Fix:
In Webflow Designer, select the hero background image element. In the Settings panel, remove the lazy loading attribute and add fetchpriority='high' to prioritize this critical resource. Consider setting this image as eager loading instead.
Eliminate Render-Blocking JavaScript
High Impact+18 points estimatedWhy It Matters:
Critical JavaScript blocks initial page render for 3.3 seconds, preventing users from seeing content quickly.
How to Fix:
In Webflow's Project Settings, defer non-essential scripts by moving them to the 'Before </body> tag' section. Use async loading for third-party scripts like Optimizely and analytics. Consider removing or deferring GSAP animations until after first contentful paint.
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
Defer Render-Blocking Resources
Critical CSS and JavaScript files block initial page render for 3.08 seconds, significantly delaying First Contentful Paint.
Optimize LCP Image Loading
The LCP image uses lazy loading and lacks priority hints, preventing fast initial render and hurting user experience.
Remove Unused CSS and JavaScript
Unused code blocks initial render and delays LCP by 2.55 seconds while consuming 319KB of unnecessary bandwidth.
Eliminate Render-Blocking JavaScript
Critical JavaScript blocks initial page render for 3.3 seconds, preventing users from seeing content quickly.