LCP
Largest Contentful Paint
2.6s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Third-Party JavaScript Impact
How to optimize credittime.kz
Reduce Third-Party JavaScript Impact
High Impact+6 points estimated
Why It Matters
Analytics and tracking scripts execute for 1.5 seconds, blocking user interactions and increasing Total Blocking Time.
How to Fix
Defer Google Analytics, Yandex Metrica, and Facebook Pixel using Next.js Script component with strategy='afterInteractive'. Remove unused portions of tracking scripts (311 KiB detected). Implement Partytown to run third-party scripts in a web worker.
0Needs Improvement
What This Score Means
A score of 88 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
350ms
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 good performance with a score of 88/100, but has significant JavaScript execution issues that are hurting user interactivity. The biggest problem is excessive JavaScript processing time (1.5 seconds), particularly from analytics scripts like Yandex Metrica and Google Tag Manager, which is causing a poor Time to Interactive score of 11.4 seconds and high Total Blocking Time of 380ms. The site is also loading 311 KiB of unused JavaScript and using outdated JavaScript polyfills that add unnecessary 36 KiB of legacy code for modern browsers. Removing unused JavaScript, optimizing third-party scripts, and updating the build process to avoid legacy polyfills could dramatically improve interactivity and reduce blocking time by several hundred milliseconds.
Other Optimization Recommendations
Optimize and Resize Images
High Impact+8 points estimatedWhy It Matters:
Large images waste 869 KiB and delay LCP by 650ms, significantly impacting page load performance.
How to Fix:
Resize licensect.jpg from 2480x3307 to match display size (315x431) and compress to WebP format. Update Next.js Image components to use responsive sizes prop with proper breakpoints. Enable next/image optimization for all static images in your public folder.
Eliminate Render-Blocking CSS
High Impact+7 points estimatedWhy It Matters:
CSS files block initial page render for 410ms, delaying First Contentful Paint by 400ms.
How to Fix:
Extract critical CSS for above-the-fold content and inline it in the document head. Use Next.js dynamic imports for non-critical CSS components. Implement font-display: swap for custom fonts and preload the primary font file.
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.