Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize 533381.snk.wtf
Images account for over 4MB of payload and delay LCP by 13.9 seconds, representing the largest performance bottleneck.
Convert PNG images to WebP/AVIF format using Rails Active Storage variants or image_processing gem. Resize the logo from 1024x1024 to 224x224 served dimensions and the screenshot from 1535x1024 to 378x252. Add responsive image generation with Rails' image_variant helper to serve appropriately sized images.
A score of 75 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 Ruby on Rails site has poor performance with a score of 75/100, but suffers from severe loading issues with a 22.4-second Time to Interactive. The biggest problem is massively oversized images that are wasting nearly 2.8MB of data - the logo image alone is 1.6MB when it only needs to display at 224x224 pixels but is served at 1024x1024. Converting these images to modern formats like WebP and properly sizing them for their display dimensions could save over 13 seconds on page load time. Adding explicit width and height attributes to images and applying fetchpriority="high" to the main logo would further improve the user experience and Core Web Vitals scores.
Why It Matters:
The LCP image (logo) lacks fetchpriority=high, preventing the browser from prioritizing its download.
How to Fix:
Add fetchpriority='high' attribute to the logo image tag in your Rails view template. Use Rails' image_tag helper with loading: :eager and fetchpriority: :high options. Consider preloading the LCP image in the document head using link rel='preload'.
Why It Matters:
Missing width and height attributes on images cause layout shifts that hurt CLS and user experience.
How to Fix:
Add explicit width and height attributes to the client screenshot image using Rails' image_tag helper with size or width/height options. Set CSS aspect-ratio property to maintain responsive behavior while preventing layout shifts. Update your Rails partials to include dimensions for all images.
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
Missing width and height attributes on images cause layout shifts that hurt CLS and user experience.
The LCP image (logo) lacks fetchpriority=high, preventing the browser from prioritizing its download.
Images are oversized by 161 KiB and could improve perceived load performance.
JavaScript is causing 316ms of forced reflows that block the main thread and delay interactions.