Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize petslucan.cl
Critical CSS files block initial page render for 3.4 seconds, preventing users from seeing content.
Inline critical above-the-fold CSS directly in the HTML head. Move non-critical CSS (Bootstrap, FontAwesome) to load asynchronously using preload with onload fallback. In Rails, use asset pipeline to extract critical CSS and implement async loading with javascript_include_tag defer: true.
A score of 56 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 pet store website has poor performance with a score of 56/100, indicating significant user experience issues. The biggest problem is extremely slow loading times, with pages taking 12 seconds to become interactive and the largest content appearing after 12 seconds - far exceeding Google's recommended 2.5 seconds. The primary culprits are oversized, unoptimized images (particularly a 500KB promotional banner that could be reduced by 75%), render-blocking CSS files that delay initial page display, and a website redirect that adds unnecessary loading time. Fixing these image optimization issues, eliminating the redirect, and streamlining CSS delivery could potentially improve the performance score by 30+ points and dramatically reduce loading times for customers browsing pet products.
Why It Matters:
The main slider image (483 KiB) severely delays LCP by 2.2 seconds and uses inefficient PNG format.
How to Fix:
Convert the slider PNG to WebP format for 40-60% size reduction. Resize from 1348x400 to display dimensions (721x214) to save 363 KiB. Add fetchpriority='high' to the LCP image element. In Rails, use image_tag with explicit dimensions and modern format variants.
Why It Matters:
Images without explicit dimensions cause layout shifts and degrade user experience during page load.
How to Fix:
Replace width='auto' height='auto' with specific pixel dimensions for all slider and product images. Add aspect-ratio CSS property as fallback for responsive behavior. In Rails views, ensure image_tag helpers include width and height parameters based on actual image dimensions.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Ruby on Rails Speed Tests
Images without explicit dimensions cause layout shifts and degrade user experience during page load.
The main slider image (483 KiB) severely delays LCP by 2.2 seconds and uses inefficient PNG format.
CSS files block initial page render for 620ms, delaying both FCP and LCP metrics.
Large images waste 842 KiB of bandwidth and delay LCP by 350ms, particularly the oversized project 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.