Improve Cloudflare Cache Configuration

How to optimize pixelvault.dev

Ruby on Rails SiteScore: 86/100Analyzed February 2026

Improve Cloudflare Cache Configuration

Medium Impact+3 points estimated

Why It Matters

Short cache lifetime on static assets forces unnecessary re-downloads on repeat visits.

How to Fix

Update your Cloudflare page rules to set longer cache TTL for static assets. Configure Rails asset pipeline with config.public_file_server.headers for far-future expires headers. Set email-decode.min.js to cache for at least 30 days.

0Needs Improvement

What This Score Means

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

LCP

Largest Contentful Paint

3.0s
Needs Improvement

Good: < 2.5s

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

INP

Interaction to Next Paint

16ms
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 good performance with a score of 86/100, but there's room for improvement in loading speed. The biggest issue is render-blocking Google Fonts requests that are delaying both First Contentful Paint and Largest Contentful Paint by 1.3 seconds, causing pages to take 3+ seconds to show meaningful content. Additionally, the site is loading 25KB of unused JavaScript from Turbo and ActionCable libraries, and experiencing forced reflows that create layout stuttering. To boost performance, prioritize deferring or inlining the Google Fonts, remove unused JavaScript code, and optimize the font loading strategy to achieve faster page rendering.

Other Optimization Recommendations

Optimize Font Loading Strategy

High Impact+12 points estimated

Why It Matters:

Render-blocking Google Fonts are delaying LCP and FCP by 1.3 seconds.

How to Fix:

Add <%= preload_link_tag 'https://fonts.googleapis.com/css2?family=Bricolage+Grotesque...', as: :style, crossorigin: 'anonymous' %> to your Rails layout. Use font-display: swap in CSS and consider self-hosting fonts with the google_fonts gem for better performance.

Reduce Turbo JavaScript Overhead

High Impact+8 points estimated

Why It Matters:

85% of Turbo JavaScript is unused and causes 62ms of forced reflows, impacting user interactions.

How to Fix:

Configure Turbo to only load required modules using import maps in Rails 7. Add data-turbo='false' to pages that don't need SPA behavior. Optimize DOM queries in turbo:load events to avoid layout thrashing.

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