LCP
Largest Contentful Paint
10.6s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Remove Unused JavaScript Code
How to optimize credittime.kz
Remove Unused JavaScript Code
High Impact+18 points estimated
Why It Matters
311 KiB of unused JavaScript delays LCP by 1.25 seconds and blocks user interactions.
How to Fix
Implement dynamic imports in Next.js to code-split tracking scripts (Ringostat, GTM). Move non-critical third-party scripts to load after page interaction using next/script with strategy='lazyOnload'. Use webpack-bundle-analyzer to identify and remove unused dependencies from your Next.js build.
0Needs Improvement
What This Score Means
A score of 62 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
274ms
Needs Improvement
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 with a score of 62/100. The biggest problem is an extremely slow Largest Contentful Paint of 10.6 seconds, primarily caused by oversized images and render-blocking CSS that delays critical content from appearing. The main hero image is downloading at 86KB when it only needs to be much smaller for mobile displays, wasting 82KB of bandwidth. Additionally, there's 311KB of unused JavaScript from tracking scripts (Google Analytics, Facebook Pixel, Ringostat) that's blocking the page from becoming interactive for over 10 seconds. Optimizing image sizes, deferring non-critical JavaScript, and improving caching policies could dramatically improve this site's performance and user experience.
Other Optimization Recommendations
Optimize Hero Image Size
High Impact+25 points estimatedWhy It Matters:
The LCP hero image is severely oversized at 1680x1280 but only displays at 380x290, causing a 10.6s LCP delay.
How to Fix:
Update your Next.js Image component to use proper responsive sizes. Generate smaller image variants using next/image's built-in optimization. Set the sizes prop to '(max-width: 640px) 380px, 672px' to match actual display dimensions. Consider using priority={true} on the hero image.
Add Image Dimensions Attributes
Medium Impact+8 points estimatedWhy It Matters:
Missing width and height attributes on logo images cause layout shifts and degrade user experience.
How to Fix:
Add explicit width and height props to all Next.js Image components, especially the logo SVGs in header and footer. For the logo, set width={117} height={20} for mobile and width={220} height={40} for footer. This prevents content jumping during load.
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.