headversity.com website review

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

6 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 3.2 MB and 781 ms of main-thread time.

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

Google Tag Manager costs a phone 522 ms of main-thread work and 516 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.

WordPress costs a phone 49 ms of main-thread work and 2.5 MB 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.

About 252 KiB of JavaScript is downloaded but never used on this page.

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

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

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

11 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.

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

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

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

Your largest element takes 2.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Headversity helps organizations build safer, stronger workp…”. Most of its time is element render delay (1.4 s).

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.5 MB in 74 requests on a phone: images 2.5 MB (21), scripts 800 KiB (20) and fonts 167 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

[aria-*] attributes are not valid or misspelled (1 element).

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

The homepage links to 25 pages on headversity.com and 12 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.

Your homepage links to /sport, which answers with an error. Visitors hit a dead end and search engines drop it.

/ebooks-guides/hr-leaders-guide-to-mental-health-strategy, /terms-and-conditions, /privacy-policy and /cookies-notice have no meta description, so Google writes the search snippet from whatever text it finds.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

1 link from your homepage to your own site is broken, for example https://headversity.com/sport/ (404).

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

headversity.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.

headversity.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.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

The homepage has only about 33 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

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.

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.