Website review, no card needed
hurlinghamclub.org.uk website review
Visit site (opens in a new tab)Reviewed 18 November 202633 issues · 81 checks
This review found 33 issues worth fixing on hurlinghamclub.org.uk, 15 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.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 999 ms |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 972 ms |
| Oct 17, 2026 | 967 ms |
| Oct 24, 2026 | 1.0 s |
| Oct 31, 2026 | 910 ms |
| Nov 7, 2026 | 917 ms |
| Nov 14, 2026 | 928 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 97 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 98 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 95 ms |
| Jul 11, 2026 | 94 ms |
| Jul 18, 2026 | 94 ms |
| Jul 25, 2026 | 96 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 99 ms |
| Aug 15, 2026 | 102 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 104 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 106 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 101 ms |
| Oct 17, 2026 | 102 ms |
| Oct 24, 2026 | 102 ms |
| Oct 31, 2026 | 101 ms |
| Nov 7, 2026 | 102 ms |
| Nov 14, 2026 | 103 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
2.9 s · 8.0 MB6 images could be 8.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.9 s faster on a phone.
Use efficient cache lifetimes
3.5 s · 2.0 MB25 files are served with short cache lifetimes, so returning visitors download them again (2.0 MB).
Render-blocking requests
4.2 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Reduce unused JavaScript
1.2 s · 576 KiBAbout 576 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Font display
1.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.0 s).
Mobile performance score: 62
62/100Your mobile performance score is 62. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
620 ms · 106 KiBAbout 106 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 620 ms faster on a phone.
Google Tag Manager adds 321 ms
321 msGoogle Tag Manager costs a phone 321 ms of main-thread work and 494 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.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Facebook and New Relic and others), adding 810 KiB and 459 ms of main-thread time.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 141 ms. During a long task the page ignores taps.
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 KiB JavaScript that modern phones do not need.
Minify JavaScript
20 KiB20 KiB could be saved by minifying JavaScript.
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.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 666 ms 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
Largest Contentful Paint: 8.1 s
8.1 sYour largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 20.5 s
20.5 sThe page becomes fully interactive after 20.5 s. Good is under 3.8 s.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Speed Index: 4.8 s
4.8 sVisually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 96 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 92 ms
92 msReal visitors wait 92 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.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 563 ms
563 msReal visitors wait 563 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.1 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 147 ms
147 msScripts block the page for only 147 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.023
0.023The layout barely moves while loading (CLS 0.023, good is under 0.1).
Images and page weight
Page weight: 9.9 MB in 50 requests
9.9 MBYour homepage downloads 9.9 MB in 50 requests on a phone: images 8.5 MB (12), scripts 1.2 MB (19) and fonts 141 KiB (3). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 8.0 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
5.7 MB6 images are downloaded at several times the size a phone draws them, for example tennis-championships-2015_dsc_2778.jpg at 2,200 px wide, shown at 390 px. Resized copies would save about 5.7 MB.
6 images in older formats
6 images (8.2 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.
3 images below the first screen load straight away
3 images further down the page (2.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.8 g of CO₂ per visit
2.82 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.82 g of CO₂e: 338.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h1 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 4 failed. 1 more 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.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
69 internal links, 1 external
The homepage links to 69 pages on hurlinghamclub.org.uk and 1 external page.
6 checks passed
Meta description: 122 characters
Your meta description is 122 characters: “The Hurlingham Club is a renowned private members’ club in Fulham, South West London, set on 42 acres by the River Tham…”.
One H1 headline
Your main headline reads: “WELCOME TO THE HURLINGHAM CLUB”.
Title: 53 characters
Your title is a healthy 53 characters: “The Hurlingham Club | Private Members' Club in London”.
Canonical URL set
The canonical URL is https://www.hurlinghamclub.org.uk/hurlingham-home.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.hurlinghamclub.org.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.hurlinghamclub.org.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 (269 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.hurlinghamclub.org.uk/hurlingham-home and / all use the title “The Hurlingham Club | Private Members' Club in London”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://www.hurlinghamclub.org.uk/hurlingham-home/private-events/event-enquiries, https://www.hurlinghamclub.org.uk/hurlingham-home/private-events/sports-hire and https://www.hurlinghamclub.org.uk/hurlingham-home/private-events/christmas 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 /, whose canonical is https://www.hurlinghamclub.org.uk/hurlingham-home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.hurlinghamclub.org.uk/hurlingham-home/private-events/event-enquiries has 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 25 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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Identifier 'loadingText' has already been declared”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
19 of 19 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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 161 words
The homepage has only about 161 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “CONTACT US”, “CONTACT” and “CONTACT THE CLUB”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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 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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
10 other companies contacted
Loading the homepage contacts 10 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 hurlinghamclub.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
- Framework
- React
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on hurlinghamclub.org.uk, including 12 speed issues, 1 SEO issue and 5 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.