Website review, no card needed
bva.co.uk website review
Visit site (opens in a new tab)Reviewed 24 October 202640 issues · 87 checks
This review found 40 issues worth fixing on bva.co.uk, 14 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.8 s |
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 178 ms |
| May 9, 2026 | 181 ms |
| May 16, 2026 | 181 ms |
| May 23, 2026 | 184 ms |
| May 30, 2026 | 196 ms |
| Jun 6, 2026 | 196 ms |
| Jun 13, 2026 | 195 ms |
| Jun 20, 2026 | 191 ms |
| Jun 27, 2026 | 189 ms |
| Jul 4, 2026 | 191 ms |
| Jul 11, 2026 | 200 ms |
| Jul 18, 2026 | 204 ms |
| Jul 25, 2026 | 198 ms |
| Aug 1, 2026 | 197 ms |
| Aug 8, 2026 | 190 ms |
| Aug 15, 2026 | 183 ms |
| Aug 22, 2026 | 183 ms |
| Aug 29, 2026 | 179 ms |
| Sep 5, 2026 | 178 ms |
| Sep 12, 2026 | 180 ms |
| Sep 19, 2026 | 177 ms |
| Sep 26, 2026 | 185 ms |
| Oct 3, 2026 | 182 ms |
| Oct 10, 2026 | 180 ms |
| Oct 17, 2026 | 183 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
Use efficient cache lifetimes
2.5 s · 3.4 MB46 files are served with short cache lifetimes, so returning visitors download them again (3.4 MB).
Reduce unused JavaScript
1.8 s · 565 KiBAbout 565 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.8 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
Improve image delivery
600 ms · 3.8 MB7 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Hotjar and Cookie-Script.com and others), adding 1.1 MB and 909 ms of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54 (desktop: 54). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 725 ms
725 msGoogle Tag Manager costs a phone 725 ms of main-thread work and 783 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.
Minify JavaScript
385 KiB385 KiB could be saved by minifying JavaScript.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 243 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 65 KiBAbout 65 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
100 ms · 15 KiBPolyfills for old browsers add 15 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
11 KiB11 KiB could be saved by minifying CSS.
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, 1.0 s of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 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: 10.0 s
10.0 sYour largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Join us today "BVA membership offers such a wide range of b…”.
Time to Interactive: 12.8 s
12.8 sThe page becomes fully interactive after 12.8 s. Good is under 3.8 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
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.
Total Blocking Time: 500 ms
500 msScripts block taps and scrolling for 500 ms in total while the page loads. Good is under 200 ms.
Speed Index: 4.3 s
4.3 sVisually, the page fills in at 4.3 s (Speed Index). Good is under 3.4 s.
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 178 ms to 183 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 159 ms
159 msReal visitors wait 159 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.007
0.007The layout barely moves while loading (CLS 0.007, good is under 0.1).
Images and page weight
Page weight: 6.0 MB in 65 requests
6.0 MBYour homepage downloads 6.0 MB in 65 requests on a phone: images 4.3 MB (23), scripts 1.5 MB (24) and fonts 184 KiB (3). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
doctor-uses-digital-tablet-on-farm-2026-09-21-18-26-11-utc.j weighs 3.6 MB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
3.5 MB1 image is downloaded at several times the size a phone draws it, for example doctor-uses-digital-tablet-on-farm-2026-09-21-18-26-11-utc.j at 6,000 px wide, shown at 360 px. Resized copies would save about 3.5 MB.
3 images in older formats
3 images (3.8 MB) 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 (82 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.7 g of CO₂ per visit
1.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.71 g of CO₂e: 205.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 failed. 2 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.
2 H1 headlines
There are 2 <h1> headlines (“Join us today” and “Join us today”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
187 internal links, 17 external
The homepage links to 187 pages on bva.co.uk and 17 external pages.
5 checks passed
Meta description: 94 characters
Your meta description is 94 characters: “BVA represents, supports and champions over 19,000 members of all ages, stages and disciplines”.
Title: 36 characters
Your title is a healthy 36 characters: “BVA - British Veterinary Association”.
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.bva.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.
No llms.txt
There is no https://www.bva.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 (837 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://www.bva.co.uk/about-us/our-events and https://www.bva.co.uk/shop are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
8 pages without a meta description
https://www.bva.co.uk/about-us/our-events, https://www.bva.co.uk/about-us/bva-strategic-plan, https://www.bva.co.uk/venue-hire/mary-brancker, https://www.bva.co.uk/venue-hire/george-fleming, https://www.bva.co.uk/venue-hire/william-hunting-suite and https://www.bva.co.uk/venue-hire/aleen-cust and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.bva.co.uk/about-us/bva-strategic-plan and https://www.bva.co.uk/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 85 found) and read each the way a search engine does.
4 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.
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
21 of 25 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 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 364 words of copy
The homepage carries about 364 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: “JOIN US” and “Learn more”.
10 calls to action
The homepage has 10 calls to action, for example “Shop”, “Contact Us” and “JOIN US”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Hotjar and Cloudflare Web 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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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 bva.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
- Framework
- Angular
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
Company
- Founded
- 1919
- Headquarters
- London
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on bva.co.uk, including 16 speed issues, 4 SEO issues 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.