Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize functional.colonialaesthetic.com
JavaScript is forcing expensive layout recalculations that block the main thread and delay interactivity.
Refactor FAQ section and video testimonials components to avoid reading layout properties after DOM changes. Batch DOM reads and writes separately. Use CSS transforms instead of changing geometric properties like offsetWidth to prevent forced reflows.
A score of 61 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 61/100, primarily due to excessive JavaScript blocking the page from becoming interactive for nearly 12 seconds. The biggest issue is 420KB of unused JavaScript code from YouTube embeds, Facebook tracking, and other third-party scripts that are slowing down page loading by over 600 milliseconds. The site also suffers from 105KB of unused CSS and inefficient caching that could save an additional 188KB on repeat visits. Removing or deferring unnecessary JavaScript, especially from YouTube and Facebook integrations, would provide the most significant performance improvement and could boost the score by 15-20 points.
Why It Matters:
Unused JavaScript wastes 420 KiB and delays LCP by 600ms while blocking main thread execution.
How to Fix:
Remove or defer Facebook Pixel (93KB unused), Hotjar analytics (57KB unused), and YouTube embed scripts until needed. Use async/defer attributes for third-party scripts. Consider loading tracking scripts only after user interaction to reduce initial bundle size.
Why It Matters:
The LCP element has a 3-second render delay causing poor perceived performance and user frustration.
How to Fix:
Optimize the hero section H1 element by removing render-blocking CSS and JavaScript that delays its appearance. Inline critical CSS for above-the-fold content. Preload the hero background image and ensure proper font loading to eliminate layout shifts during render.
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
The oversized logo image wastes 97 KiB and delays LCP by 450ms while being displayed much smaller than its actual size.
126 KiB of unused JavaScript from Google Analytics and GTM delays LCP by 900ms and wastes bandwidth.
Render blocking CSS and fonts delay LCP and FCP by 1,050ms, preventing users from seeing content immediately.
Award images are oversized by 441KB and lack explicit dimensions, causing layout shifts.