Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize productivitytools.io
Font loading delays FCP by 10ms and creates invisible text during font swap, impacting perceived performance.
In Webflow's custom code head section, add <link rel='preload'> for critical fonts (Inconsolata and Mona Sans). Add font-display: swap to Google Fonts URL parameters. Consider hosting fonts locally through Webflow's font upload feature to reduce external requests and improve cache control.
A score of 57 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.
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 poor performance with a score of 57/100, indicating significant user experience issues. The biggest problem is excessive JavaScript execution taking 2.2 seconds, which is blocking the page from becoming interactive until nearly 10 seconds after loading. The site is also suffering from render-blocking CSS and JavaScript files that delay the initial paint by 2.6 seconds, plus a massive 12.5MB network payload dominated by video content. Reducing JavaScript execution time, deferring non-critical scripts, and optimizing the large video files could improve the score by 30+ points and dramatically reduce loading times for users.
Why It Matters:
JavaScript execution takes 2.2 seconds and blocks rendering for 2.55 seconds, severely impacting LCP (6.3s) and TTI (9.8s).
How to Fix:
In Webflow Designer, move all custom code from the head to before </body> tag. Defer GSAP and animation libraries by wrapping them in window.addEventListener('load'). Remove unused JavaScript from the 468KB of detected unused code. Consider replacing heavy GSAP animations with CSS animations for initial page load.
Why It Matters:
Images lack explicit dimensions causing layout shifts and oversized files waste 717KB of bandwidth affecting load performance.
How to Fix:
In Webflow Designer, set explicit width and height on all image elements to prevent CLS. Use Webflow's responsive image settings to serve appropriate sizes. Compress testimonial background images from 2048x2048 to actual display size of 262x262. Enable Webflow's automatic WebP conversion in project settings.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Webflow Speed Tests
Images lack explicit dimensions causing layout shifts and oversized files waste 717KB of bandwidth affecting load performance.
JavaScript execution takes 2.2 seconds and blocks rendering for 2.55 seconds, severely impacting LCP (6.3s) and TTI (9.8s).
Oversized images waste 413KB of bandwidth and delay LCP by 1.3 seconds unnecessarily.
Excessive JavaScript execution time of 1.9 seconds blocks user interactions and degrades performance.