Reduce Unused JavaScript Code

How to optimize armycadets.com

Generic SiteScore: 53/100Analyzed February 2026

Reduce Unused JavaScript Code

Medium Impact+8 points estimated

Why It Matters

321KB of unused JavaScript increases download time and blocks the main thread for 2.4 seconds.

How to Fix

Remove or defer unused portions of Vimeo player scripts and Google Analytics code. Use tree-shaking to eliminate dead code from vendor libraries. Implement code splitting to load JavaScript only when needed for specific page sections.

0Needs Improvement

What This Score Means

A score of 53 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.2s
Poor

Good: < 2.5s

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

INP

Interaction to Next Paint

199ms
Good

Good: < 200ms

Measures how quickly the page responds to user interactions

CLS

Cumulative Layout Shift

0.26
Poor

Good: < 0.1

Measures visual stability - how much content shifts during page load

AI Performance Analysis

The Army Cadets website has poor performance with a score of 53/100, primarily due to render-blocking CSS and JavaScript files that are delaying the page's initial display by over 3 seconds. The biggest issue is that critical CSS files (especially the main stylesheet and external fonts) are blocking the browser from showing content quickly, resulting in a slow 4.1-second First Contentful Paint and causing significant layout shifts as elements load. The site is also carrying a heavy 17MB payload with lots of unused CSS and JavaScript code that could be removed or deferred. Fixing the render-blocking resources alone could save 3.4 seconds in load time and dramatically improve the user experience.

Other Optimization Recommendations

Fix Render-Blocking CSS Resources

High Impact+25 points estimated

Why It Matters:

Render-blocking CSS delays LCP by 3.4 seconds, preventing any content from appearing until all stylesheets load.

How to Fix:

Inline critical CSS for above-the-fold content directly in the HTML head. Use media='print' onload='this.media="all"' to defer non-critical CSS like FontAwesome and Typekit fonts. Minify the main stylesheet to reduce its 54KB size by 27%.

Eliminate Cumulative Layout Shift

High Impact+15 points estimated

Why It Matters:

CLS score of 0.262 indicates significant content jumping that degrades user experience and Core Web Vitals.

How to Fix:

Add explicit width and height attributes to the unsized quote images causing layout shifts. Reserve space for the featured banner textbox with CSS min-height. Use font-display: swap for custom fonts to prevent invisible text periods.

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