Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize bb.open.com
Plausible analytics script has only 1-minute cache lifetime, causing unnecessary re-downloads for returning visitors.
Configure your server or CDN to serve the analytics script with longer cache headers (e.g., 1 week). If using a reverse proxy, set cache-control headers to max-age=604800. Consider self-hosting the analytics script for better cache control.
A score of 100 falls in the "Good" 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 achieves a perfect performance score of 100/100, indicating excellent loading speeds and user experience. However, there are still optimization opportunities that could make the site even faster, particularly the render-blocking CSS file (banner.B9Kfk2py.css) which is delaying initial page rendering by nearly 1 second and could be deferred or inlined. The site also has a chain of font loading dependencies where custom fonts load after the CSS, creating a 319ms loading sequence that could be optimized with font preloading. Minor improvements include setting longer cache lifetimes for the analytics script and addressing some forced reflows in JavaScript, but overall this site is already performing exceptionally well.
Why It Matters:
The main CSS file is blocking initial render for 950ms, significantly delaying both LCP and FCP.
How to Fix:
Inline critical CSS directly in the HTML head for above-the-fold content. Load the remaining CSS asynchronously using media='print' onload technique or rel='preload'. Split CSS into critical and non-critical parts to reduce blocking time.
Why It Matters:
Three Space Grotesk font variants are loaded sequentially, extending the critical path to 319ms.
How to Fix:
Add font-display: swap to @font-face rules to prevent invisible text during font load. Preload only the most critical font weight (400) using rel='preload'. Consider using a variable font to reduce the number of font files from three to one.
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.