LCP
Largest Contentful Paint
20.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Unused CSS and JavaScript
How to optimize ullswaterroadgarage.co.uk
Reduce Unused CSS and JavaScript
High Impact+25 points estimated
Why It Matters
Unused code blocks critical rendering for 6+ seconds and wastes 1.1MB in network payload.
How to Fix
Use Rails asset pipeline to analyze and remove unused CSS rules (434 KiB savings). Implement code splitting with Webpacker to load only necessary JavaScript per page. Remove unused polyfills from CookieControl library (38KB savings) and consider switching to a lighter alternative.
0Needs Improvement
What This Score Means
A score of 55 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
151ms
Good
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 significant performance problems with a poor score of 55/100. The biggest issue is excessive unused CSS that's blocking the page from rendering quickly, wasting 434 KiB of data and delaying both First Contentful Paint and Largest Contentful Paint by over 2 seconds. The site is also suffering from forced reflows caused by JavaScript (primarily Google Analytics), legacy JavaScript bloat, and poor caching strategies that force users to re-download 2.7 MB of resources on every visit. Cleaning up the CSS, implementing proper caching headers, and optimizing the JavaScript could easily improve the performance score by 30+ points and dramatically reduce the current 20-second load time.
Other Optimization Recommendations
Fix Forced Reflows and Performance
High Impact+18 points estimatedWhy It Matters:
JavaScript queries cause 92ms of forced reflows, blocking main thread and delaying interactivity.
How to Fix:
Optimize Google Analytics implementation by using gtag with minimal configuration. Cache DOM queries in your Rails JavaScript and batch DOM writes. Move CookieControl initialization to after page load to reduce blocking time.
Implement Efficient Caching Strategy
High Impact+15 points estimatedWhy It Matters:
Zero cache lifetime on assets wastes 2.7MB on repeat visits and slows LCP by 11 seconds.
How to Fix:
Configure Rails asset pipeline with far-future expires headers (1 year) for static assets. Set up CloudFlare or similar CDN with proper cache control headers. Enable gzip compression for CSS/JS files in your Rails server configuration.
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
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.
Defer Render-Blocking JavaScript Resources
Critical JavaScript files are blocking page render and delaying FCP by 1.05 seconds.
Optimize Image Delivery and Sizing
Oversized and uncompressed images waste 347KB of bandwidth and slow LCP by 500ms.