LCP
Largest Contentful Paint
17.1s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Reduce JavaScript Execution Time
How to optimize weave.living.com
Generic SiteScore: 48/100Analyzed January 2026
Reduce JavaScript Execution Time
High Impact+25 points estimated
Why It Matters
JavaScript execution takes 5.0 seconds and blocks the main thread, severely impacting TBT and user interactions.
How to Fix
Code-split the 413KB main bundle (a3319169-bfd38be0eee3c695.js) using Next.js dynamic imports. Remove unused JavaScript - 80% of the main bundle and 61% of Google Tag Manager are unused. Defer non-critical scripts and implement lazy loading for components below the fold.
0Poor
What This Score Means
A score of 48 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
242ms
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 48/100, indicating significant user experience issues. The biggest problem is excessive JavaScript execution taking 5.0 seconds to process, which is severely blocking the page and causing a painfully slow Speed Index of 18.6 seconds. The site is loading 6.2MB of data with massive unused JavaScript (1.3MB wasted) and inefficient image delivery that could save 462KB, while the server response time of 820ms is also problematically slow. Reducing JavaScript payloads, optimizing images with modern formats like WebP, and improving server response times could dramatically improve performance by several seconds and boost the score by 30+ points.
Other Optimization Recommendations
Optimize Server Response Time
High Impact+18 points estimatedWhy It Matters:
The initial document takes 820ms to load, delaying both FCP and LCP by 700ms each.
How to Fix:
Implement server-side caching for your Next.js application using Redis or Vercel Edge Functions. Enable compression (gzip/brotli) on your server. Consider using a CDN like Cloudflare or Vercel's edge network to reduce latency. Optimize database queries and API responses.
Fix Image Delivery Performance
Medium Impact+12 points estimatedWhy It Matters:
Images are oversized and unoptimized, wasting 462KB of bandwidth and slowing page load.
How to Fix:
Use Next.js Image component with proper responsive sizes - your images are served at 720px but displayed at 298px. Configure your CDN (weave-living.com/cdn-cgi) to serve WebP/AVIF formats automatically. Set appropriate quality levels (60-75) and implement proper srcset attributes for different screen sizes.
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