LCP
Largest Contentful Paint
7.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Implement Responsive Image Optimization
How to optimize pocapay.com
Implement Responsive Image Optimization
High Impact+18 points estimated
Why It Matters
Artist images waste 921KB by serving 640x640 images for 117x117 display size.
How to Fix
Replace standard img tags with Next.js Image component using sizes prop for responsive loading. Create multiple image variants (128px, 256px, 512px) and serve appropriately sized images. Convert Spotify images to modern AVIF/WebP formats using Next.js built-in optimization.
0Needs Improvement
What This Score Means
A score of 74 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
75ms
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 site has concerning performance issues with a score of 74/100, primarily due to extremely slow content loading that takes over 7 seconds for the largest element to appear on screen. The biggest problem is poor image optimization - the site is downloading images that are 3x larger than needed (640x640 pixels displayed at only 204x204) and using outdated image formats, wasting nearly 1MB of data. Additionally, the main hero image lacks proper caching and priority hints, further delaying the critical loading experience. Implementing responsive images, modern WebP/AVIF formats, and proper caching could dramatically improve load times and boost the performance score by 20+ points.
Other Optimization Recommendations
Optimize LCP Image Delivery
High Impact+25 points estimatedWhy It Matters:
LCP is 7.1 seconds due to inefficient image loading and the LCP image lacks priority hints.
How to Fix:
Add fetchpriority='high' to the LCP image (ILLIT image). Convert the 128KB WebP image to AVIF format for 20-30% additional compression. Ensure the LCP image is eagerly loaded and properly sized using Next.js Image component with priority prop.
Configure Static Asset Caching
Medium Impact+8 points estimatedWhy It Matters:
Poor cache configuration forces unnecessary re-downloads of 133KB on repeat visits.
How to Fix:
Set cache-control headers for static assets to 1 year in next.config.js using headers() configuration. Configure your CDN or hosting provider to cache WebP images and fonts with long expiration times. Add immutable directive to versioned assets for better browser caching.
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.