LCP
Largest Contentful Paint
4.9s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize JavaScript Execution Performance
How to optimize majesticrules.fun
Optimize JavaScript Execution Performance
High Impact+12 points estimated
Why It Matters
1.4 seconds of JavaScript execution time is blocking the main thread and delaying interactivity.
How to Fix
Update your Next.js build target to modern browsers (ES2017+) to eliminate unnecessary polyfills and save 14KB. Move Yandex Metrica initialization to useEffect with a delay or load it after user interaction. Consider using Next.js Script component with strategy='afterInteractive' for analytics.
0Needs Improvement
What This Score Means
A score of 70 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
122ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.02
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js site has concerning performance issues with a score of 70/100, primarily caused by excessive JavaScript that's slowing down the page. The biggest problem is a massive 1.4 seconds spent executing JavaScript, with nearly half of the code being unused (63 KiB of waste), which is delaying your Largest Contentful Paint to a poor 4.9 seconds. The Yandex analytics script alone accounts for much of this bloat, using 46% more code than necessary. Removing unused JavaScript, optimizing your build process to avoid unnecessary polyfills, and implementing better caching strategies could significantly improve load times and user experience.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+15 points estimatedWhy It Matters:
63KB of unused JavaScript is delaying LCP by 450ms and wasting bandwidth.
How to Fix:
Analyze your Next.js bundle with @next/bundle-analyzer to identify unused code. Configure Yandex Metrica to load only essential features or consider replacing with a lighter analytics solution. Use dynamic imports for non-critical components to enable code splitting.
Implement Long-term Asset Caching
Medium Impact+8 points estimatedWhy It Matters:
Poor caching strategy wastes 74KB on repeat visits and slows LCP by 300ms.
How to Fix:
Configure your CDN or hosting provider to set cache headers for static assets to 1 year (31536000 seconds). For Yandex Metrica, implement a service worker to cache the analytics script locally. Ensure Next.js static assets use immutable cache headers with proper versioning.
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 Next.js Speed Tests
Next.js Performance Resources
Eliminate Render-Blocking CSS Resources
Render-blocking CSS is delaying LCP by 1.95 seconds, preventing the page from displaying content quickly.
Fix Render Blocking Resources
Critical CSS files are blocking initial page render and delaying LCP by 200ms.
Reduce JavaScript Execution Time
JavaScript takes 10.5 seconds to execute, blocking the main thread and preventing user interactions for 4.3 seconds.
Eliminate Unused JavaScript Code
Removing 3,139 KiB of unused JavaScript will reduce network transfer time and improve LCP by 12 seconds.