LCP
Largest Contentful Paint
2.5s
Needs Improvement
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
Optimize Image Responsive Sizing
How to optimize bloomhealthcenters.com
Optimize Image Responsive Sizing
Medium Impact+5 points estimated
Why It Matters
Images are being served at larger dimensions than displayed, wasting 32 KiB and potentially impacting LCP timing.
How to Fix
Configure NitroPack's image optimization to generate proper responsive breakpoints for the video thumbnail (reduce from 1280x720 to 1120x630). Update the staff images to serve 700x494 instead of 851x601. Add srcset attributes with multiple image sizes for different viewport widths.
0Good
What This Score Means
A score of 95 falls in the "Good" 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
16ms
Good
Good: < 200ms
Measures how quickly the page responds to user interactions
CLS
Cumulative Layout Shift
0.04
Good
Good: < 0.1
Measures visual stability - how much content shifts during page load
AI Performance Analysis
This website achieves an excellent performance score of 95/100, indicating very fast loading times with minimal optimization needed. The primary issue affecting page speed is excessive unused CSS code - the site is loading 73KB of unnecessary styling rules, with some stylesheets using as little as 3% of their code. While the site loads relatively quickly with First Contentful Paint at 2.1 seconds and Largest Contentful Paint at 2.5 seconds, cleaning up the unused CSS and implementing better image sizing (currently wasting 32KB on oversized images) could push this already high-performing site to near-perfect scores. The forced reflow issues in JavaScript are also causing minor performance hiccups that could be addressed for an even smoother user experience.
Other Optimization Recommendations
Remove Unused CSS Rules
Medium Impact+8 points estimatedWhy It Matters:
72 KiB of unused CSS is being loaded, wasting bandwidth and potentially delaying render-blocking resources.
How to Fix:
Configure NitroPack to purge unused CSS more aggressively, particularly from the combined stylesheets showing 90%+ waste. Use tools like PurifyCSS or UnCSS to identify critical above-the-fold CSS. Split CSS files to load only necessary styles for each page template.
Eliminate Forced Layout Reflows
High Impact+12 points estimatedWhy It Matters:
JavaScript is causing 86ms of forced reflows, blocking the main thread and potentially degrading user interaction responsiveness.
How to Fix:
Audit inline JavaScript in the main document for DOM queries that trigger layout recalculations. Batch DOM reads and writes to avoid repeated layout thrashing. Consider moving problematic scripts to load after initial page render or use requestAnimationFrame for layout-heavy operations.
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
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
Fix Element Render Delay
Your LCP element has 2.8 seconds of render delay, significantly impacting user experience.
Reduce Unused JavaScript Bundle
47% of your main JavaScript bundle (28KB) is unused, wasting 150ms of load time.
Eliminate Render Blocking Resources
Critical CSS and JavaScript files are blocking page render, delaying LCP by 600ms.
Remove Unused CSS Rules
40 KiB of unused CSS is adding 300ms to both FCP and LCP load times.