Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize getnett.app
Critical CSS and JavaScript files are blocking page render, delaying LCP by 600ms.
Inline critical CSS from _slug_.BP_1DDoQ.css directly in the HTML head. Defer the Cloudflare email decode script by adding 'defer' attribute or moving it to the end of body. Use Astro's built-in CSS inlining features for above-the-fold styles.
A score of 98 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 an excellent performance score of 98/100, indicating very fast loading times overall. However, the biggest issue is render-blocking resources that are delaying the initial page display by 600ms, particularly a Cloudflare email protection script and CSS file that prevent content from appearing quickly. The site also has a high element render delay of 2.8 seconds for the Largest Contentful Paint, and contains 27KB of unused JavaScript that could be removed or deferred. Addressing these render-blocking resources through inlining or deferring, along with cleaning up unused code, could make this already fast site even more responsive for users.
Why It Matters:
47% of your main JavaScript bundle (28KB) is unused, wasting 150ms of load time.
How to Fix:
Enable code splitting in your Astro build configuration to create smaller chunks. Use dynamic imports for components not needed on initial page load. Audit client.Dc9Vh3na.js to identify and remove unused dependencies or lazy load them.
Why It Matters:
Your LCP element has 2.8 seconds of render delay, significantly impacting user experience.
How to Fix:
Eliminate the forced reflow in index.astro script by batching DOM reads and writes. Move geometric property queries (offsetWidth) before DOM modifications. Consider using CSS transforms instead of layout-triggering properties for animations.
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 LCP element has 2.8 seconds of render delay, significantly impacting user experience.
47% of your main JavaScript bundle (28KB) is unused, wasting 150ms of load time.
40 KiB of unused CSS is adding 300ms to both FCP and LCP load times.
A 1MB product image is oversized by 1000x for its 40x40px display, wasting bandwidth and loading time.