sargentandgreenleaf.com website review

About 988 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.

137 files are served with short cache lifetimes, so returning visitors download them again (455 KiB).

18 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

Your mobile performance score is 22 (desktop: 34). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

About 129 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

6 third-party services load with your homepage (Google Tag Manager, Optanon and Salesforce.com and others), adding 1.3 MB and 731 ms of main-thread time.

Google Tag Manager costs a phone 504 ms of main-thread work and 472 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

A phone's processor spends 3.6 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Vimeo costs a phone 38 ms of main-thread work and 510 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

20 long tasks block the main thread while loading, the longest for 186 ms. During a long task the page ignores taps.

Polyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

2 images could be 62 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying CSS.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 1.20 (75th percentile). Good is under 0.1.

Your largest element takes 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The layout shifts by 1.164 while loading, so content jumps under the reader's thumb. Good is under 0.1.

The first text or image appears after 6.9 s on a phone. Good is under 1.8 s.

The page becomes fully interactive after 16.2 s. Good is under 3.8 s.

Visually, the page fills in at 8.6 s (Speed Index). Good is under 3.4 s.

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 431 ms in total while the page loads. Good is under 200 ms.

2 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 3.0 MB in 158 requests on a phone: scripts 2.2 MB (114), fonts 302 KiB (6) and images 251 KiB (11). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example cq5dam.web.1280.1280.jpeg at 1,248 px wide, shown at 390 px. Resized copies would save about 15 KiB.

3 images (224 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 0.85 g of CO₂e: 101.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.

Heading levels should only increase by one: 3 elements on the page fail this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 80 characters, so Google will cut it off around 60: “Sargent & Greenleaf | Leading high-security lock solutions | SargentandGreenleaf”.

Structured data found (BreadcrumbList and WebSite) but with 2 problems, for example “ld+json block 1 is not valid JSON (Expected double-quoted property name in JSON at position 351)”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

A phone browser shows 385 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.sargentandgreenleaf.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 385 words of visible text.

Opening the homepage sets 5 cookies, 2 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.