Website review, no card needed
clarionhg.com website review
Visit site (opens in a new tab)Reviewed 20 November 202634 issues · 81 checks
This review found 34 issues worth fixing on clarionhg.com, 12 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.8 s |
| Nov 14, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 145 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 144 ms |
| Jun 20, 2026 | 148 ms |
| Jun 27, 2026 | 148 ms |
| Jul 4, 2026 | 149 ms |
| Jul 11, 2026 | 151 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 155 ms |
| Aug 1, 2026 | 176 ms |
| Aug 8, 2026 | 188 ms |
| Aug 15, 2026 | 199 ms |
| Aug 22, 2026 | 211 ms |
| Aug 29, 2026 | 210 ms |
| Sep 5, 2026 | 213 ms |
| Sep 12, 2026 | 212 ms |
| Sep 19, 2026 | 211 ms |
| Sep 26, 2026 | 215 ms |
| Oct 3, 2026 | 218 ms |
| Oct 10, 2026 | 213 ms |
| Oct 17, 2026 | 217 ms |
| Oct 24, 2026 | 217 ms |
| Oct 31, 2026 | 218 ms |
| Nov 7, 2026 | 226 ms |
| Nov 14, 2026 | 224 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
2.2 s · 977 KiBAbout 977 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.2 s faster on a phone.
Render-blocking requests
1.9 s35 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Use efficient cache lifetimes
800 ms · 234 KiB7 files are served with short cache lifetimes, so returning visitors download them again (234 KiB).
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Facebook and Google Maps and others), adding 1.2 MB and 694 ms of main-thread time.
Google Tag Manager adds 338 ms
338 msGoogle Tag Manager costs a phone 338 ms of main-thread work and 501 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.
Reduce unused CSS
300 ms · 59 KiBAbout 59 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 139 ms. During a long task the page ignores taps.
Improve image delivery
75 KiB2 images could be 75 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
63 KiBPolyfills for old browsers add 63 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
2 checks passed
Main-thread work: 1.7 s
A phone's processor spends 1.7 s on main-thread work while loading, 981 ms of it running JavaScript. That is comfortably low.
Server response: 96 ms
96 msYour server sent the HTML in 96 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 9.2 s
9.2 sYour largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Supporting people into work and training”.
Time to Interactive: 13.9 s
13.9 sThe page becomes fully interactive after 13.9 s. Good is under 3.8 s.
First Contentful Paint: 4.6 s
4.6 sThe first text or image appears after 4.6 s on a phone. Good is under 1.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 s.
Real-user INP: 225 ms
225 msReal visitors wait 225 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 55% slower for real visitors
+55%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 145 ms to 224 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 289 ms
289 msScripts block taps and scrolling for 289 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
5 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 589 ms
589 msReal visitors wait 589 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.046
0.046The layout barely moves while loading (CLS 0.046, good is under 0.1).
Images and page weight
Page weight: 15.8 MB in 90 requests
15.8 MBYour homepage downloads 15.8 MB in 90 requests on a phone: media 13.6 MB (2), scripts 1.8 MB (30) and images 206 KiB (11). Under 2 MB keeps phones on slow connections fast.
About 4.5 g of CO₂ per visit
4.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.47 g of CO₂e: 536.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Unlabelled dropdowns
1 dropdown has no label.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 23 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (21 characters)
Your title is only 21 characters: “Clarion Housing Group”. Between 30 and 65 characters leaves room to say what you do and for whom.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (166 characters)
Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “WebSite: missing name”.
26 internal links, 7 external
The homepage links to 26 pages on clarionhg.com and 7 external pages.
4 checks passed
One H1 headline
Your main headline reads: “Supporting people into work and training”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.clarionhg.com/sitemap.xml.
AI search readiness
Organization data is thin (0 of 6 facts)
Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.clarionhg.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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (696 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “The source list for Content Security Policy directive 'script-src-elem' contains a source with an invalid path: 'https://www.clarionhg.com/c/hot…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
11 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 787 words of copy
The homepage carries about 787 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact us”.
Analytics in place
Analytics detected: Google Tag Manager and Hotjar.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Hotjar and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
No consent tool detected
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.
11 other companies contacted
Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at clarionhg.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Azure
Company
- Headquarters
- London
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on clarionhg.com, including 17 speed issues, 4 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.