LCP
Largest Contentful Paint
7.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Fix LCP Image Critical Loading
How to optimize nurskin.fr
Fix LCP Image Critical Loading
High Impact+25 points estimated
Why It Matters
Your hero image lacks fetchpriority=high and proper discovery, causing a 7.1s LCP that severely impacts user experience.
How to Fix
Add fetchpriority='high' to the hero image at div.pt-24 > section.relative > div.absolute > img.w-full. Ensure the image is discoverable in initial HTML without JavaScript. Move the image source directly into the HTML instead of loading it dynamically.
0Needs Improvement
What This Score Means
A score of 65 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
184ms
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 poor performance with a score of 65/100, primarily due to extremely slow loading times. The biggest problem is the Largest Contentful Paint taking 7.1 seconds, which is caused by render-blocking CSS and font files that delay page rendering by an estimated 1.4 seconds. The site is also loading 336 KiB of unused JavaScript and serving unoptimized images that waste 347 KiB of bandwidth. Fixing the render-blocking resources, compressing images properly, and removing unused JavaScript could dramatically improve the score and cut loading times nearly in half.
Other Optimization Recommendations
Eliminate Render Blocking Resources
High Impact+18 points estimatedWhy It Matters:
CSS and font files are blocking first paint by 1.36 seconds, delaying when users see content.
How to Fix:
Inline critical CSS from index-6xt0zXI9.css directly in the HTML head. Add rel='preload' with as='style' for Google Fonts CSS files. Use font-display: swap in your CSS to prevent invisible text during font load.
Optimize Image Delivery and Sizing
Medium Impact+12 points estimatedWhy It Matters:
Oversized and uncompressed images waste 347KB of bandwidth and slow LCP by 500ms.
How to Fix:
Resize the 4500x4500 logo to actual display dimensions (168x168). Increase compression on the Unsplash hero image to save 177KB. Add explicit width and height attributes to prevent layout shifts. Use Rails' image_tag helper with size parameter for proper dimensions.
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
Optimize Image Delivery and Sizing
Oversized and uncompressed images waste 347KB of bandwidth and slow LCP by 500ms.
Eliminate Render Blocking Resources
CSS and font files are blocking first paint by 1.36 seconds, delaying when users see content.
Reduce Unused Code Payload
2.2MB of unused JavaScript and 485KB unused CSS waste bandwidth and slow parsing.
Fix Critical Layout Shifts
Layout shifts score of 1.03 severely impacts user experience and Core Web Vitals.