Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize willjobz.webapp..willjobz.staging.asia.southeast1.hosted.app
Your LCP element has a massive 2.57-second render delay, causing the 9.7s LCP time that's killing your Core Web Vitals.
Move the LCP paragraph element higher in your React component tree to render earlier. Remove any conditional rendering logic that delays this text. Use Next.js getStaticProps or getServerSideProps to pre-render content server-side instead of client-side hydration delays.
A score of 57 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 Next.js/React website has poor performance with a score of 57/100, indicating significant issues that affect user experience. The biggest problem is an extremely slow Largest Contentful Paint of 9.7 seconds, primarily caused by a massive 2.6-second element render delay and excessive unused JavaScript (608 KiB of waste from reCAPTCHA and Google Analytics scripts). The site is also loading 56 KiB of unused CSS and has render-blocking stylesheets that delay initial page rendering. To improve performance, the development team should remove or defer unused JavaScript, optimize CSS delivery by eliminating unused styles, and investigate why the main content element takes so long to render after the page loads.
Why It Matters:
Unused JavaScript is consuming 608 KiB and delaying LCP by 4.2 seconds, making it the biggest performance bottleneck.
How to Fix:
Configure Next.js bundle analyzer to identify dead code in your chunks. Remove unused reCAPTCHA instances (229KB+ waste detected). Use dynamic imports for Google Analytics and defer non-critical third-party scripts until after page load. Enable tree-shaking in your webpack config.
Why It Matters:
Render-blocking CSS files are delaying first paint by 611ms and contributing to the poor FCP score.
How to Fix:
Use Next.js built-in CSS optimization by moving critical styles inline with styled-jsx or CSS-in-JS. Split your 17KB CSS file into critical and non-critical parts using Next.js automatic CSS splitting. Remove 100% unused reCAPTCHA CSS (42KB) by loading it only when needed.
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 Next.js Speed Tests
Render-blocking CSS files are delaying first paint by 611ms and contributing to the poor FCP score.
Unused JavaScript is consuming 608 KiB and delaying LCP by 4.2 seconds, making it the biggest performance bottleneck.
Oversized images waste 448 KiB and your logo alone is 2852x2696 but displayed at 70x70 pixels.
570 KiB of unused JavaScript is delaying LCP by 2.85 seconds and blocking user interactions.