Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize radiation.monitor.com
Render-blocking CSS delays initial page rendering and prevents users from seeing content quickly.
Inline critical CSS styles directly in the HTML head section for above-the-fold content. Load cards.min.css asynchronously using media='print' onload='this.media="all"' technique. Split CSS into critical and non-critical parts to prioritize essential styling.
A score of 63 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 poor performance with a score of 63/100, indicating significant issues that hurt user experience. The biggest problem is extremely slow content loading - it takes 7.3 seconds for the largest element to appear and 4.6 seconds for any content to show up, which is far beyond Google's recommended limits. The main culprits are 292 KiB of unused JavaScript code (especially from Google Analytics and portal widgets) that's blocking the page from loading quickly, plus inefficient caching that forces users to re-download the same files repeatedly. Removing or deferring unused scripts and implementing proper long-term caching could dramatically improve load times and boost the performance score by 30+ points.
Why It Matters:
Unused JavaScript wastes 292 KiB and delays LCP by 1.2 seconds while blocking critical rendering.
How to Fix:
Audit Google Tag Manager setup and remove unused tracking scripts. Defer non-essential portal.min.js components using async/defer attributes. Split JavaScript bundles to load only required components on initial page load. Consider replacing heavy third-party scripts with lightweight alternatives.
Why It Matters:
Poor caching wastes 516 KiB on repeat visits and delays LCP by 2.4 seconds unnecessarily.
How to Fix:
Configure CDN cache headers for jsdelivr.net resources to cache for at least 1 year instead of 10 minutes. Add Cache-Control headers with max-age=31536000 for static assets. Implement versioning strategy to handle cache busting when files change.
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.