Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize jacksonhewitt.com
227 KiB of unused JavaScript delays LCP by 1.35 seconds and blocks user interactions.
Audit Google Tag Manager implementation to remove unused tags and triggers. Split Vue.js components to load only required modules for each page. Tree-shake third-party libraries and use dynamic imports for non-critical features. Consider replacing the full jQuery library with native JavaScript for simple DOM operations.
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, indicating significant user experience issues. The biggest problem is an extremely slow Largest Contentful Paint of 9.0 seconds, caused primarily by oversized and uncompressed images that are wasting 730 KB of unnecessary data transfer. The site is also loading 227 KB of unused JavaScript code and has render-blocking CSS files that delay initial page display by over 2 seconds. Optimizing images by compressing them and serving appropriately-sized versions, removing unused code, and implementing proper caching could dramatically improve load times and boost the performance score by 30+ points.
Why It Matters:
730 KiB of unoptimized images significantly impact page load time and user experience.
How to Fix:
Compress the hero image from 494KB to under 100KB using modern formats like WebP. Implement responsive images with srcset to serve appropriately sized images for different devices. Add explicit width and height attributes to prevent layout shifts during image loading.
Why It Matters:
Render-blocking CSS delays first paint by 2.25 seconds, severely impacting user perception.
How to Fix:
Inline critical CSS for above-the-fold content directly in the HTML head. Use media queries or preload hints for non-critical stylesheets. Minify all CSS files to reduce the 32 KiB of unnecessary whitespace and comments. Consider combining smaller CSS files to reduce HTTP requests.
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
85 KiB of unused CSS and 59 KiB of unused JavaScript are unnecessarily slowing page load by 750ms total.
CSS and JavaScript files are blocking initial render, delaying First Contentful Paint by 1.7 seconds.
Images are causing a 2.75 second delay to LCP and wasting 623 KiB with oversized dimensions and poor compression.
The LCP image uses lazy loading inappropriately, adding unnecessary delay to the largest visual element.