Website review, no card needed

thebmc.co.uk logo

thebmc.co.uk website review

Visit site (opens in a new tab)Reviewed 19 October 202650 issues · 81 checks

This review found 50 issues worth fixing on thebmc.co.uk, 18 of them high impact, across 81 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

Full-page screenshot of thebmc.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thebmc.co.uk at 0.6 s0.6 s
  2. thebmc.co.uk at 1.3 s1.3 s
  3. thebmc.co.uk at 1.9 s1.9 s
  4. thebmc.co.uk at 2.6 s2.6 s
  5. thebmc.co.uk at 3.2 s3.2 s
  6. thebmc.co.uk at 3.9 s3.9 s
  7. thebmc.co.uk at 4.5 s4.5 s
  8. thebmc.co.uk at 5.2 s5.2 s

Speed

12 to fix35
  • Improve image delivery

    11.4 s · 2.5 MB

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

  • Use efficient cache lifetimes

    5.5 s · 5.1 MB

    47 files are served with short cache lifetimes, so returning visitors download them again (5.1 MB).

  • Render-blocking requests

    2.0 s

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

  • Mobile performance score: 35

    35/100

    Your mobile performance score is 35 (desktop: 37). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Brightcove and others), adding 12.6 MB and 998 ms of main-thread time.

  • incrowdsports.com adds 0 ms

    0 ms

    incrowdsports.com costs a phone 0 ms of main-thread work and 7.1 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.

  • Reduce unused JavaScript

    160 ms · 499 KiB

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

  • Google Tag Manager adds 535 ms

    535 ms

    Google Tag Manager costs a phone 535 ms of main-thread work and 503 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.

  • cortextech.io adds 0 ms

    0 ms

    cortextech.io costs a phone 0 ms of main-thread work and 4.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.

  • Facebook adds 314 ms

    314 ms

    Facebook costs a phone 314 ms of main-thread work and 276 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.

  • 6 long tasks on the main thread

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

  • Main-thread work: 2.1 s

    A phone's processor spends 2.1 s on main-thread work while loading, 836 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused CSS

    160 ms · 28 KiB

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

  • Document request latency

    120 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

  • 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: 386 ms

    386 ms

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

Core Web Vitals

7 to fix31
  • Largest Contentful Paint: 18.6 s

    18.6 s

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

  • Time to Interactive: 18.9 s

    18.9 s

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

  • First Contentful Paint: 3.7 s

    3.7 s

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

  • Cumulative Layout Shift: 0.267

    0.267

    The layout shifts by 0.267 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 651 ms

    651 ms

    Scripts block taps and scrolling for 651 ms in total while the page loads. Good is under 200 ms.

  • Speed Index: 4.8 s

    4.8 s

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

  • 2 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

5 to fix18
  • Page weight: 12.9 MB in 58 requests

    12.9 MB

    Your homepage downloads 12.9 MB in 58 requests on a phone: images 11.6 MB (39), scripts 1.0 MB (8) and HTML 180 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 2.9 MB together. On a phone connection a single image that size takes seconds.

  • 7 images far larger than shown

    550 KiB

    7 images are downloaded at several times the size a phone draws them, for example 87f53324-5de2-4359-963e-46371b2571b1.gif at 1,280 px wide, shown at 358 px. Resized copies would save about 550 KiB.

  • 12 images in older formats

    12 images (3.4 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.

  • 9 images below the first screen load straight away

    9 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.6 g of CO₂ per visit

    3.64 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.64 g of CO₂e: 437.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

8 to fixGoogle 7286
  • Hidden but focusable

    14 elements hidden from screen readers can still receive keyboard focus.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 27 images without alt text

    27 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (26 elements)

    All page content should be contained by landmarks: 26 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 16 links without text

    16 visible links have no text or label, so screen readers cannot say where they go.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 31 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 7367
  • No meta description

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 7 H1 headlines

    There are 7 <h1> headlines (“Heaton Park Skills Session | 21st November”, “Heaton Park Skills Session | 12th November” and “Heaton Park Skills Session (Women Only ) | 5th No…”). 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.

  • No XML sitemap

    No XML sitemap at https://thebmc.co.uk/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at thebmc.co.uk/robots.txt, the first file search crawlers ask for.

  • 8 links crawlers can't follow

    8 links have no real href, so search engines can't follow them.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • Open Graph partly set

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 195 internal links, 21 external

    The homepage links to 195 pages on thebmc.co.uk and 21 external pages.

1 checks passed
  • Title: 46 characters

    Your title is a healthy 46 characters: “Home Page - The British Mountaineering Council”.

AI search readiness

1 to fix88
  • 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://thebmc.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,516 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix78
  • 2 pages share a title

    https://thebmc.co.uk/en and https://thebmc.co.uk/cy all use the title “Home Page - The British Mountaineering Council”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://thebmc.co.uk/cy, https://thebmc.co.uk/access, https://thebmc.co.uk/access-news, https://thebmc.co.uk/land-property-trust, https://thebmc.co.uk/get-involved-volunteering and https://thebmc.co.uk/access-conservation-resources and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://thebmc.co.uk/cy, whose canonical is https://thebmc.co.uk/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 5 pages without an H1

    https://thebmc.co.uk/indoor-climbing, https://thebmc.co.uk/indoor-climbing-news, https://thebmc.co.uk/indoor-climbing-learn, https://thebmc.co.uk/indoor-climbing-resources and https://thebmc.co.uk/bmc-associate-wall-members 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 90 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

1 to fixGoogle 10093
  • 14 small tap targets

    14 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

  • 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 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 1,166 words of copy

    The homepage carries about 1,166 words of visible text.

3 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “JOIN THE BMC” and “Contact us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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

    1

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

  • 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 thebmc.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
Tailwind CSS
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on thebmc.co.uk, including 19 speed issues, 8 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