Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize armycadets.com
40 KiB of unused CSS from TypeKit fonts delays rendering and wastes bandwidth.
Review TypeKit font usage and remove unused font weights/styles from your Adobe Fonts project. Add font-display: swap to prevent invisible text during font load. Consider self-hosting critical fonts to reduce network dependency chains.
A score of 85 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.
Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Interaction to Next Paint
Good: < 200ms
Measures how quickly the page responds to user interactions
Cumulative Layout Shift
Good: < 0.1
Measures visual stability - how much content shifts during page load
This website has good performance with a score of 85/100, but there's significant room for improvement in loading speed. The biggest issue is excessive unused JavaScript (164 KiB), which is delaying the Largest Contentful Paint to 4.0 seconds and making the site fully interactive only after 4.9 seconds. The site is also suffering from forced reflows that cause layout shifts and has 40 KiB of unused CSS that could be removed. Cleaning up the JavaScript, removing unused code, and optimizing the remaining CSS could easily push this site into the 90+ performance range and provide a noticeably faster user experience.
Why It Matters:
164 KiB of unused JavaScript delays LCP by 300ms and blocks user interactions.
How to Fix:
Audit and remove the unused xky8 script (74KB) and defer Google Analytics until after page load. Use code splitting to load jQuery only when needed. Consider removing or replacing heavy third-party scripts with lighter alternatives.
Why It Matters:
Forced reflows cause 40ms of blocking time that prevents smooth user interactions.
How to Fix:
Identify JavaScript code that reads layout properties after DOM changes. Batch DOM reads and writes separately to avoid triggering multiple reflows. Use CSS transforms instead of changing layout properties when possible.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Google Tag Manager scripts contain 139KB of unused code, slowing LCP by 600ms and wasting processing time.
17MB of video content has zero cache lifetime, forcing full re-downloads on every visit and wasting 69MB of bandwidth.
JavaScript files are blocking initial page render, delaying FCP by 750ms and preventing users from seeing content.
136KB of unused JavaScript and 63KB of unused CSS waste bandwidth and slow down page parsing.
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.