LCP
Largest Contentful Paint
12.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Add Image Dimensions and Caching
How to optimize concordseminars.com
Next.js SiteScore: 46/100Analyzed January 2026
Add Image Dimensions and Caching
Medium Impact+8 points estimated
Why It Matters
Missing image dimensions cause layout shifts and poor caching wastes 120 KiB on repeat visits.
How to Fix
Add explicit width/height props to all Next.js Image components to prevent CLS. Configure Cache-Control headers in next.config.js for static assets with 'headers' array setting max-age=31536000 for images. Set Facebook Pixel cache headers via middleware or CDN rules.
0Poor
What This Score Means
A score of 46 falls in the "Poor" 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
238ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.09
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This Next.js/React site has severe performance issues with a score of 46/100. The biggest problem is massive JavaScript bloat, causing users to wait over 28 seconds for the page to become interactive and 12 seconds for the main content to appear. The site is loading 280 KiB of unused JavaScript and 12+ MB of oversized images that aren't optimized for web delivery. Removing unused code, compressing images to modern formats like WebP, and implementing proper caching could improve the score by 30+ points and dramatically reduce load times from nearly half a minute to under 5 seconds.
Other Optimization Recommendations
Optimize JavaScript Bundle Splitting
High Impact+25 points estimatedWhy It Matters:
280 KiB of unused JavaScript delays LCP by 1.7 seconds and blocks main thread execution.
How to Fix:
Configure Next.js to split chunks more aggressively by adding 'experimental: { optimizeCss: true }' to next.config.js. Use dynamic imports for non-critical components with next/dynamic. Remove or defer Google Tag Manager until after page load using Next.js Script component with strategy='afterInteractive'.
Compress and Modernize Product Images
High Impact+20 points estimatedWhy It Matters:
Product images are 12.8 MB total with poor LCP of 12 seconds due to oversized JPEGs.
How to Fix:
Use Next.js Image component with priority prop for above-fold images and responsive sizes. Convert images to WebP/AVIF using next-optimized-images or sharp. Resize source images to match display dimensions (704x469) instead of serving 4791x3258 files.
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
Compress and Modernize Product Images
Product images are 12.8 MB total with poor LCP of 12 seconds due to oversized JPEGs.
Optimize JavaScript Bundle Splitting
280 KiB of unused JavaScript delays LCP by 1.7 seconds and blocks main thread execution.
Remove Unused JavaScript Code
1,308 KiB of unused JavaScript increases bundle size and delays LCP by 150ms.
Reduce JavaScript Execution Time
JavaScript execution takes 2.2 seconds and blocks main thread, causing 24-second Time to Interactive.
Frequently Asked Questions
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