LCP
Largest Contentful Paint
10.5s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize LCP Image Discovery
How to optimize dodgerblue.fox.193444.hostingersite.com
Optimize LCP Image Discovery
High Impact+15 points estimated
Why It Matters
The hero image takes 10.5 seconds to load because it's not discoverable from HTML, causing massive LCP delays.
How to Fix
Add fetchpriority='high' to the Depicter slider's hero image. Preload the LCP image using <link rel='preload' as='image'> in the document head. Ensure hero images are directly in HTML rather than loaded via JavaScript to improve discovery time.
0Poor
What This Score Means
A score of 28 falls in the "Poor" 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
337ms
Needs Improvement
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.27
Poor
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This WordPress site has severe performance issues with a score of only 28/100. The biggest problem is render-blocking CSS and JavaScript resources that are delaying the initial page render by nearly 4 seconds, causing your First Contentful Paint to take 3.2 seconds and Largest Contentful Paint to reach a poor 10.5 seconds. The site is loading over 650KB of unused JavaScript (including heavy reCAPTCHA files) and 200KB of unused CSS that could be eliminated or deferred. Additionally, images lack proper width and height attributes causing layout shifts, and the main thread is blocked for 5.4 seconds by excessive JavaScript execution. Prioritizing the removal of render-blocking resources, eliminating unused code, and optimizing images could potentially improve your score by 40+ points and dramatically enhance user experience.
Other Optimization Recommendations
Eliminate Render-Blocking CSS Resources
High Impact+25 points estimatedWhy It Matters:
Render-blocking stylesheets delay first paint by 3.8 seconds, severely impacting user experience and Core Web Vitals.
How to Fix:
Use a WordPress optimization plugin like WP Rocket or Autoptimize to inline critical CSS and defer non-critical stylesheets. Specifically target ElementsKit, YouTube feed, and Royal Elementor Addons CSS files that are blocking initial render. Remove unused CSS rules from these plugin stylesheets using PurgeCSS or similar tools.
Reduce Unused JavaScript Payload
High Impact+18 points estimatedWhy It Matters:
651 KiB of unused JavaScript delays LCP by 1.05 seconds and blocks main thread execution.
How to Fix:
Remove or replace the reCAPTCHA implementation that's loading 450+ KiB of unused code. Audit FluentForm conversational features - disable if not needed or load conditionally. Use Asset CleanUp Pro to disable unused plugins on specific pages and implement code splitting for remaining JavaScript.
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 WordPress Speed Tests
WordPress Performance Resources
Optimize Hero Image Delivery
The 664KB hero background image is delaying LCP by 1.6 seconds as it's not optimized or prioritized.
Remove Unused JavaScript and CSS
Over 2.4MB of unused JavaScript and 411KB of unused CSS are slowing LCP by 7+ seconds.
Eliminate Render-Blocking Resources
Critical CSS and JavaScript files are blocking initial page render, delaying FCP by 4.4 seconds.
Extend Cache Lifetimes for Assets
Short cache durations force unnecessary re-downloads on repeat visits, slowing LCP by 150ms.