Largest Contentful Paint
Good: < 2.5s
Measures how long it takes for the main content to appear on screen
How to optimize objectev.com
86% of your CSS is unused, wasting 12 KiB and delaying both FCP and LCP by 150ms.
Use PurgeCSS to remove unused Tailwind classes from your build process. Configure your build tool to only include CSS for components actually used on each page. Split critical above-the-fold CSS and inline it in the HTML head.
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 excessive unused JavaScript (361 KiB waste), primarily from Google services like reCAPTCHA and analytics, which is severely slowing down page loading - your Largest Contentful Paint takes 7.2 seconds when it should be under 2.5 seconds. Additionally, 86% of your CSS is unused, and images are taking too long to render due to processing delays. Removing or deferring unused scripts, cleaning up CSS, and optimizing image loading could potentially improve your score by 30+ points and dramatically speed up the site.
Why It Matters:
Unused JavaScript wastes 361 KiB and delays LCP by 1.5 seconds, severely impacting Core Web Vitals.
How to Fix:
Defer ReCAPTCHA loading until user interaction with forms. Move Google Analytics to load after page interactive using gtag('config') with custom_map. Remove or replace heavy third-party scripts with lighter alternatives.
Why It Matters:
The hero image has 1.7 seconds of render delay, making LCP extremely poor at 7.2 seconds.
How to Fix:
Preload the hero image using <link rel='preload' as='image' href='/images/our-mission.jpg'>. Ensure the image is above-the-fold without lazy loading. Optimize the image file size and serve in WebP format with fallback.
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.