LCP
Largest Contentful Paint
19.7s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce Unused JavaScript Payload
How to optimize weave.living.com
Generic SiteScore: 43/100Analyzed January 2026
Reduce Unused JavaScript Payload
High Impact+18 points estimated
Why It Matters
1,300 KiB of unused JavaScript is blocking the main thread and delaying LCP by 3.45 seconds.
How to Fix
Enable code splitting in Next.js using dynamic imports for non-essential components. Remove or lazy-load the oversized a3319169 chunk (330KB unused). Defer Google Analytics and Facebook Pixel loading until after page interaction using next/script with strategy='afterInteractive'.
0Poor
What This Score Means
A score of 43 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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
252ms
Needs Improvement
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 poor performance with a score of 43/100, indicating significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 19.7 seconds, primarily caused by oversized images that are much larger than their display dimensions and inefficient server response times. The site is loading images at 720px when they're only displayed at 298px, wasting 462 KiB of bandwidth, while render-blocking CSS files are delaying initial page rendering by 1.6 seconds. Additionally, the server takes 760ms to respond initially, which cascades into longer load times for all other resources. Optimizing image sizes for their actual display dimensions, implementing modern image formats like WebP, improving server response times, and addressing the 1.3MB of unused JavaScript could dramatically improve performance and reduce the load time from nearly 20 seconds to under 3-4 seconds.
Other Optimization Recommendations
Optimize Image Delivery and Sizing
High Impact+12 points estimatedWhy It Matters:
Images are wasting 462 KiB through oversized dimensions and lack of modern formats, directly impacting LCP performance.
How to Fix:
Convert images to WebP/AVIF format for 20-35% size reduction. Implement responsive images using Next.js Image component with proper sizes attribute. Ensure served image dimensions match display dimensions (currently serving 720px images for 298px display).
Eliminate Render-blocking CSS Resources
High Impact+15 points estimatedWhy It Matters:
CSS files are blocking initial page render by 1,550ms, severely delaying First Contentful Paint.
How to Fix:
Inline critical CSS for above-the-fold content in Next.js using styled-jsx or CSS-in-JS. Move non-critical CSS to load asynchronously using next/dynamic. Combine smaller CSS files (8c0c7e9d and b2b9c812) into main stylesheet to reduce HTTP requests.
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
Implement Hero Image Optimization
The LCP hero image takes 21.6 seconds to load due to poor compression and oversized dimensions.
Optimize JavaScript Bundle Size
889KB of unused JavaScript delays LCP by 4.3 seconds and blocks user interactions for 1.3 seconds.
Eliminate Critical Request Redirects
Page redirects add 750ms delay before any content can load, severely impacting all Core Web Vitals.
Fix Image Delivery Performance
Images are oversized and unoptimized, wasting 462KB of bandwidth and slowing page load.
Frequently Asked Questions
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