Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize carloslucasteamworkspace.myclickfunnels.com
40KB of unused JavaScript and 34KB of unused CSS are unnecessarily slowing page load.
Use webpack-bundle-analyzer to identify unused code in Rails asset pipeline. Remove unused FontAwesome CSS (98% unused) and replace with specific icons. Split JavaScript bundles to load only required functionality per page using Rails code splitting.
A score of 81 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 ClickFunnels landing page has good performance with a score of 81/100, but has significant room for improvement in Core Web Vitals. The biggest issue is render-blocking JavaScript files (jQuery, lazysizes, and intlTelInput libraries) that are delaying your First Contentful Paint by over 1 second and contributing to a slow Largest Contentful Paint of 3.7 seconds. The page is also loading 40KB of unused JavaScript and serving oversized images that are much larger than their displayed dimensions. Deferring non-critical JavaScript, minifying your custom scripts, and properly sizing your images could easily push your performance score above 90 and deliver a much faster user experience.
Why It Matters:
Critical JavaScript files are blocking page render and delaying FCP by 1.05 seconds.
How to Fix:
Move jQuery, lazysizes, and intlTelInput scripts to load after DOM content using defer attribute or async loading. In Rails, use javascript_include_tag with defer: true option. Consider inlining critical JavaScript directly in HTML to reduce network requests.
Why It Matters:
LCP takes 3.7 seconds due to oversized images that are 4x larger than display dimensions.
How to Fix:
Resize hero image from 1000x279 to actual display size of 263x73 using Rails image processing gems like ImageMagick. Add fetchpriority='high' to LCP image element. Generate responsive srcset with multiple sizes using Rails Active Storage variants.
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 Ruby on Rails Speed Tests
LCP takes 3.7 seconds due to oversized images that are 4x larger than display dimensions.
Critical JavaScript files are blocking page render and delaying FCP by 1.05 seconds.
Oversized and uncompressed images waste 347KB of bandwidth and slow LCP by 500ms.
CSS and font files are blocking first paint by 1.36 seconds, delaying when users see content.