Remove Unused JavaScript Code

How to optimize staging.faraday.email

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

Remove Unused JavaScript Code

High Impact+25 points estimated

Why It Matters

252 KiB of unused JavaScript is blocking page load and delaying LCP by 1.35 seconds.

How to Fix

Use webpack-bundle-analyzer to identify unused code in your main bundle. Implement code splitting to load only essential JavaScript on initial page load. Remove or defer Google Tag Manager until after page interaction. Consider lazy loading the Home component since 68% of it is unused initially.

0Needs Improvement

What This Score Means

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

11.5s
Poor

Good: < 2.5s

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

INP

Interaction to Next Paint

16ms
Good

Good: < 200ms

Measures how quickly the page responds to user interactions

CLS

Cumulative Layout Shift

0.06
Good

Good: < 0.1

Measures visual stability - how much content shifts during page load

AI Performance Analysis

This website has poor performance with a score of 55/100, indicating significant user experience issues. The biggest problem is excessive unused JavaScript (252 KiB wasted) and CSS (53 KiB wasted), which is causing extremely slow loading times - your First Contentful Paint and Largest Contentful Paint are taking over 10 seconds each, far exceeding acceptable standards. The site is also suffering from oversized images that are 605 KiB larger than necessary and inefficient caching that could save an additional 14 KiB. Cleaning up unused code, optimizing images for their display dimensions, and implementing better caching could dramatically improve your performance score by 30+ points and provide a much faster user experience.

Other Optimization Recommendations

Optimize Image Delivery Performance

High Impact+20 points estimated

Why It Matters:

Images are oversized by 605 KiB and lack proper dimensions, affecting load speed and layout stability.

How to Fix:

Resize images to match their display dimensions (thumbnail.png to 351x198, clients-mobile.png to 352x421). Convert PNG images to WebP format for better compression. Add explicit width and height attributes to prevent layout shifts during image loading.

Defer Non-Critical CSS Loading

Medium Impact+12 points estimated

Why It Matters:

Render-blocking CSS delays First Contentful Paint by 300ms and contains 95% unused styles.

How to Fix:

Extract critical above-the-fold CSS and inline it in the HTML head. Load the remaining CSS asynchronously using media='print' onload technique. Remove unused CSS rules from your stylesheet or implement CSS tree-shaking in your build process.

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