Eliminate Unused JavaScript Code

How to optimize quick.surf

Generic SiteScore: 71/100Analyzed April 2026Re-analyze this site

Eliminate Unused JavaScript Code

High Impact+12 points estimated

Why It Matters

2MB of unused JavaScript is delaying LCP by 300ms and wasting network resources.

How to Fix

Audit the si-set-BzjTBkDQ.js file which is 98.7% unused and remove unnecessary icon libraries. Implement code splitting to load only required JavaScript modules on demand. Use dynamic imports for features that aren't immediately needed.

0Needs Improvement

What This Score Means

A score of 71 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

LCP

Largest Contentful Paint

4.9s
Poor

Good: < 2.5s

Measures how long it takes for the main content to appear on screen

INP

Interaction to Next Paint

78ms
Good

Good: < 200ms

Measures how quickly the page responds to user interactions

CLS

Cumulative Layout Shift

0.01
Good

Good: < 0.1

Measures visual stability - how much content shifts during page load

AI Performance Analysis

This website has moderate performance issues with a score of 71/100, indicating room for significant improvement. The biggest problem is excessive unused JavaScript - nearly 2MB of unnecessary code is being loaded, with 98.7% of one JavaScript file going unused, which is severely slowing down page loading and delaying the Largest Contentful Paint to 4.9 seconds. The site is also loading 87% unused CSS and has an oversized total payload of 3.3MB, causing the main thread to be blocked for over 2 seconds. Removing unused JavaScript and CSS could save over 2MB of data transfer and improve loading times by several seconds, potentially boosting the performance score by 15-20 points.

Other Optimization Recommendations

Optimize Main Thread Performance

High Impact+10 points estimated

Why It Matters:

2.1 seconds of main thread blocking prevents user interaction and degrades page responsiveness.

How to Fix:

Break up long-running JavaScript tasks using setTimeout or requestIdleCallback to yield control back to the browser. Defer script evaluation for non-critical functionality until after page load. Consider using web workers for heavy computational tasks.

Remove Unused CSS Rules

Medium Impact+8 points estimated

Why It Matters:

87% of your CSS is unused, creating unnecessary render blocking and slowing FCP by 200ms.

How to Fix:

Use PurgeCSS or similar tools to remove unused styles from styles-Cnd2a28Q.css. Extract critical CSS for above-the-fold content and inline it. Defer loading of remaining CSS using media='print' onload='this.media="all"' technique.

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

More Generic Speed Tests

Generic Performance Resources

Frequently Asked Questions