Website review, no card needed
vandgard.co.uk website review
Visit site (opens in a new tab)Reviewed 12 November 202629 issues · 68 checks
This review found 29 issues worth fixing on vandgard.co.uk, 9 of them high impact, across 68 checks. The most urgent: fails Core Web Vitals for real visitors. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 4.2 s |
| May 30, 2026 | 4.7 s |
| Jun 6, 2026 | 5.1 s |
| Jun 13, 2026 | 5.5 s |
| Jun 20, 2026 | 5.6 s |
| Jun 27, 2026 | 5.6 s |
| Jul 4, 2026 | 5.4 s |
| Jul 11, 2026 | 5.0 s |
| Jul 18, 2026 | 4.9 s |
| Jul 25, 2026 | 4.7 s |
| Aug 1, 2026 | 4.6 s |
| Aug 8, 2026 | 4.6 s |
| Aug 15, 2026 | 4.7 s |
| Aug 22, 2026 | 4.8 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 5.2 s |
| Sep 12, 2026 | 5.2 s |
| Sep 19, 2026 | 5.4 s |
| Sep 26, 2026 | 5.7 s |
| Oct 3, 2026 | 5.7 s |
| Oct 10, 2026 | 5.8 s |
| Oct 17, 2026 | 5.6 s |
| Oct 24, 2026 | 5.6 s |
| Oct 31, 2026 | 5.5 s |
| Nov 7, 2026 | 5.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 188 ms |
| May 30, 2026 | 194 ms |
| Jun 6, 2026 | 194 ms |
| Jun 13, 2026 | 190 ms |
| Jun 20, 2026 | 193 ms |
| Jun 27, 2026 | 189 ms |
| Jul 4, 2026 | 179 ms |
| Jul 11, 2026 | 180 ms |
| Jul 18, 2026 | 176 ms |
| Jul 25, 2026 | 173 ms |
| Aug 1, 2026 | 183 ms |
| Aug 8, 2026 | 182 ms |
| Aug 15, 2026 | 182 ms |
| Aug 22, 2026 | 185 ms |
| Aug 29, 2026 | 174 ms |
| Sep 5, 2026 | 175 ms |
| Sep 12, 2026 | 174 ms |
| Sep 19, 2026 | 175 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 180 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 190 ms |
| Oct 24, 2026 | 205 ms |
| Oct 31, 2026 | 214 ms |
| Nov 7, 2026 | 213 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
Speed
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Shopify and others), adding 1.3 MB and 626 ms of main-thread time.
Google Tag Manager adds 415 ms
415 msGoogle Tag Manager costs a phone 415 ms of main-thread work and 694 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.
Main-thread work: 2.2 s
A phone's processor spends 2.2 s on main-thread work while loading, 957 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Other Google APIs/SDKs adds 85 ms
85 msOther Google APIs/SDKs costs a phone 85 ms of main-thread work and 405 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.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 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.
Real-user LCP: 6.4 s
6.4 sReal visitors wait 6.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.0 s
5.0 sReal visitors see the first content after 5.0 s (75th percentile). Good is under 1.8 s.
Real-user INP: 239 ms
239 msReal visitors wait 239 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest content (LCP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 4.2 s to 5.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
14 images without width and height
14 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 188 ms to 213 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.9 MB in 181 requests
3.9 MBYour homepage downloads 3.9 MB in 181 requests on a phone: images 1.5 MB (28), scripts 1.2 MB (57) and other files 736 KiB (86). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.10 g of CO₂e: 131.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
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 21 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (251 characters)
Your meta description is 251 characters; Google truncates after about 160, so the end of your pitch is cut.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
91 internal links, 11 external
The homepage links to 91 pages on vandgard.co.uk and 11 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Vandgard® - Anti Climb Guards Ltd”.
Title: 56 characters
Your title is a healthy 56 characters: “Vandgard® Anti Climb – Vandgard® - Anti Climb Guards Ltd”.
Canonical URL set
The canonical URL is https://vandgard.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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://vandgard.co.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.
3 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 (808 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://vandgard.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://vandgard.co.uk/collections/rotaspike-security-topping, https://vandgard.co.uk/collections/wall-spikes, https://vandgard.co.uk/collections/prikka-strip and https://vandgard.co.uk/blogs/newsletters have no meta description, so Google writes the search snippet from whatever text it finds.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://vandgard.co.uk/collections/vandgard%C2%AE-anti-climb-guard, whose canonical is https://vandgard.co.uk/collections/vandgard%c2%ae-anti-climb-guard. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 41 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.
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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.
2 checks passed
Tap targets are thumb-sized
26 of 29 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.
Thin social proof
Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 592 words of copy
The homepage carries about 592 words of visible text.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact”, “Sign up and save” and “Subscribe”.
5 short forms
5 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
19 other companies contacted
Loading the homepage contacts 19 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 vandgard.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
orichi.info · weglot.com · chimpstatic.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- Rye
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on vandgard.co.uk, including 11 speed issues, 3 SEO issues and 2 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.