Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize dtagrimart.com
65% of Swiper.js and 97% of CSS are unused, adding unnecessary 49 KiB to page weight.
Create custom Swiper build with only needed modules instead of full bundle. Extract critical CSS for above-the-fold content and defer the rest. Remove unused Bootstrap components from all.min.css. Consider code-splitting to load Swiper only when needed.
A score of 95 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.
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 e-commerce site achieves an excellent performance score of 95/100, indicating very strong overall optimization. However, the biggest remaining issue is oversized images that are wasting 219 KiB of bandwidth - particularly a chickpea product image that's being served at 1940x2000 pixels but only displayed at a much smaller 1045x697 size. Additionally, there's unused JavaScript code (28 KiB from the Swiper carousel library) and unminified CSS (11 KiB) that could be cleaned up. While these optimizations won't dramatically change the already-high score, properly sizing images and removing unused code would reduce page load times and improve the user experience, especially for visitors on slower connections.
Why It Matters:
Images are oversized and under-compressed, wasting 219 KiB and potentially delaying LCP.
How to Fix:
Resize the main product image from 1940x2000 to match display dimensions (~388x400). Implement responsive images using srcset attribute. Increase compression for WebP images while maintaining visual quality. Use image optimization tools or CDN with automatic resizing.
Why It Matters:
LCP breakdown shows 1.9 seconds of resource load delay, significantly impacting perceived performance.
How to Fix:
Add fetchpriority='high' to the main product image (already implemented for feature image). Preload critical images above the fold. Optimize server response times and consider using a CDN for faster asset delivery. Move non-critical JavaScript loading to after LCP element loads.
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.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Short 1-hour cache lifetime for static assets wastes 3.6MB of repeat downloads for returning visitors.
Unsized images are causing a CLS score of 0.252, significantly hurting user experience and rankings.
Large unoptimized images are causing 1.9MB of wasted bandwidth and delaying LCP by 750ms.
LCP breakdown shows 1.9 seconds of resource load delay, significantly impacting perceived performance.