Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize getnett.app
DOM geometry queries after style changes cause 37ms of unnecessary layout recalculation.
Review line 775 in your main script for offsetWidth/offsetHeight queries. Batch DOM reads before writes, or use CSS transforms instead of changing layout properties. Consider using the ResizeObserver API for responsive measurements.
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 overall performance. However, there are still some optimization opportunities that could improve user experience, with the biggest issue being oversized images that could save 677 KiB in download size and reduce Largest Contentful Paint by 150ms. The site is serving images at much larger dimensions than needed (1988x1742 pixels displayed at only 637x558), and implementing responsive images would significantly reduce bandwidth usage. Additionally, there's a render-blocking CSS file that could be optimized to save another 150ms in loading time, and some minor forced reflow issues in the JavaScript that could be addressed for smoother performance.
Why It Matters:
Your showcase images are 677 KiB oversized and delay LCP by 150ms.
How to Fix:
Resize app-showcase.png and app-showcase-light.png from 1988x1742 to 637x558 pixels to match display dimensions. Generate responsive image sizes using Astro's Image component with srcset. Consider using WebP format for additional 25-35% compression.
Why It Matters:
Your CSS file blocks initial render and delays both FCP and LCP by 150ms.
How to Fix:
Extract above-the-fold CSS from _slug_.4SWEsLHw.css and inline it in your HTML head. Use Astro's built-in CSS optimization or astro-critters plugin to automatically inline critical styles. Defer remaining CSS with rel='preload' and onload JavaScript.
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
Your CSS file blocks initial render and delays both FCP and LCP by 150ms.
Your showcase images are 677 KiB oversized and delay LCP by 150ms.
Missing image dimensions cause layout shifts and forced reflows waste 184ms of processing time.
The critical CSS file blocks initial render and delays LCP/FCP by 150ms.