LCP
Largest Contentful Paint
5.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Add Priority Hints to LCP Image
How to optimize moducraft.org.za
Add Priority Hints to LCP Image
High Impact+6 points estimated
Why It Matters
The LCP element lacks fetchpriority=high attribute, which could improve resource loading prioritization and reduce the 5.0s LCP time.
How to Fix
Identify your hero section's main image or background. Add fetchpriority='high' attribute to the image tag or preload link. Ensure the LCP resource is preloaded in the document head with <link rel='preload' as='image' href='hero-image.jpg' fetchpriority='high'>.
0Needs Improvement
What This Score Means
A score of 76 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
104ms
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 moderate performance issues with a score of 76/100, but several critical problems are slowing it down significantly. The biggest issue is an extremely slow Largest Contentful Paint of 5.0 seconds, which means visitors wait far too long to see the main content load. The primary culprit is 66 KiB of unused JavaScript (mainly from Google Analytics tracking code) that's blocking the page from loading efficiently. Quick wins include removing or deferring this unused JavaScript, adding fetchpriority="high" to the main image, and improving cache settings for key resources, which together could easily boost the performance score above 85 and dramatically improve user experience.
Other Optimization Recommendations
Remove Unused Google Analytics JavaScript
High Impact+8 points estimatedWhy It Matters:
Unused JavaScript is wasting 67KB and delaying LCP by 600ms with only 42% of Google Tag Manager code being used.
How to Fix:
Audit your Google Analytics implementation and remove unused tracking features. Consider switching to GA4's minimal gtag implementation or use Partytown to run analytics in a web worker. Defer the analytics script loading until after page interaction using async/defer attributes.
Inline Critical CSS and Defer Non-Critical
Medium Impact+4 points estimatedWhy It Matters:
Render-blocking CSS is delaying initial paint by 160ms and preventing faster content rendering.
How to Fix:
Extract above-the-fold CSS from your main stylesheet and inline it in the HTML head. Load the remaining CSS asynchronously using media='print' onload="this.media='all'" technique. Consider using tools like Critical or PurgeCSS to identify and extract critical styles automatically.
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
Extend Cache Lifetimes
Short cache durations force unnecessary re-downloads on repeat visits, slowing performance.
Eliminate Unused JavaScript Code
67KB of unused JavaScript increases bundle size and slows initial page load.
Implement Responsive Image Delivery
Oversized images delay LCP by 300ms and waste 70KB of bandwidth on mobile devices.
Inline Critical CSS and Defer Non-Critical
Render-blocking CSS is delaying initial paint by 160ms and preventing faster content rendering.