buckman.com website review

Your mobile performance score is 73 (desktop: 99). Pages that score under 90 lose visitors before the first paint.

12 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.

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

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

8 third-party services load with your homepage (Google CDN, cdn-cookieyes.com and glue1lazy.com and others), adding 126 KiB and 93 ms of main-thread time.

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

Polyfills for old browsers add 16 KiB JavaScript that modern phones do not need.

Desktop scores 99 but mobile only 73. A gap that wide usually means heavy scripts and images that hit phones hardest.

8 KiB could be saved by minifying JavaScript.

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

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.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 104 ms to 113 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 13.0 MB in 75 requests on a phone: media 12.3 MB (1), scripts 400 KiB (37) and images 249 KiB (16). Under 2 MB keeps phones on slow connections fast.

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

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

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

The homepage links to 96 pages on buckman.com and 18 external pages.

There is no /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.

/innovation has no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 15 pages linked from your homepage (of 47 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://www.buckman.com/.

9 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

buckman.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

buckman.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

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 368 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

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

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