Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize info.sparrowhomeloans.com
444 KiB of unused JavaScript is blocking rendering and delaying LCP by 1.05 seconds.
Analyze Facebook Pixel and HotJar implementations - over 99% of code is unused. Remove or defer these tracking scripts until after page load. Use dynamic imports to load analytics code only when needed. Consider lighter alternatives or custom implementations.
A score of 69 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 69/100, primarily due to excessive JavaScript blocking the page from loading quickly. The biggest issue is legacy JavaScript from Facebook tracking scripts that wastes 34 KB and delays your Largest Contentful Paint by 4.3 seconds. Your First Contentful Paint takes 2.1 seconds, which is too slow for good user experience. To improve performance, consider removing or deferring non-essential Facebook tracking code, implementing modern JavaScript without polyfills for older browsers, and optimizing your CSS delivery which currently blocks rendering for 320ms. These changes could improve your score by 20+ points and make your site feel significantly faster to users.
Why It Matters:
CSS is blocking first paint by 300ms, directly delaying both FCP and LCP metrics.
How to Fix:
Inline critical CSS for above-the-fold content directly in the HTML head. Load non-critical CSS asynchronously using media='print' onload technique. Split CSS into critical and non-critical bundles during build process.
Why It Matters:
34 KiB of legacy polyfills are unnecessary for modern browsers, slowing down LCP by 50ms.
How to Fix:
Update build configuration to target modern browsers (ES2017+). Remove Babel transforms for features like Array methods and Object methods that are widely supported. Use differential serving to deliver modern code to modern browsers and polyfills only to older ones.
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.