LCP
Largest Contentful Paint
12.0s
Poor
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Image Dimensions and Compression
How to optimize 7dots.com
Generic SiteScore: 57/100Analyzed January 2026
Optimize Image Dimensions and Compression
Medium Impact+8 points estimated
Why It Matters
Case study images are oversized (500x500 vs 299x299 display) and poorly compressed, wasting 270 KiB of bandwidth.
How to Fix
Implement responsive images using srcset with properly sized variants (299px, 598px for retina). Apply modern compression techniques to reduce file sizes by 40-50%. Convert PNG images to WebP format for better compression while maintaining quality.
0Needs Improvement
What This Score Means
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.
Core Web Vitals Analysis
INP
Interaction to Next Paint
166ms
Good
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 57/100, indicating significant user experience issues. The biggest problem is render-blocking CSS files that are delaying the page from displaying content, causing a slow First Contentful Paint of 4.6 seconds and an extremely poor Largest Contentful Paint of 12 seconds. The site is also loading 355 KiB of unused JavaScript from Google Tag Manager and cookie consent scripts, further slowing down the page. Fixing the render-blocking resources could save 1.2 seconds of load time, while optimizing images and removing unused code could provide additional improvements of several hundred kilobytes in data savings.
Other Optimization Recommendations
Eliminate Render-Blocking CSS
High Impact+18 points estimatedWhy It Matters:
Multiple CSS files are blocking initial render, delaying LCP by 1.2 seconds and preventing users from seeing content.
How to Fix:
Combine the 6 separate block-specific CSS files (blockForm.css, blockTeamMember.css, etc.) into a single minified stylesheet. Inline critical above-the-fold CSS directly in the HTML head. Use media queries or loadCSS to defer non-critical styles until after page load.
Remove Unused JavaScript
High Impact+15 points estimatedWhy It Matters:
355 KiB of unused JavaScript is slowing page load by 1.85 seconds and blocking main thread execution.
How to Fix:
Audit Google Tag Manager implementation to remove unused triggers and tags. Implement code splitting to load only necessary JavaScript per page. Use tree shaking to eliminate dead code from the 49KB app.js bundle. Consider replacing heavy third-party scripts with lighter alternatives.
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
Remove Unused JavaScript Code
Google Tag Manager scripts contain 139KB of unused code, slowing LCP by 600ms and wasting processing time.
Optimize Video File Caching
17MB of video content has zero cache lifetime, forcing full re-downloads on every visit and wasting 69MB of bandwidth.
Defer Render-Blocking JavaScript
JavaScript files are blocking initial page render, delaying FCP by 750ms and preventing users from seeing content.
Remove Unused CSS and JavaScript
136KB of unused JavaScript and 63KB of unused CSS waste bandwidth and slow down page parsing.
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