LCP
Largest Contentful Paint
13.8s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize JavaScript Execution Time
How to optimize surgence.io
Next.js SiteScore: 37/100Analyzed January 2026
Optimize JavaScript Execution Time
High Impact+20 points estimated
Why It Matters
JavaScript execution takes 5.7 seconds and blocks the main thread, causing 2,580ms Total Blocking Time.
How to Fix
Move Calendly and reCAPTCHA scripts to load after user interaction using Next.js dynamic imports with ssr: false. Break up large JavaScript tasks using scheduler.postTask() or setTimeout for non-critical operations. Defer third-party scripts until after page load.
0Poor
What This Score Means
A score of 37 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
647ms
Poor
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/React website has severe performance issues with a critically low score of 37/100. The biggest problem is excessive JavaScript execution time (5.7 seconds), primarily from third-party scripts like Calendly and reCAPTCHA, which is causing devastating load times - your main content doesn't appear until 13.8 seconds and the page isn't interactive for over 31 seconds. The site is also bloated with 1.6MB of unused JavaScript and 502KB of unused CSS, while images are poorly optimized and oversized. Immediate priorities should be removing or deferring unnecessary third-party scripts, implementing code splitting to reduce unused resources, and optimizing images with modern formats like WebP to dramatically improve user experience.
Other Optimization Recommendations
Eliminate Unused JavaScript and CSS
High Impact+25 points estimatedWhy It Matters:
Unused JavaScript (1,618 KiB) and CSS (502 KiB) are blocking critical resources and delaying LCP by 4.7 seconds.
How to Fix:
Configure Next.js bundle analyzer to identify unused code. Remove or lazy-load Calendly widget (67% unused) until user interaction. Use dynamic imports for non-critical components and implement code splitting by route.
Fix Image Optimization Issues
Medium Impact+12 points estimatedWhy It Matters:
Images are poorly optimized with 781 KiB potential savings and incorrect sizing causing layout shifts.
How to Fix:
Use Next.js Image component with priority prop for LCP images and remove loading='lazy'. Convert PNG logos to WebP/AVIF format. Set proper responsive sizes (130x130 displayed vs 400x400 served) using Next.js Image srcSet generation.
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Performance Analyses
Next.js Performance Resources
Optimize Image Responsive Sizing
Images are served at larger dimensions than displayed, wasting 39 KiB of bandwidth and slowing perceived load time.
Reduce Unused JavaScript Bundle
238 KiB of unused JavaScript is delaying LCP by 450ms and blocking main thread execution.
Optimize Hero Image Loading
The hero mascot image is 15KB larger than needed and could be impacting perceived load performance.
Eliminate Render Blocking CSS Files
CSS files are blocking initial render for 750ms, significantly delaying both FCP and your 5.3s LCP.
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