Website review, no card needed

afcwimbledonfoundation.org.uk logo

afcwimbledonfoundation.org.uk website review

Visit site (opens in a new tab)Reviewed 17 November 202629 issues · 80 checks

This review found 29 issues worth fixing on afcwimbledonfoundation.org.uk, 8 of them high impact, across 80 checks. The most urgent: improve image delivery. 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
1.5 s1.1 sMay 30Nov 141.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.4 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.4 s
Jul 25, 20261.4 s
Aug 1, 20261.3 s
Aug 8, 20261.2 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.2 s
Sep 12, 20261.1 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Nov 7, 20261.5 s
Nov 14, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
120 ms67 msMay 30Nov 14114 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202685 ms
Jun 6, 202687 ms
Jun 13, 202690 ms
Jun 20, 202692 ms
Jun 27, 202688 ms
Jul 4, 202683 ms
Jul 11, 202680 ms
Jul 18, 202679 ms
Jul 25, 202676 ms
Aug 1, 202678 ms
Aug 8, 202679 ms
Aug 15, 202679 ms
Aug 22, 202688 ms
Aug 29, 202686 ms
Sep 5, 202681 ms
Sep 12, 202681 ms
Sep 19, 202678 ms
Sep 26, 202673 ms
Oct 3, 202680 ms
Oct 10, 202677 ms
Oct 17, 202673 ms
Oct 24, 202681 ms
Oct 31, 202681 ms
Nov 14, 2026114 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 afcwimbledonfoundation.org.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. afcwimbledonfoundation.org.uk at 0.4 s0.4 s
  2. afcwimbledonfoundation.org.uk at 0.8 s0.8 s
  3. afcwimbledonfoundation.org.uk at 1.1 s1.1 s
  4. afcwimbledonfoundation.org.uk at 1.5 s1.5 s
  5. afcwimbledonfoundation.org.uk at 1.9 s1.9 s
  6. afcwimbledonfoundation.org.uk at 2.3 s2.3 s
  7. afcwimbledonfoundation.org.uk at 2.6 s2.6 s
  8. afcwimbledonfoundation.org.uk at 3.0 s3.0 s

Speed

9 to fix66
  • Improve image delivery

    5.5 s · 1.1 MB

    4 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.5 s faster on a phone.

  • Render-blocking requests

    1.9 s

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

  • Reduce unused JavaScript

    450 ms · 1,006 KiB

    About 1,006 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Mobile performance score: 66

    66/100

    Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Squarespace, Google Tag Manager and Hotjar and others), adding 3.5 MB and 636 ms of main-thread time.

  • Reduce unused CSS

    600 ms · 189 KiB

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

  • Squarespace adds 387 ms

    387 ms

    Squarespace costs a phone 387 ms of main-thread work and 1.3 MB 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.

  • squarespace-cdn.com adds 0 ms

    0 ms

    squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.5 MB 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.

  • sqspcdn.com adds 46 ms

    46 ms

    sqspcdn.com costs a phone 46 ms of main-thread work and 339 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

    150 ms · 124 KiB

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

  • 5 long tasks on the main thread

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

  • Use efficient cache lifetimes

    23 KiB

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

  • 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: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 640 ms of it running JavaScript. That is comfortably low.

  • Server response: 66 ms

    66 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 10.9 s

    10.9 s

    Your largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 17.4 s

    17.4 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Speed Index: 4.4 s

    4.4 s

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

  • 1 image without width and height

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

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

    +13%

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

  • Largest content (LCP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.4 s 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: 1.4 s

    1.4 s

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

  • Real-user INP: 109 ms

    109 ms

    Real visitors wait 109 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.2 s

    1.2 s

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

  • Total Blocking Time: 193 ms

    193 ms

    Scripts block the page for only 193 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix70
  • 1 image over 500 KB

    Our+Programmes+Landscape.png weighs 564 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 3.6 MB in 73 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 73 requests on a phone: scripts 1.8 MB (45), images 1.4 MB (6) and stylesheets 174 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    1.03 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.03 g of CO₂e: 123.3 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

Google 98100
  • Headings skip levels

    Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 46 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: 46 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9279
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (24 characters)

    Your title is only 24 characters: “AFC Wimbledon Foundation”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 2 problems

    Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5e4169716545fb14fe2…”.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 59 internal links, 11 external

    The homepage links to 59 pages on afcwimbledonfoundation.org.uk and 11 external pages.

4 checks passed
  • One H1 headline

    Your main headline reads: “keep in touch”.

  • Canonical URL set

    The canonical URL is https://afcwimbledonfoundation.com/.

  • 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://afcwimbledonfoundation.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo and description. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://afcwimbledonfoundation.com/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 (356 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix81
  • 3 linked pages hidden from search

    https://afcwimbledonfoundation.com/about, https://afcwimbledonfoundation.com/impact and https://afcwimbledonfoundation.com/edi 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://afcwimbledonfoundation.com/news, https://afcwimbledonfoundation.com/meet-the-trustees, https://afcwimbledonfoundation.com/5-a-side-pitch, https://afcwimbledonfoundation.com/christmas-quiz-1, https://afcwimbledonfoundation.com/christmas-quiz and https://afcwimbledonfoundation.com/our-programmes and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages share a meta description

    https://afcwimbledonfoundation.com/about, https://afcwimbledonfoundation.com/impact, https://afcwimbledonfoundation.com/edi and https://afcwimbledonfoundation.com/safeguarding use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://afcwimbledonfoundation.com/safeguarding, https://afcwimbledonfoundation.com/christmas-quiz-1, https://afcwimbledonfoundation.com/christmas-quiz and https://afcwimbledonfoundation.com/our-programmes have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://afcwimbledonfoundation.com/news and https://afcwimbledonfoundation.com/edi took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

1 to fixGoogle 10092
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/5e4169716545fb14fe2c2174/222/5c5…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 228 words

    The homepage has only about 228 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 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.

6 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Apply for a Club Together Bursary”, “Book Now” and “Sign up to receive our e-newsletters”.

  • Analytics in place

    Analytics detected: Google Analytics and Hotjar.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 3 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads 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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 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.

  • 12 other companies contacted

    Loading the homepage contacts 12 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 afcwimbledonfoundation.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

CMS
Squarespace
Analytics
Google Analytics | Hotjar
Hosting
AWS

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 afcwimbledonfoundation.org.uk, including 14 speed issues, 3 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

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