Website review, no card needed

sanctuary-housing.co.uk logo

sanctuary-housing.co.uk website review

Visit site (opens in a new tab)Reviewed 5 November 202632 issues · 84 checks

This review found 32 issues worth fixing on sanctuary-housing.co.uk, 13 of them high impact, across 84 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.3 s2.2 sMay 16Oct 313.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.4 s
May 23, 20262.3 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.6 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.7 s
Oct 17, 20262.8 s
Oct 24, 20263.0 s
Oct 31, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
143 ms108 msMay 16Oct 31130 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026112 ms
May 23, 2026113 ms
May 30, 2026116 ms
Jun 6, 2026117 ms
Jun 13, 2026120 ms
Jun 20, 2026121 ms
Jun 27, 2026124 ms
Jul 4, 2026128 ms
Jul 11, 2026128 ms
Jul 18, 2026128 ms
Jul 25, 2026129 ms
Aug 1, 2026130 ms
Aug 8, 2026132 ms
Aug 15, 2026136 ms
Aug 22, 2026136 ms
Aug 29, 2026137 ms
Sep 5, 2026138 ms
Sep 12, 2026139 ms
Sep 19, 2026139 ms
Sep 26, 2026139 ms
Oct 3, 2026139 ms
Oct 10, 2026138 ms
Oct 17, 2026137 ms
Oct 24, 2026133 ms
Oct 31, 2026130 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

Full-page screenshot of sanctuary-housing.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sanctuary-housing.co.uk at 0.9 s0.9 s
  2. sanctuary-housing.co.uk at 1.8 s1.8 s
  3. sanctuary-housing.co.uk at 2.7 s2.7 s
  4. sanctuary-housing.co.uk at 3.6 s3.6 s
  5. sanctuary-housing.co.uk at 4.5 s4.5 s
  6. sanctuary-housing.co.uk at 5.4 s5.4 s
  7. sanctuary-housing.co.uk at 6.3 s6.3 s
  8. sanctuary-housing.co.uk at 7.2 s7.2 s

Speed

13 to fix33
  • Use efficient cache lifetimes

    2.4 s · 723 KiB

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

  • Render-blocking requests

    2.5 s

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

  • Reduce unused JavaScript

    1.9 s · 360 KiB

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

  • Google Tag Manager adds 1.0 s

    1.0 s

    Google Tag Manager costs a phone 1.0 s of main-thread work and 378 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • VWO adds 1.0 s

    1.0 s

    VWO costs a phone 1.0 s of main-thread work and 172 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 33

    33/100

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

  • Main-thread work: 7.1 s

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (VWO, Google Tag Manager and cookiebot.eu and others), adding 693 KiB and 2.4 s of main-thread time.

  • Improve image delivery

    450 ms · 444 KiB

    13 images could be 444 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Font display

    800 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 800 ms).

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    350 ms · 45 KiB

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

  • 1,993 HTML elements

    The page has 1,993 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Minify JavaScript

    210 ms · 169 KiB

    169 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    210 ms · 38 KiB

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

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

  • Forced reflow

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 12.8 s

    12.8 s

    Your largest element takes 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We are one of the UK’s largest providers of housing, care a…”. Most of its time is element render delay (6.6 s).

  • Total Blocking Time: 2.7 s

    2.7 s

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

  • Time to Interactive: 12.9 s

    12.9 s

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

  • Speed Index: 7.7 s

    7.7 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • Largest content (LCP) got 31% slower for real visitors

    +31%

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

  • 5 images without width and height

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

  • Tap response (INP) got 17% slower for real visitors

    +17%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 126 ms

    126 ms

    Real visitors wait 126 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 432 ms

    432 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

3 to fix74
  • Page weight: 2.1 MB in 186 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 186 requests on a phone: scripts 1.3 MB (90), images 679 KiB (29) and fonts 89 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    england-homepage3.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    36 KiB

    1 image is downloaded at several times the size a phone draws it, for example shawtrust_accessible.jpg at 962 px wide, shown at 180 px. Resized copies would save about 36 KiB.

  • 3 images in older formats

    3 images (255 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.

  • 5 images below the first screen load straight away

    5 images further down the page (138 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.6 g of CO₂ per visit

    0.60 g

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

Accessibility

1 to fixGoogle 10099
  • All page content should be contained by landmarks (3 elements)

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

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10096
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 181 internal links, 21 external

    The homepage links to 181 pages on sanctuary-housing.co.uk and 21 external pages.

7 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Welcome to Sanctuary. With over 105,000 affordable homes across England and Scotland, we are one of the UK's leading so…”.

  • One H1 headline

    Your main headline reads: “Sanctuary Home Page”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Sanctuary | Leading Housing and Care Provider”.

  • Canonical URL set

    The canonical URL is https://www.sanctuary.co.uk/.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.sanctuary.co.uk/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://www.sanctuary.co.uk/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 (1,262 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix98
  • 2 pages share a meta description

    https://www.sanctuary.co.uk/about-sanctuary and https://www.sanctuary.co.uk/join-our-team use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 156 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

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to script at 'https://analytics.silktide.com/ce8a6dd43c98b69e25d0c07bf10c03c7.js' from origin 'https://www.sanct…”.

2 checks passed
  • Tap targets are thumb-sized

    17 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • 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.

  • 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 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 777 words of copy

    The homepage carries about 777 words of visible text.

5 checks passed
  • 15 calls to action

    The homepage has 15 calls to action, for example “Join our team”, “Update your contact details” and “Request an account statement”.

  • 1 short form

    A short form (6 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 7 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Opening hours shown

    Your opening hours are on the homepage.

Privacy and tracking

  • 1 tracker load before any consent

    1

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

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies (measured from a US location before any click).

  • 8 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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 sanctuary-housing.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Drupal
Framework
jQuery
Analytics
Google Tag Manager
Hosting
AWS

Hiring

Hiring
1 open role
Job board
careers page

Company

Founded
1969
Headquarters
Worcester

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on sanctuary-housing.co.uk, including 20 speed issues, 1 SEO issue and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25