Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize wp.astra.vercel.app
Two Elementor CSS files block initial render and delay FCP by 350ms with critical path timing issues.
Inline critical CSS from widget-social-icons.min.css and widget-icon-list.min.css directly in HTML head. Defer non-critical CSS using media='print' onload technique or async CSS loading. Configure Elementor to generate inline CSS for above-the-fold widgets.
A score of 99 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 has excellent performance with an outstanding score of 99/100, indicating a fast-loading site that provides great user experience. The main issue holding back perfect performance is unused CSS, particularly a FontAwesome stylesheet that's completely unused but still being loaded, wasting 12 KB of data and adding 150ms to page load time. Additionally, some CSS files for Elementor widgets are blocking the initial page render, which could delay when users first see content by about 330ms. Removing the unused FontAwesome CSS and deferring the render-blocking stylesheets would likely achieve a perfect 100/100 score while making the page load even faster for users.
Why It Matters:
Unused CSS wastes 12 KiB and delays LCP by 150ms, especially the completely unused FontAwesome stylesheet.
How to Fix:
Remove or defer the FontAwesome CSS file at /content/plugins/elementor/assets/lib/font-awesome/css/fontawesome.css since it's 100% unused. Use Elementor's selective loading feature to only load required icon fonts. Consider using CSS purging tools like PurgeCSS for production builds.
Why It Matters:
Forced reflows consume 47ms of main thread time due to DOM geometry queries after style changes.
How to Fix:
Batch DOM reads and writes to avoid layout thrashing in custom JavaScript. Use CSS transforms instead of changing layout properties like width/height. Implement virtual scrolling or pagination if dealing with large dynamic content lists.
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
Missing image dimensions cause layout shifts and poor caching wastes 841KB on repeat visits.
The hero background image (bg.png) is 460KB and has a 4.7 second resource load delay, causing poor LCP of 6.1 seconds.
CSS files are blocking initial page render for 2.6 seconds, significantly delaying First Contentful Paint.
Forced reflows consume 47ms of main thread time due to DOM geometry queries after style changes.