Website review, no card needed
avfc.co.uk website review
Visit site (opens in a new tab)Reviewed 26 October 202656 issues · 84 checks
This review found 56 issues worth fixing on avfc.co.uk, 27 of them high impact, across 84 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
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 3.1 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 5.5 s |
| Jul 11, 2026 | 5.6 s |
| Jul 18, 2026 | 5.7 s |
| Jul 25, 2026 | 5.7 s |
| Aug 1, 2026 | 5.7 s |
| Aug 8, 2026 | 5.8 s |
| Aug 15, 2026 | 5.9 s |
| Aug 22, 2026 | 6.1 s |
| Aug 29, 2026 | 6.2 s |
| Sep 5, 2026 | 6.2 s |
| Sep 12, 2026 | 6.3 s |
| Sep 19, 2026 | 6.3 s |
| Sep 26, 2026 | 6.4 s |
| Oct 3, 2026 | 6.4 s |
| Oct 10, 2026 | 6.4 s |
| Oct 17, 2026 | 6.4 s |
| Oct 24, 2026 | 6.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 194 ms |
| May 16, 2026 | 194 ms |
| May 23, 2026 | 199 ms |
| May 30, 2026 | 200 ms |
| Jun 6, 2026 | 202 ms |
| Jun 13, 2026 | 203 ms |
| Jun 20, 2026 | 203 ms |
| Jun 27, 2026 | 207 ms |
| Jul 4, 2026 | 213 ms |
| Jul 11, 2026 | 218 ms |
| Jul 18, 2026 | 220 ms |
| Jul 25, 2026 | 219 ms |
| Aug 1, 2026 | 220 ms |
| Aug 8, 2026 | 224 ms |
| Aug 15, 2026 | 228 ms |
| Aug 22, 2026 | 234 ms |
| Aug 29, 2026 | 236 ms |
| Sep 5, 2026 | 237 ms |
| Sep 12, 2026 | 237 ms |
| Sep 19, 2026 | 239 ms |
| Sep 26, 2026 | 245 ms |
| Oct 3, 2026 | 253 ms |
| Oct 10, 2026 | 256 ms |
| Oct 17, 2026 | 262 ms |
| Oct 24, 2026 | 261 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
Reduce unused JavaScript
12.9 s · 2.3 MBAbout 2.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.9 s faster on a phone.
Use efficient cache lifetimes
10.1 s · 5.0 MB249 files are served with short cache lifetimes, so returning visitors download them again (5.0 MB).
Render-blocking requests
2.3 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Google Tag Manager adds 1.5 s
1.5 sGoogle Tag Manager costs a phone 1.5 s of main-thread work and 1.0 MB 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: 27
27/100Your mobile performance score is 27 (desktop: 31). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.8 s
A phone's processor spends 9.8 s on main-thread work while loading, 6.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
27.6 MB55 images could be 27.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and halfspace.co.uk and others), adding 3.1 MB and 3.3 s of main-thread time.
Reduce unused CSS
300 ms · 234 KiBAbout 234 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.
Google CDN adds 437 ms
437 msGoogle CDN costs a phone 437 ms of main-thread work and 734 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 453 ms. During a long task the page ignores taps.
halfspace.co.uk adds 368 ms
368 mshalfspace.co.uk costs a phone 368 ms of main-thread work and 19 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
300 ms · 14 KiB14 KiB could be saved by minifying JavaScript.
Facebook adds 255 ms
255 msFacebook costs a phone 255 ms of main-thread work and 282 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.
ContentSquare adds 253 ms
253 msContentSquare costs a phone 253 ms of main-thread work and 180 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.
Legacy JavaScript
200 ms · 66 KiBPolyfills for old browsers add 66 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 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.
1 checks passed
Server response: 36 ms
36 msYour server sent the HTML in 36 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.7 s
6.7 sReal visitors wait 6.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.7 s
3.7 sReal visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 8.1 s
8.1 sThe first text or image appears after 8.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 42.2 s
42.2 sYour largest element takes 42.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 29.2 s
29.2 sVisually, the page fills in at 29.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 61.7 s
61.7 sThe page becomes fully interactive after 61.7 s. Good is under 3.8 s.
Total Blocking Time: 2.2 s
2.2 sScripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.
Real-user INP: 277 ms
277 msReal visitors wait 277 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 35% slower for real visitors
+35%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 194 ms to 261 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 146% slower for real visitors
+146%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.6 s to 6.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user CLS: 0.09
0.09For real visitors the layout shifts by 0.09 (75th percentile). Good is under 0.1.
Real-user TTFB: 548 ms
548 msReal visitors wait 548 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.047
0.047The layout barely moves while loading (CLS 0.047, good is under 0.1).
Images and page weight
Page weight: 39.4 MB in 632 requests
39.4 MBYour homepage downloads 39.4 MB in 632 requests on a phone: images 33.0 MB (114), scripts 4.4 MB (249) and other files 1.7 MB (257). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
48 KiB2 images are downloaded at several times the size a phone draws them, for example 95f571e0-9729-11f1-abe3-bbb7535ab5e7.png at 350 px wide, shown at 60 px. Resized copies would save about 48 KiB.
2 images in older formats
2 images (110 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 (50 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 11.2 g of CO₂ per visit
11.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 11.17 g of CO₂e: 1340.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must be contained by particular parents (24 elements)
Certain ARIA roles must be contained by particular parents: 24 elements on the page fail this check, rated critical by axe-core.
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
ARIA tab nodes must have an accessible name (19 elements)
ARIA tab nodes must have an accessible name: 19 elements on the page fail this check, rated serious by axe-core.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Elements must only use permitted ARIA attributes (4 elements)
Elements must only use permitted ARIA attributes: 4 elements on the page fail this check, rated serious by axe-core.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
<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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails 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.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
ARIA role should be appropriate for the element (3 elements)
ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
2 checks passed
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.avfc.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.avfc.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.
1 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.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “[Veritonic] IP lookup failed with status 0”.
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
18 of 18 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 91 words
The homepage has only about 91 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
17 cookies set on arrival
17Opening the homepage sets 17 cookies (measured from a US location before any click).
54 other companies contacted
Loading the homepage contacts 54 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 avfc.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
- Nuxt
- Analytics
- Google Tag Manager
- Hosting
- AWS
Company
- Founded
- 1874
- Headquarters
- Aston
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 56 issues on avfc.co.uk, including 27 speed issues, 9 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.