Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize tarasahurley.com
Legacy polyfills and transforms waste 61 KiB and add 250ms to LCP unnecessarily.
Update your build process to target modern browsers (ES2017+) instead of transpiling to ES5. Remove Babel transforms for widely-supported features like Array.from, Object.assign, and arrow functions. Configure bundler to serve modern JS to capable browsers.
A score of 68 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 68/100, primarily due to excessive unused JavaScript that's slowing down page loading. The biggest issue is 316 KB of unnecessary JavaScript code from third-party widgets and tracking scripts (including Google Analytics and Facebook Pixel), which is causing your Largest Contentful Paint to take a sluggish 9.2 seconds. Additionally, the site is using outdated JavaScript with unnecessary polyfills that modern browsers don't need, wasting another 61 KB. Cleaning up unused JavaScript, updating to modern code, and improving caching policies could potentially save over 1.5 seconds in loading time and significantly boost your performance score.
Why It Matters:
316 KiB of unused JavaScript delays LCP by 1.5 seconds and blocks user interactions.
How to Fix:
Audit third-party widgets (widgetbe.com widget removing 89KB unused code). Defer Google Analytics and Tag Manager loading until after page load. Use code splitting to load only necessary JavaScript per page. Consider alternatives to heavy tracking scripts.
Why It Matters:
Poor cache policies force 123 KiB of unnecessary downloads on repeat visits, delaying LCP by 400ms.
How to Fix:
Configure your server to cache Facebook Pixel and third-party scripts for at least 1 year instead of 20 minutes. Add versioned filenames for cache busting. Set Cache-Control headers to 'public, max-age=31536000' for static assets.
Get AI-powered performance insights with actionable fixes in 30 seconds
More Generic Speed Tests
Google Tag Manager scripts contain 139KB of unused code, slowing LCP by 600ms and wasting processing time.
17MB of video content has zero cache lifetime, forcing full re-downloads on every visit and wasting 69MB of bandwidth.
JavaScript files are blocking initial page render, delaying FCP by 750ms and preventing users from seeing content.
136KB of unused JavaScript and 63KB of unused CSS waste bandwidth and slow down page parsing.
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.