LCP
Largest Contentful Paint
12.4s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Image Delivery Strategy
How to optimize inflact.com
Optimize Image Delivery Strategy
Medium Impact+8 points estimated
Why It Matters
Images are oversized by 161 KiB and could improve perceived load performance.
How to Fix
Use Rails' image_tag with srcset attribute to serve responsive images at correct dimensions. Compress PNG images using ImageOptim or similar tools in your asset pipeline. Convert large images to WebP format with Rails Active Storage variants. Set proper width/height attributes to prevent layout shifts.
0Poor
What This Score Means
A score of 44 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
435ms
Needs Improvement
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 Ruby on Rails site has poor performance with a score of 44/100. The biggest problem is excessive unused JavaScript (391 KiB), particularly from Google Ads and cookie consent scripts, which is causing a painfully slow 12.4-second load time and blocking user interactions for over 770ms. The site is also loading 21 separate JavaScript chunks in a dependency chain that takes 443ms to complete, while serving unminified JavaScript files and oversized images. Removing unused JavaScript, minifying remaining scripts, and optimizing the image delivery could improve the score by 30+ points and dramatically reduce load times.
Other Optimization Recommendations
Eliminate Unused JavaScript Dependencies
High Impact+25 points estimatedWhy It Matters:
391 KiB of unused JavaScript delays LCP by 1.95 seconds and blocks user interactions.
How to Fix:
Configure Rails asset pipeline to code-split chunks more granularly using dynamic imports. Remove unused Google Ads and tracking scripts from critical rendering path. Use Rails' javascript_include_tag with defer attribute for non-essential scripts. Audit OneTrust cookie consent library for unused features.
Fix Forced Layout Reflows
High Impact+20 points estimatedWhy It Matters:
JavaScript is causing 316ms of forced reflows that block the main thread and delay interactions.
How to Fix:
Batch DOM reads and writes in your Rails view helpers to avoid layout thrashing. Cache geometric properties like offsetWidth instead of repeatedly querying them. Move style calculations to CSS using transforms instead of JavaScript positioning. Profile the chunks causing reflows (8001.js and 946.js) to identify specific DOM manipulation code.
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 Ruby on Rails Speed Tests
Ruby on Rails Performance Resources
Fix Forced Layout Reflows
JavaScript is causing 316ms of forced reflows that block the main thread and delay interactions.
Eliminate Unused JavaScript Dependencies
391 KiB of unused JavaScript delays LCP by 1.95 seconds and blocks user interactions.
Remove Unused CSS and JavaScript
40KB of unused JavaScript and 34KB of unused CSS are unnecessarily slowing page load.
Optimize LCP Image Loading Performance
LCP takes 3.7 seconds due to oversized images that are 4x larger than display dimensions.