LCP
Largest Contentful Paint
10.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Update JavaScript Build Configuration
How to optimize rosehillpilates.com
Next.js SiteScore: 61/100Analyzed February 2026
Update JavaScript Build Configuration
Medium Impact+8 points estimated
Why It Matters
Legacy JavaScript polyfills add 20KB of unnecessary code for modern browsers, slowing LCP by 200ms.
How to Fix
Update your Next.js target to 'es2017' or newer in next.config.js. Configure Babel to exclude polyfills for baseline JavaScript features like Array.at() and Object.hasOwn(). Use browserslist to target only browsers you need to support.
0Needs Improvement
What This Score Means
A score of 61 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
59ms
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 Next.js site has poor performance issues with a score of 61/100. The biggest problem is extremely slow loading times, with your Largest Contentful Paint taking 10.6 seconds and First Contentful Paint at 5.2 seconds - far beyond Google's recommended thresholds. The main culprits are unused JavaScript (23 KB that could be removed), render-blocking CSS files, and oversized images that are larger than needed for their display size. Quick wins include removing 35% of unused JavaScript code, minifying third-party scripts, and properly sizing images, which together could save over 50 KB and reduce load times by several seconds.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+12 points estimatedWhy It Matters:
35% of your JavaScript bundle (24KB) is unused, increasing LCP by 300ms and blocking page interactivity.
How to Fix:
Use Next.js bundle analyzer to identify unused code. Enable tree shaking in your webpack config. Split large chunks using dynamic imports and load components only when needed. Remove or lazy-load the Barion pixel tracking script.
Eliminate Render Blocking CSS
High Impact+10 points estimatedWhy It Matters:
CSS files are blocking first paint, delaying FCP by 300ms and hurting user experience.
How to Fix:
Move critical CSS inline using Next.js styled-jsx or CSS-in-JS solutions. Use next/dynamic with ssr: false for non-critical components. Defer the 15KB CSS chunk by splitting it into critical and non-critical parts.
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Next.js Speed Tests
Next.js Performance Resources
Eliminate Render Blocking CSS
CSS files are blocking first paint, delaying FCP by 300ms and hurting user experience.
Remove Unused JavaScript Code
35% of your JavaScript bundle (24KB) is unused, increasing LCP by 300ms and blocking page interactivity.
Optimize Decorative Images
Oversized garland images waste 1MB of bandwidth without contributing to core functionality.
Reduce Unused JavaScript Bundle
1.5MB of unused JavaScript delays LCP by 13.8 seconds and blocks page interactivity.
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