Website review, no card needed
nawt.org.uk website review
Visit site (opens in a new tab)Reviewed 24 October 202626 issues · 83 checks
This review found 26 issues worth fixing on nawt.org.uk, 9 of them high impact, across 83 checks. The most urgent: improve image delivery. 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
87BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 576 ms |
| May 9, 2026 | 564 ms |
| May 16, 2026 | 569 ms |
| May 23, 2026 | 567 ms |
| May 30, 2026 | 570 ms |
| Jun 6, 2026 | 570 ms |
| Jun 13, 2026 | 567 ms |
| Jun 20, 2026 | 569 ms |
| Jun 27, 2026 | 573 ms |
| Jul 4, 2026 | 576 ms |
| Jul 11, 2026 | 585 ms |
| Jul 18, 2026 | 584 ms |
| Jul 25, 2026 | 611 ms |
| Aug 1, 2026 | 650 ms |
| Aug 8, 2026 | 686 ms |
| Aug 15, 2026 | 720 ms |
| Aug 22, 2026 | 722 ms |
| Aug 29, 2026 | 721 ms |
| Sep 5, 2026 | 713 ms |
| Sep 12, 2026 | 710 ms |
| Sep 19, 2026 | 715 ms |
| Sep 26, 2026 | 718 ms |
| Oct 3, 2026 | 725 ms |
| Oct 10, 2026 | 730 ms |
| Oct 17, 2026 | 724 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 74 ms |
| May 9, 2026 | 74 ms |
| May 16, 2026 | 73 ms |
| May 23, 2026 | 73 ms |
| May 30, 2026 | 74 ms |
| Jun 6, 2026 | 75 ms |
| Jun 13, 2026 | 74 ms |
| Jun 20, 2026 | 74 ms |
| Jun 27, 2026 | 74 ms |
| Jul 4, 2026 | 75 ms |
| Jul 11, 2026 | 76 ms |
| Jul 18, 2026 | 76 ms |
| Jul 25, 2026 | 76 ms |
| Aug 1, 2026 | 75 ms |
| Aug 8, 2026 | 76 ms |
| Aug 15, 2026 | 75 ms |
| Aug 22, 2026 | 75 ms |
| Aug 29, 2026 | 75 ms |
| Sep 5, 2026 | 75 ms |
| Sep 12, 2026 | 75 ms |
| Sep 19, 2026 | 75 ms |
| Sep 26, 2026 | 75 ms |
| Oct 3, 2026 | 75 ms |
| Oct 10, 2026 | 75 ms |
| Oct 17, 2026 | 75 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.5 s
1.0 s
1.5 s
2.1 s
2.6 s
3.1 s
3.6 s
4.1 s
Speed
Improve image delivery
1.4 s · 302 KiB7 images could be 302 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Reduce unused JavaScript
1.2 s · 201 KiBAbout 201 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Render-blocking requests
1.4 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 61
61/100Your mobile performance score is 61 (desktop: 81). Pages that score under 90 lose visitors before the first paint.
Minify JavaScript
500 ms · 112 KiB112 KiB could be saved by minifying JavaScript.
Reduce unused CSS
500 ms · 54 KiBAbout 54 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 500 ms faster on a phone.
Use efficient cache lifetimes
300 ms · 130 KiB10 files are served with short cache lifetimes, so returning visitors download them again (130 KiB).
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, cookiehub.eu and Google Analytics and others), adding 507 KiB and 145 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 109 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 0.6 s
A phone's processor spends 0.6 s on main-thread work while loading, 167 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “National Animal Welfare Trust is a rescue and rehoming char…”. Most of its time is element render delay (3.0 s).
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
Time to Interactive: 8.3 s
8.3 sThe page becomes fully interactive after 8.3 s. Good is under 3.8 s.
Largest content (LCP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.6 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 74 ms to 75 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 86 ms
86 msReal visitors wait 86 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 542 ms
542 msReal visitors wait 542 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 67 ms
67 msScripts block the page for only 67 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
2 images far larger than shown
157 KiB2 images are downloaded at several times the size a phone draws them, for example right.png at 450 px wide, shown at 76 px. Resized copies would save about 157 KiB.
2 images in older formats
2 images (248 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.
1 image below the first screen load straight away
1 image further down the page (26 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.51 g of CO₂e: 61.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.8 MB in 45 requests
1.8 MBYour homepage downloads 1.8 MB in 45 requests on a phone: images 733 KiB (27), fonts 599 KiB (5) and scripts 420 KiB (4). That is a lean page.
Accessibility
32 text elements with low contrast
32 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
44 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: 44 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Expected ',' or '}' after property value in JSON at position)”.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
67 internal links, 22 external
The homepage links to 67 pages on nawt.org.uk and 22 external pages.
7 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “The National Animal Welfare Trust is one of the UK’s top animal welfare charities, operating five rehoming centres acro…”.
One H1 headline
Your main headline reads: “Are you looking torehome a...cat or dog”.
Title: 63 characters
Your title is a healthy 63 characters: “National Animal Welfare Charity | National Animal Welfare Trust”.
Canonical URL set
The canonical URL is https://www.nawt.org.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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.nawt.org.uk/sitemap.xml.
AI search readiness
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.nawt.org.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 (489 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages without a meta description
https://www.nawt.org.uk/donate, https://www.nawt.org.uk/useful-information, https://www.nawt.org.uk/get-involved, https://www.nawt.org.uk/get-involved/volunteer, https://www.nawt.org.uk/get-involved/working-with-us and https://www.nawt.org.uk/get-involved/fundraise-for-us and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.nawt.org.uk/useful-information has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.nawt.org.uk/donate has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 45 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
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
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
22 of 23 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 458 words of copy
The homepage carries about 458 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop” and “Learn more”.
5 calls to action
The homepage has 5 calls to action, for example “Shop”, “Join our Lottery” and “Sign Up To Gift Aid”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 3 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
10 other companies contacted
Loading the homepage contacts 10 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 nawt.org.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
Company
- Employees
- 116
- Founded
- 1971
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on nawt.org.uk, including 13 speed issues, 2 SEO issues and 3 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.