LCP
Largest Contentful Paint
5.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Main Thread Performance
How to optimize majesticrules.fun
Optimize Main Thread Performance
Medium Impact+8 points estimated
Why It Matters
3.6 seconds of main thread blocking work is preventing user interactions and degrading performance.
How to Fix
Break up long JavaScript tasks by using React.Suspense and lazy loading for heavy components. Implement code splitting at the route level in Next.js using dynamic imports. Move Yandex Metrika and other analytics to web workers or defer until after critical rendering.
0Needs Improvement
What This Score Means
A score of 71 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
74ms
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/React site has concerning performance issues with a score of 71/100, primarily due to slow content loading times. The biggest problem is excessive unused JavaScript (111 KiB of wasted code), which is significantly delaying your Largest Contentful Paint to 5.5 seconds - well above the recommended 2.5 seconds for good user experience. The site is also suffering from render-blocking CSS files and inefficient caching of third-party scripts like Yandex Metrica. Removing unused JavaScript, optimizing CSS delivery, and implementing better caching strategies could improve loading times by over 600 milliseconds and substantially boost your Core Web Vitals scores.
Other Optimization Recommendations
Remove Unused JavaScript Code
High Impact+18 points estimatedWhy It Matters:
111 KiB of unused JavaScript is delaying LCP by 600ms and FCP by 300ms.
How to Fix:
Audit your Next.js bundles using webpack-bundle-analyzer to identify unused code. Implement dynamic imports for non-critical components and lazy load the Yandex Metrika script after page load. Use Next.js tree-shaking by importing only needed functions from libraries.
Eliminate Render Blocking CSS
High Impact+12 points estimatedWhy It Matters:
CSS files are blocking initial render, delaying LCP and FCP by 150ms.
How to Fix:
Move critical CSS inline in your Next.js _document.js file for above-the-fold content. Use Next.js built-in CSS optimization with next/dynamic to load non-critical styles asynchronously. Consider using CSS-in-JS solutions like styled-components for component-specific styles.
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
Optimize Critical CSS Rendering
Render-blocking CSS files delay FCP by 750ms and contribute to the poor initial paint performance.
Reduce Unused JavaScript Bundle Size
756 KiB of unused JavaScript delays LCP by 3.9 seconds and wastes 3.9 seconds of load time.
Eliminate Redirect and Optimize Server Response
The redirect from commissions.gg to www.commissions.gg wastes 780ms and delays both FCP and LCP by 800ms each.
Eliminate Element Render Delay
LCP element has 3.2 second render delay causing the poor 7-second LCP score.