LCP
Largest Contentful Paint
3.1s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Unused CSS and JavaScript
How to optimize eatoutthebox.co.za
Reduce Unused CSS and JavaScript
High Impact+18 points estimated
Why It Matters
Unused CSS (119 KiB) and JavaScript (363 KiB) are blocking rendering and extending load times by 450ms for LCP.
How to Fix
Use Asset CleanUp or Perfmatters plugin to disable unused reCAPTCHA resources on non-contact pages. Remove or defer the duplicate reCAPTCHA script loading. Enable LiteSpeed Cache's CSS/JS optimization to purge unused code automatically.
0Good
What This Score Means
A score of 90 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
196ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.05
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This WordPress site has good performance with a score of 90/100, but there are still some significant issues holding it back. The biggest problem is excessive main-thread work (2.1 seconds) caused by heavy JavaScript processing, particularly from unused reCAPTCHA code that's wasting 363 KiB of bandwidth. The site also suffers from poor interactivity with an 11.1-second Time to Interactive, plus image optimization issues that could save 217 KiB in file sizes. Reducing unused JavaScript, optimizing images, and cleaning up unused CSS (119 KiB wasted) would dramatically improve user experience and push this site closer to a perfect performance score.
Other Optimization Recommendations
Optimize and Compress Product Images
High Impact+15 points estimatedWhy It Matters:
Large, uncompressed images are wasting 217 KiB and potentially impacting LCP performance with the main product image being 209 KiB oversized.
How to Fix:
Install ShortPixel or Smush plugin to automatically compress the Neapolitan pizza image and other product photos. Increase compression levels for product images since they're currently under-compressed. Set proper image dimensions in WooCommerce to match display sizes (300x300 for thumbnails).
Fix Font Display and Image Dimensions
Medium Impact+8 points estimatedWhy It Matters:
Missing image dimensions cause layout shifts affecting CLS, and fonts without proper display settings delay text rendering by 60ms.
How to Fix:
Add explicit width='25' height='25' attributes to phone and envelope footer icons in your WordPress theme templates. Set font-display: swap in your theme's CSS for FontAwesome and Outfit fonts to prevent invisible text during font load.
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
Fix Font Display and Image Dimensions
Missing image dimensions cause layout shifts affecting CLS, and fonts without proper display settings delay text rendering by 60ms.
Optimize and Compress Product Images
Large, uncompressed images are wasting 217 KiB and potentially impacting LCP performance with the main product image being 209 KiB oversized.
Remove Unused Elementor CSS
1.24MB of unused CSS blocks rendering and wastes bandwidth on every page load.
Optimize LCP Image Discovery
LCP element suffers 3.9 second resource load delay because it's not discoverable in initial HTML.