Remove Unused JavaScript Code

How to optimize newcenturyhonda.nabthat.com

Generic SiteScore: 76/100Analyzed January 2026

Remove Unused JavaScript Code

Medium Impact+8 points estimated

Why It Matters

54 KiB of unused JavaScript increases bundle size and slows page loading unnecessarily.

How to Fix

Analyze chunk-IALVUH5E.js (33KB unused) and chunk-BNMTKENX.js (21KB unused) to identify dead code. Use tree-shaking in your Angular build process. Split large chunks into smaller, route-specific bundles using lazy loading for non-critical components.

0Needs Improvement

What This Score Means

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

2.4s
Good

Good: < 2.5s

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

INP

Interaction to Next Paint

340ms
Needs Improvement

Good: < 200ms

Measures how quickly the page responds to user interactions

CLS

Cumulative Layout Shift

0.22
Needs Improvement

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 76/100. The biggest problem is an extremely slow server response time of 770ms, which is delaying page loading by 670ms and directly impacting how quickly users see content. The site is also suffering from significant layout shifts (CLS score of 0.219) caused by unsized images and web fonts loading, making the page feel unstable as it loads. Additionally, the site is bloated with 54KB of unused JavaScript and 15KB of unused CSS that could be removed to improve loading speed.

Other Optimization Recommendations

Optimize Server Response Time

High Impact+12 points estimated

Why It Matters:

Your server takes 770ms to respond, adding 650ms to both LCP and FCP metrics.

How to Fix:

Enable server-side compression (gzip/brotli) in your web server configuration. Implement CDN caching for static assets. Review server resources and database queries causing the 670ms delay. Consider upgrading hosting plan or optimizing backend processes.

Fix Layout Shift Issues

High Impact+10 points estimated

Why It Matters:

Multiple layout shifts (CLS: 0.219) create poor user experience and hurt Core Web Vitals.

How to Fix:

Add explicit width and height attributes to the NabThat logo image in footer. Reserve space for the slider section using CSS min-height. Preload critical fonts (Robotto-500, Robotto-400) using <link rel='preload'> to prevent font swap shifts.

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