Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize lk.npfsb.ru
Oversized garland images waste 1MB of bandwidth without contributing to core functionality.
Resize garland images from 4000px to actual display size (672px) using Next.js Image component with proper sizing. Convert PNG decorations to WebP format for 70% size reduction. Consider using CSS-based decorations or SVG alternatives for simple graphics.
A score of 55 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 Next.js site has poor performance with a score of 55/100, indicating significant user experience issues. The biggest problem is multiple page redirects that are adding nearly 37 seconds of delay, catastrophically slowing down both First Contentful Paint and Largest Contentful Paint metrics. Additionally, the site is loading oversized, unoptimized images (saving potential of 1MB) and serving 1.5MB of unused JavaScript code that's not needed for the current page. Fixing the redirect chain and optimizing images would provide the most dramatic performance improvements, potentially boosting the score by 30+ points.
Why It Matters:
Redirect chains delay page load by 36.8 seconds, severely impacting LCP and user experience.
How to Fix:
Configure your Next.js application to serve the login page directly without authentication redirects. Implement client-side authentication checks after initial page load. Update server configurations to avoid the OAuth redirect chain for anonymous users.
Why It Matters:
1.5MB of unused JavaScript delays LCP by 13.8 seconds and blocks page interactivity.
How to Fix:
Enable Next.js tree shaking by using ES6 imports and avoiding default imports for libraries. Implement dynamic imports for non-critical components using next/dynamic. Split your main bundle by moving authentication logic to separate chunks that load conditionally.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Next.js Speed Tests
Legacy JavaScript polyfills add 20KB of unnecessary code for modern browsers, slowing LCP by 200ms.
CSS files are blocking first paint, delaying FCP by 300ms and hurting user experience.
35% of your JavaScript bundle (24KB) is unused, increasing LCP by 300ms and blocking page interactivity.
1.5MB of unused JavaScript delays LCP by 13.8 seconds and blocks page interactivity.
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.