Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize eotb.moducraft.io
CSS and JavaScript files are blocking initial render for 1,230ms, severely delaying First Contentful Paint.
In LiteSpeed Cache, enable 'Inline CSS Async' for critical CSS and defer non-critical styles. Move jQuery and other scripts to load asynchronously using defer attribute. Remove or defer the Cloudflare email-decode script which isn't critical for initial render.
A score of 70 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 with a score of 70/100, indicating significant room for improvement. The biggest problem is an extremely slow Largest Contentful Paint of 7.6 seconds, primarily caused by render-blocking CSS and JavaScript files that delay the initial page render by over 1.2 seconds. The site is also wasting 78KB on unused CSS and has oversized images that could be reduced by 166KB through proper compression and responsive sizing. Addressing these render-blocking resources and optimizing images could dramatically improve load times and boost the performance score by 20+ points.
Why It Matters:
Your LCP image is lazy-loaded and not discoverable in HTML, delaying LCP by 1,269ms and causing the poor 7.6s LCP score.
How to Fix:
Disable lazy loading for the hero banner image by adding loading='eager' and fetchpriority='high' attributes. In LiteSpeed Cache settings, exclude above-the-fold images from lazy loading. Add a preload link tag for the banner image in your theme's header.php.
Why It Matters:
Your main CSS file contains 86% unused code (78KB waste), slowing down page load by 300ms.
How to Fix:
Use LiteSpeed Cache's 'CSS Minify' and 'Remove Unused CSS' features to eliminate dead code. Configure critical CSS generation for above-the-fold content. Consider splitting CSS into page-specific files rather than one large stylesheet.
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.