Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize armycadets.com
JavaScript is forcing layout recalculations 80ms worth of blocking time, degrading user interaction responsiveness.
Audit your bundle.min.js file to identify DOM queries that trigger reflows. Batch DOM reads and writes separately to avoid layout thrashing. Use CSS transforms instead of changing geometric properties like width/height for animations.
A score of 54 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 Army Cadets website has poor performance with a score of 54/100, indicating significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 10.9 seconds, primarily caused by render-blocking CSS files that delay the initial page display by over 1.3 seconds. The site is also loaded down with 319 KB of unused JavaScript and 72 KB of unused CSS that could be removed or deferred to speed up loading. Addressing the render-blocking resources and eliminating unused code could potentially improve the performance score by 30+ points and drastically reduce loading times for visitors.
Why It Matters:
Render-blocking CSS is delaying your LCP by 1.35 seconds and preventing the page from painting content.
How to Fix:
Inline critical above-the-fold CSS directly in the HTML head section. Use media queries to defer non-critical CSS like print styles. Load remaining CSS asynchronously using rel='preload' with onload callback or a plugin like WP Rocket's CSS optimization feature.
Why It Matters:
319 KiB of unused JavaScript is adding 1.8 seconds to your LCP and blocking the main thread.
How to Fix:
Use a plugin like Asset CleanUp to disable unused scripts on specific pages. Remove or replace the heavy Vimeo player scripts with a lighter alternative. Defer Google Analytics and other tracking scripts to load after page interaction using gtag or Google Tag Manager's built-in delays.
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.