Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize crawlbase.com
Unused JavaScript (452 KiB) delays LCP by 1.5 seconds and blocks main thread execution.
Remove or defer Intercom chat widget if not essential (214 KiB unused). Configure Google Analytics to load asynchronously after page interaction. Audit and remove unused tracking pixels from Reddit and Quora that contribute 98 KiB of waste.
A score of 60 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 website has poor performance with a score of 60/100, indicating significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 10 seconds, primarily caused by oversized background images that are much larger than needed for their display size, wasting 113 KB of data. The site is also loading 452 KB of unused JavaScript from third-party services like Intercom and analytics tools, which delays page interactivity to 13.8 seconds. Optimizing image sizes, removing unused code, and adding priority hints to critical images could dramatically improve loading speeds and boost the performance score by 30+ points.
Why It Matters:
The hero background image is oversized (1182x1168 for 721x712 display) adding 600ms to LCP.
How to Fix:
Generate responsive image variants for the background ellipse at actual display sizes. Add fetchpriority='high' attribute to the LCP image as recommended. Implement proper srcset with optimized WebP images sized for mobile, tablet, and desktop breakpoints.
Why It Matters:
91% of CSS (44 KiB) is unused and blocks initial render, delaying FCP by 100ms.
How to Fix:
Use PurgeCSS or UnCSS to remove unused styles from styles-fb7bf32739.css. Inline critical above-the-fold CSS directly in HTML head. Split remaining CSS and load non-critical styles asynchronously using media='print' onload technique.
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
Unminified JavaScript wastes 1.4 MB and causes 2.3 seconds of blocking execution time.
Large unoptimized images cause 10.4 MB of wasted bandwidth and trigger major layout shifts affecting CLS.
Blocking CSS resources delay First Contentful Paint by 5.4 seconds and waste 237 KiB of unused styles.
Critical CSS file blocks initial page render for 8.1 seconds, severely delaying FCP and LCP.