LCP
Largest Contentful Paint
53.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Eliminate Render-Blocking Resources
How to optimize changeengine.com
Eliminate Render-Blocking Resources
High Impact+25 points estimated
Why It Matters
Render-blocking CSS and JavaScript delay First Contentful Paint by 3.9 seconds, preventing users from seeing content quickly.
How to Fix
In Webflow's Project Settings, move custom code from the Head to before closing Body tag where possible. Use Webflow's built-in CSS optimization features. Remove or defer the cookieJS-default.js script that's blocking for 780ms with zero bytes transferred.
0Poor
What This Score Means
A score of 25 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
967ms
Poor
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 severe performance issues with a critically low score of 25/100. The biggest problem is excessive JavaScript execution taking over 18 seconds to complete, which is blocking the page from becoming interactive for nearly 54 seconds and causing a devastating Total Blocking Time of 7.7 seconds. The site is also loading an enormous 21MB of content including large video files and animations, while serving outdated JavaScript that wastes 1.2MB of bandwidth. Immediate priorities should be reducing JavaScript payloads, optimizing or removing heavy video content, and addressing the render-blocking resources that delay initial page loading by nearly 4 seconds.
Other Optimization Recommendations
Optimize Critical JavaScript Execution
High Impact+35 points estimatedWhy It Matters:
JavaScript execution takes 18.1 seconds and creates 7.7 seconds of Total Blocking Time, severely impacting user interactions and Core Web Vitals.
How to Fix:
In Webflow, remove unused JavaScript interactions and defer non-critical third-party scripts. Move Wistia video embeds to load on user interaction rather than page load. Split large JavaScript chunks by removing unnecessary Webflow interactions from pages where they're not used.
Optimize LCP Image Loading
High Impact+20 points estimatedWhy It Matters:
The hero laptop image has a 4.1 second render delay and lacks priority hints, contributing to a 53.6 second LCP score.
How to Fix:
Add fetchpriority='high' to the hero laptop image in Webflow's image settings. Ensure the image is not lazy-loaded by unchecking lazy loading in the image element settings. Consider using Webflow's responsive image feature to serve appropriately sized images for different devices.
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
Configure Browser Caching Headers
Poor cache lifetimes waste 80KB on repeat visits and slow FCP by 450ms for returning users.
Implement Proper Image Optimization
Oversized gallery images waste 664KB and delay LCP by 250ms while missing dimensions cause layout shifts.
Optimize Render-Blocking Resources
Render-blocking CSS and JavaScript delay First Contentful Paint by 900ms and severely impact LCP (9.3s).
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.