Website review, no card needed
balfesbikes.co.uk website review
Visit site (opens in a new tab)Reviewed 22 October 202648 issues · 99 checks
This review found 48 issues worth fixing on balfesbikes.co.uk, 16 of them high impact, across 99 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.7 s |
| May 9, 2026 | 1.7 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.9 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 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 210 ms |
| May 9, 2026 | 208 ms |
| May 16, 2026 | 206 ms |
| May 23, 2026 | 205 ms |
| May 30, 2026 | 208 ms |
| Jun 6, 2026 | 211 ms |
| Jun 13, 2026 | 212 ms |
| Jun 20, 2026 | 215 ms |
| Jun 27, 2026 | 217 ms |
| Jul 4, 2026 | 219 ms |
| Jul 11, 2026 | 221 ms |
| Jul 18, 2026 | 223 ms |
| Jul 25, 2026 | 223 ms |
| Aug 1, 2026 | 227 ms |
| Aug 8, 2026 | 232 ms |
| Aug 15, 2026 | 236 ms |
| Aug 22, 2026 | 241 ms |
| Aug 29, 2026 | 244 ms |
| Sep 5, 2026 | 243 ms |
| Sep 12, 2026 | 244 ms |
| Sep 19, 2026 | 250 ms |
| Sep 26, 2026 | 265 ms |
| Oct 3, 2026 | 285 ms |
| Oct 10, 2026 | 300 ms |
| Oct 17, 2026 | 312 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.5 s
1.0 s
1.4 s
1.9 s
2.4 s
2.9 s
3.4 s
3.9 s
Speed
Improve image delivery
15.7 s · 7.3 MB24 images could be 7.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 15.7 s faster on a phone.
Use efficient cache lifetimes
7.0 s · 7.7 MB104 files are served with short cache lifetimes, so returning visitors download them again (7.7 MB).
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
3,331 HTML elements
The page has 3,331 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
600 ms · 779 KiBAbout 779 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Mobile performance score: 57
57/100Your mobile performance score is 57 (desktop: 50). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, omnisnippet1.com and Clarity and others), adding 747 KiB and 528 ms of main-thread time.
Reduce unused CSS
450 ms · 82 KiBAbout 82 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
Legacy JavaScript
300 ms · 51 KiBPolyfills for old browsers add 51 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Minify JavaScript
300 ms · 43 KiB43 KiB could be saved by minifying JavaScript.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify CSS
150 ms · 20 KiB20 KiB could be saved by minifying CSS.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 131 ms. During a long task the page ignores taps.
Duplicated JavaScript
6 KiB6 KiB JavaScript is shipped twice across bundles.
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: 188 ms
188 msYour server sent the HTML in 188 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: 40.5 s
40.5 sYour largest element takes 40.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Savings on Bikes From Scott, Giant, Specialized & Many More…”.
Speed Index: 16.5 s
16.5 sVisually, the page fills in at 16.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 52.7 s
52.7 sThe page becomes fully interactive after 52.7 s. Good is under 3.8 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user INP: 318 ms
318 msReal visitors wait 318 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 46% slower for real visitors
+46%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 210 ms to 312 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.7 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
21 images without width and height
21 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 281 ms
281 msReal visitors wait 281 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 183 ms
183 msScripts block the page for only 183 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 20.2 MB in 168 requests
20.2 MBYour homepage downloads 20.2 MB in 168 requests on a phone: images 17.8 MB (74), scripts 1.7 MB (38) and other files 389 KiB (42). Under 2 MB keeps phones on slow connections fast.
11 images over 500 KB
11 images weigh 10.5 MB together. On a phone connection a single image that size takes seconds.
19 images far larger than shown
8.1 MB19 images are downloaded at several times the size a phone draws them, for example exposure-oct26.png at 1,920 px wide, shown at 299 px. Resized copies would save about 8.1 MB.
2 images in older formats
2 images (137 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 (39 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 5.7 g of CO₂ per visit
5.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.74 g of CO₂e: 688.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (20 elements)
All page content should be contained by landmarks: 20 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
25 links without text
25 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.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (73 characters)
Your title is 73 characters, so Google will cut it off around 60: “Balfe's Bikes | Balfe’s Bikes | London's Leading Bike Shop & Online Store”.
5 links crawlers can't follow
5 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
669 internal links, 5 external
The homepage links to 669 pages on balfesbikes.co.uk and 5 external pages.
7 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Shop online or in-store at Balfe’s Bikes. 12 local bike shops across London & the South East. Click & Collect, servicin…”.
One H1 headline
Your main headline reads: “Balfe's Bikes”.
Canonical URL set
The canonical URL is https://www.balfesbikes.co.uk/.
Structured data in place
Structured data found: Organization and Store.
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.balfesbikes.co.uk/sitemap.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,020 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.balfesbikes.co.uk/llms.txt (13 KiB, 76 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a meta description
https://www.balfesbikes.co.uk/bikes/2026 and https://www.balfesbikes.co.uk/bikes/2027 use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.balfesbikes.co.uk/bikes/mountain-bikes/full-suspension-mtb, whose canonical is https://www.balfesbikes.co.uk/bikes/mountain-bikes. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
11 pages without an H1
https://www.balfesbikes.co.uk/bikes/onsale, https://www.balfesbikes.co.uk/bikes/electric-bikes, https://www.balfesbikes.co.uk/bikes/road-bikes, https://www.balfesbikes.co.uk/bikes/mountain-bikes, https://www.balfesbikes.co.uk/bikes/mountain-bikes/full-suspension-mtb and https://www.balfesbikes.co.uk/bikes/mountain-bikes/hardtail-mtb and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.balfesbikes.co.uk/bikes/onsale and https://www.balfesbikes.co.uk/bikes/2027 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 194 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
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
3 broken images
3 images failed to load on a phone, for example https://www.balfesbikes.co.uk/siteSpecific/customContent/.
42 small tap targets
42 of 104 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 checks passed
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 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: 2 trust badges. 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 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 919 words of copy
The homepage carries about 919 words of visible text.
5 checks passed
27 calls to action
The homepage has 27 calls to action, for example “Shop by Type”, “Ex-Display & Ex-Demo Bikes” and “Shop by Model”.
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Opening hours shown
Your opening hours are on the homepage.
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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Meta Pixel, Microsoft Ads and Microsoft Clarity (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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
26 other companies contacted
Loading the homepage contacts 26 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 balfesbikes.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
- Analytics
- Google Tag Manager
Company
- Founded
- 2008
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on balfesbikes.co.uk, including 21 speed issues, 2 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.