Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize gemini.google.com
Document latency causes 820ms delay affecting both LCP and FCP by 800ms each.
Remove the redirect chain from consent.google.com to gemini.google.com by serving content directly. Enable GZIP/Brotli compression on your server. Implement HTTP/2 server push for critical resources to reduce network round trips.
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 page has good performance with a score of 85/100, but faces significant loading delays that could be easily fixed. The biggest problem is multiple page redirects that waste 780 milliseconds before the page even starts loading, combined with slow server response times that add another 820 milliseconds of delay. Additionally, the site loads 130 KiB of unused JavaScript code that serves no purpose for users. Eliminating the redirects and optimizing the unused code could save over 1.5 seconds of loading time and dramatically improve the user experience.
Why It Matters:
Over 130KB of unused JavaScript delays LCP by 150ms and wastes bandwidth.
How to Fix:
Use webpack-bundle-analyzer to identify unused code in the large Google Scripts bundle (91KB). Implement code splitting to load only required modules. Remove or defer the feedback service script (30KB) until user interaction triggers it.
Why It Matters:
JavaScript queries of geometric properties after DOM changes cause 47ms of blocking reflow.
How to Fix:
Move all DOM reads before DOM writes in your JavaScript code. Use requestAnimationFrame for layout-triggering operations. Cache geometric property values instead of repeatedly querying offsetWidth and similar properties.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
91% of CSS (44 KiB) is unused and blocks initial render, delaying FCP by 100ms.
The hero background image is oversized (1182x1168 for 721x712 display) adding 600ms to LCP.
Unused JavaScript (452 KiB) delays LCP by 1.5 seconds and blocks main thread execution.
Over 316KB of unused JavaScript is loaded, wasting bandwidth and blocking the main thread.