LCP
Largest Contentful Paint
3.0s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Google Fonts Loading Strategy
How to optimize wp.astra.vercel.app
Optimize Google Fonts Loading Strategy
High Impact+12 points estimated
Why It Matters
Multiple Google Fonts requests create a dependency chain that extends to 884ms, blocking rendering and contributing to poor FCP.
How to Fix
Consolidate font requests into a single Google Fonts URL to reduce network requests. Add preconnect hints for fonts.googleapis.com and fonts.gstatic.com in your theme's header. Consider self-hosting fonts or using font-display: swap for faster text rendering during font load.
0Needs Improvement
What This Score Means
A score of 89 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
16ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.00
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This website has good performance with a score of 89/100, but there's still room for improvement on loading speed. The biggest issue is render-blocking CSS files that are delaying the First Contentful Paint by 2.9 seconds, with an estimated savings of 1.76 seconds if optimized. The main culprits are Google Fonts requests and Elementor plugin stylesheets that block the page from rendering quickly. To improve performance, consider deferring non-critical CSS, optimizing font loading with better display settings, and removing 12KB of unused CSS from the Font Awesome library.
Other Optimization Recommendations
Eliminate Render-Blocking CSS Resources
High Impact+15 points estimatedWhy It Matters:
Render-blocking CSS is delaying First Contentful Paint by 1,750ms, significantly impacting user experience.
How to Fix:
Inline critical CSS directly in the HTML head for above-the-fold content. Defer non-critical CSS files like widget-icon-list.min.css and widget-social-icons.min.css using media='print' onload='this.media="all"' or async CSS loading. Use WordPress optimization plugins like WP Rocket or Autoptimize to automatically handle CSS optimization.
Remove Unused CSS and Fonts
Medium Impact+8 points estimatedWhy It Matters:
12KB of completely unused FontAwesome CSS is wasted bandwidth that doesn't contribute to page rendering.
How to Fix:
Audit your Elementor widgets to identify if FontAwesome icons are actually needed. If unused, disable FontAwesome loading in Elementor settings under Advanced > CSS Print Method. For necessary icons, consider switching to inline SVG icons or a lighter icon solution to reduce payload size.
Keep Your Site Fast After Optimization
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.
Explore DeployHQ →Trusted by engineering teams shipping high-performance sites
Want to Analyze YOUR Website?
Get AI-powered performance insights with actionable fixes in 30 seconds
Related Performance Analyses
More Generic Speed Tests
Generic Performance Resources
Fix Image Dimensions and Caching
Missing image dimensions cause layout shifts and poor caching wastes 841KB on repeat visits.
Optimize LCP Image Performance
The hero background image (bg.png) is 460KB and has a 4.7 second resource load delay, causing poor LCP of 6.1 seconds.
Eliminate Render-Blocking CSS Resources
CSS files are blocking initial page render for 2.6 seconds, significantly delaying First Contentful Paint.
Optimize JavaScript Layout Queries
Forced reflows consume 47ms of main thread time due to DOM geometry queries after style changes.