Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize changeengine.com
JavaScript execution takes 18.1 seconds and creates 7.7 seconds of Total Blocking Time, severely impacting user interactions and Core Web Vitals.
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.
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.
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 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.
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.
Why 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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Performance Analyses
The hero laptop image has a 4.1 second render delay and lacks priority hints, contributing to a 53.6 second LCP score.
Render-blocking CSS and JavaScript delay First Contentful Paint by 3.9 seconds, preventing users from seeing content quickly.
Large video files (6MB total) have no cache headers, forcing re-downloads on every visit and impacting LCP by 150ms.
The redirect from rewardful.com to www.rewardful.com adds 780ms delay to every page load.
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.