LCP
Largest Contentful Paint
11.3s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize LCP Image Loading
How to optimize flowcode.may.launch.webflow.io
Optimize LCP Image Loading
High Impact+18 points estimated
Why It Matters
The LCP image uses lazy loading and lacks priority hints, preventing fast initial render and hurting user experience.
How to Fix
In Webflow Designer, select the pricing card image (LCP element) and remove lazy loading. Add fetchpriority='high' via custom attributes. Set explicit width and height dimensions to prevent layout shifts during load.
0Needs Improvement
What This Score Means
A score of 55 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
126ms
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 poor performance with a score of 55/100, indicating significant user experience issues. The biggest problem is excessive unused CSS (57 KiB) and JavaScript (256 KiB) that's blocking page rendering and severely delaying your First Contentful Paint to 6.4 seconds and Largest Contentful Paint to 11.3 seconds. The site is also loading massive files like a 1.3MB SVG logo and has render-blocking resources that add over 3 seconds to load time. Removing unused code, optimizing images, and deferring non-critical JavaScript could improve your performance score by 30+ points and dramatically reduce load times for your users.
Other Optimization Recommendations
Remove Unused CSS and JavaScript
High Impact+25 points estimatedWhy It Matters:
Unused code blocks initial render and delays LCP by 2.55 seconds while consuming 319KB of unnecessary bandwidth.
How to Fix:
In Webflow Designer, audit your custom CSS and remove unused styles. Disable unnecessary integrations like HubSpot feedback widget if not essential. Use Webflow's built-in optimization to purge unused CSS automatically on publish.
Defer Render-Blocking Resources
Medium Impact+12 points estimatedWhy It Matters:
Critical CSS and JavaScript files block initial page render for 3.08 seconds, significantly delaying First Contentful Paint.
How to Fix:
Move Optimizely and other A/B testing scripts to load asynchronously after page content. In Webflow project settings, defer Google Fonts loading using font-display: swap. Consider inlining critical CSS for above-the-fold content.
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.
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.
Optimize Video Content Delivery
Vimeo video chunks consume 5.6MB of the 10MB total payload, severely impacting load times and Core Web Vitals.