Optimize Image Delivery Format

How to optimize pearsoncars.com

Ruby on Rails SiteScore: 40/100Analyzed February 2026

Optimize Image Delivery Format

High Impact+12 points estimated

Why It Matters

Large PNG images waste 3.3MB of bandwidth and slow LCP, especially the 408KB commercial vehicle image.

How to Fix

Convert PNG images to WebP format using Rails Active Storage with image_processing gem and libvips. Add responsive image variants with different sizes. Use picture element with WebP and PNG fallback. Implement lazy loading for below-fold images with loading='lazy' attribute.

0Poor

What This Score Means

A score of 40 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

LCP

Largest Contentful Paint

42.0s
Poor

Good: < 2.5s

Measures how long it takes for the main content to appear on screen

INP

Interaction to Next Paint

230ms
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 website has severe performance problems with a critically low score of 40/100. The biggest issue is extremely slow loading times - it takes nearly 20 seconds for users to see any content and over 42 seconds for the main image to fully load, which is unacceptable for modern web standards. The site is being crushed by massive amounts of unused JavaScript (over 2MB wasted), render-blocking CSS and JavaScript files that delay initial page rendering, and oversized unoptimized images that should be converted to modern formats like WebP. Fixing these JavaScript and CSS blocking issues alone could improve load times by over 11 seconds and dramatically boost both user experience and search engine rankings.

Other Optimization Recommendations

Remove Unused JavaScript Code

High Impact+25 points estimated

Why It Matters:

Unused JavaScript wastes 2.2MB and delays LCP by 11.5 seconds, severely impacting Core Web Vitals.

How to Fix:

Analyze the large YouTube embed and reCAPTCHA scripts - only load YouTube player when user clicks play button using facade technique. Move reCAPTCHA to contact forms only. In Rails, use conditional loading with content_for blocks to include scripts only where needed. Remove or defer ShareThis social sharing until user interaction.

Eliminate Render Blocking Resources

High Impact+18 points estimated

Why It Matters:

CSS and JS files block initial render for 3.5 seconds, preventing users from seeing content quickly.

How to Fix:

In Rails asset pipeline, move critical CSS inline using critical gem. Defer non-critical stylesheets with media='print' onload='this.media="all"'. For JavaScript, add defer attribute to script tags or move to bottom of body. Use Rails' javascript_include_tag with defer: true option for non-critical scripts.

Want to Analyze YOUR Website?

Get AI-powered performance insights with actionable fixes in 30 seconds

More Ruby on Rails Speed Tests

Ruby on Rails Performance Resources

Frequently Asked Questions

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