Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize eatoutthebox.co.za
194KB of unused JavaScript creates 850ms of blocking time and extends Time to Interactive to 9.6 seconds.
Use LiteSpeed Cache's JS minification and combination features to reduce file sizes. Defer Google Tag Manager and Google Sign-In scripts using the 'Delay JS' feature. Remove legacy JavaScript transforms by updating your build process to target modern browsers only.
A score of 58 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.
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 WordPress site has poor performance issues with a score of 58/100. The biggest problem is extremely slow loading times, with your Largest Contentful Paint taking 8.7 seconds and pages becoming interactive only after 9.6 seconds - both far exceeding Google's recommended thresholds. The main culprits are oversized images that waste 166KB of bandwidth, 78KB of unused CSS that blocks rendering, and 194KB of unused JavaScript that slows down loading. Optimizing image sizes, removing unused code, and implementing proper caching could dramatically improve your score by 30+ points and provide a much better user experience.
Why It Matters:
Render-blocking CSS delays First Contentful Paint by 950ms and contains 80KB of unused styles that slow down page rendering.
How to Fix:
Use LiteSpeed Cache's CSS optimization to inline critical CSS and defer non-critical styles. Enable 'Load CSS Asynchronously' and 'Remove Unused CSS' options in the plugin settings. Consider splitting the large CSS file into smaller, page-specific stylesheets.
Why It Matters:
Oversized images waste 166KB and delay LCP by 200ms, while the LCP image lacks priority hints for faster loading.
How to Fix:
Add fetchpriority='high' to your hero banner image in WordPress theme files. Use LiteSpeed Cache's image optimization to generate properly sized responsive images with srcset attributes. Enable WebP conversion and set appropriate compression levels for the category images.
Get AI-powered performance insights with actionable fixes in 30 seconds
More WordPress Speed Tests
Custom fonts block text rendering for 880ms, delaying FCP and creating poor user experience.
LCP element has 7.5 second resource load delay because it's not discoverable from initial HTML.
Unused assets waste 130KB of bandwidth and delay FCP by 1.05 seconds, severely impacting Core Web Vitals.
CSS files are blocking page rendering and delaying FCP by 8.99 seconds, severely impacting user experience.
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.