Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize wildforkfoods.com
2.6MB of unused JavaScript increases LCP by 2.8 seconds and blocks main thread for critical user interactions.
Implement Next.js dynamic imports for large components that aren't immediately needed. Use Next.js bundle analyzer to identify and remove unused dependencies. Split large chunks using Next.js code splitting features and load non-critical scripts after page interaction.
A score of 4 falls in the "Poor" 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 Next.js/React site has severe performance issues with a critically low score of 4/100. The biggest problem is massive JavaScript bloat, with over 10 seconds spent processing scripts and 2.6MB of unused JavaScript that's delaying page interactivity for nearly a minute. The site also suffers from poorly optimized images (4MB+ in oversized files), extensive layout shifts from unsized images and web fonts, and an enormous 13MB total page weight that's costing users significant load time and data usage. Removing unused JavaScript, properly sizing images, and implementing efficient caching could potentially improve the score by 60+ points and transform the user experience from unusable to acceptable.
Why It Matters:
Unsized images cause massive CLS of 1.111, severely degrading user experience as content jumps around during loading.
How to Fix:
Add explicit width and height attributes to all Next.js Image components, especially product images in the ProductCarousel section. Use Next.js Image component's priority prop for above-the-fold images. Reserve space for dynamically loaded content with CSS aspect-ratio or min-height properties.
Why It Matters:
Web fonts cause 515ms of layout shift and block text rendering, delaying FCP and creating poor user experience.
How to Fix:
Add font-display: swap to all @font-face declarations in your CSS. Preload critical fonts (Oswald, Montserrat) using Next.js Head component with <link rel='preload'>. Use font-metric overrides in CSS to match fallback fonts and reduce layout shifts during font swaps.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Next.js Speed Tests
Web fonts cause 515ms of layout shift and block text rendering, delaying FCP and creating poor user experience.
Unsized images cause massive CLS of 1.111, severely degrading user experience as content jumps around during loading.
Missing image dimensions cause layout shifts and poor caching wastes 120 KiB on repeat visits.
Product images are 12.8 MB total with poor LCP of 12 seconds due to oversized JPEGs.
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.