Implement Long-Term Asset Caching

How to optimize tarasahurley.com

Generic SiteScore: 68/100Analyzed January 2026

Implement Long-Term Asset Caching

Medium Impact+6 points estimated

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.

0Needs Improvement

What This Score Means

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.

Core Web Vitals Analysis

LCP

Largest Contentful Paint

9.2s
Poor

Good: < 2.5s

Measures how long it takes for the main content to appear on screen

INP

Interaction to Next Paint

157ms
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 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.

Other Optimization Recommendations

Remove Unused JavaScript Code

High Impact+18 points estimated

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.

Upgrade to Modern JavaScript

Medium Impact+8 points estimated

Why It Matters:

Legacy polyfills and transforms waste 61 KiB and add 250ms to LCP unnecessarily.

How to Fix:

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.

Want to Analyze YOUR Website?

Get AI-powered performance insights with actionable fixes in 30 seconds

More Generic Speed Tests

Generic Performance Resources

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