Remove Unused Google Analytics JavaScript

How to optimize andycomputers.com

Generic SiteScore: 97/100Analyzed January 2026

Remove Unused Google Analytics JavaScript

Medium Impact+3 points estimated

Why It Matters

49 KiB of unused JavaScript from Google Tag Manager is unnecessarily increasing bundle size and parse time.

How to Fix

Audit your Google Analytics configuration to remove unused tracking features. Consider switching to gtag direct implementation instead of GTM if you only need basic tracking. Load analytics scripts asynchronously after page interactive using defer attribute or dynamic import.

0Good

What This Score Means

A score of 97 falls in the "Good" 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

2.4s
Good

Good: < 2.5s

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

INP

Interaction to Next Paint

83ms
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 website has excellent performance with a score of 97/100, indicating a very well-optimized site. The main optimization opportunity is reducing unused JavaScript from Google Analytics, which is loading 48 KiB of unnecessary code that could be deferred or removed. Additionally, improving cache settings for Google's scripts could save an extra 4 KiB on repeat visits. While these improvements won't dramatically impact the already-strong performance, implementing them would help achieve a near-perfect score and ensure optimal loading speed for all users.

Other Optimization Recommendations

Extend Cache Headers for Static Assets

Low Impact+2 points estimated

Why It Matters:

Short cache lifetimes force repeat visitors to re-download resources unnecessarily, slowing subsequent page loads.

How to Fix:

Configure your web server to set cache-control headers with max-age of at least 31536000 (1 year) for static JavaScript files like Google's loader.js and call-tracking scripts. Add versioning to filenames for cache busting when updates are needed.

Implement Comprehensive Performance Monitoring

Low Impact+1 point estimated

Why It Matters:

With a 97 performance score, focus shifts to maintaining excellence and monitoring real-user metrics for regression detection.

How to Fix:

Set up Google Search Console Core Web Vitals monitoring to track real user data. Implement performance budgets in your deployment process. Add RUM (Real User Monitoring) to catch performance regressions before they impact users.

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

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