Website review, no card needed
plumbase.co.uk website review
Visit site (opens in a new tab)Reviewed 29 October 202643 issues · 87 checks
This review found 43 issues worth fixing on plumbase.co.uk, 14 of them high impact, across 87 checks. The most urgent: render-blocking requests. 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 97 ms |
| May 16, 2026 | 97 ms |
| May 23, 2026 | 97 ms |
| May 30, 2026 | 98 ms |
| Jun 6, 2026 | 100 ms |
| Jun 13, 2026 | 98 ms |
| Jun 20, 2026 | 100 ms |
| Jun 27, 2026 | 99 ms |
| Jul 4, 2026 | 100 ms |
| Jul 11, 2026 | 102 ms |
| Jul 18, 2026 | 103 ms |
| Jul 25, 2026 | 103 ms |
| Aug 1, 2026 | 102 ms |
| Aug 8, 2026 | 102 ms |
| Aug 15, 2026 | 101 ms |
| Aug 22, 2026 | 102 ms |
| Aug 29, 2026 | 103 ms |
| Sep 5, 2026 | 103 ms |
| Sep 12, 2026 | 102 ms |
| Sep 19, 2026 | 102 ms |
| Sep 26, 2026 | 103 ms |
| Oct 3, 2026 | 102 ms |
| Oct 10, 2026 | 101 ms |
| Oct 17, 2026 | 100 ms |
| Oct 24, 2026 | 99 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
Render-blocking requests
4.8 s41 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.8 s.
Reduce unused JavaScript
3.4 s · 654 KiBAbout 654 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.4 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 385 KiB15 files are served with short cache lifetimes, so returning visitors download them again (385 KiB).
Improve image delivery
1.4 s · 264 KiB4 images could be 264 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
460 ms · 109 KiBAbout 109 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Cookie-Script.com and others), adding 1.0 MB and 411 ms of main-thread time.
Legacy JavaScript
300 ms · 19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 167 ms
167 msGoogle Tag Manager costs a phone 167 ms of main-thread work and 446 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.
Google CDN adds 73 ms
73 msGoogle CDN costs a phone 73 ms of main-thread work and 352 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.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Minify JavaScript
150 ms · 39 KiB39 KiB could be saved by minifying JavaScript.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 87 ms. During a long task the page ignores taps.
Minify CSS
7 KiB7 KiB could be saved by minifying CSS.
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: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 420 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 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: 14.4 s
14.4 sYour largest element takes 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 14.4 s
14.4 sThe page becomes fully interactive after 14.4 s. Good is under 3.8 s.
First Contentful Paint: 4.9 s
4.9 sThe first text or image appears after 4.9 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.417
0.417The layout shifts by 0.417 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 97 ms to 99 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 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 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 FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 419 ms
419 msReal visitors wait 419 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 37 ms
37 msScripts block the page for only 37 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.1 MB in 96 requests
2.1 MBYour homepage downloads 2.1 MB in 96 requests on a phone: scripts 1.1 MB (34), fonts 394 KiB (4) and images 363 KiB (16). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
196 KiB1 image is downloaded at several times the size a phone draws it, for example c3520d91097e20732420a2887e36db1113e59e15.jpg at 2,222 px wide, shown at 391 px. Resized copies would save about 196 KiB.
1 image in older formats
1 image (272 KiB) is 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.
About 0.6 g of CO₂ per visit
0.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.60 g of CO₂e: 71.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
44 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: 44 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
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.
31 internal links, 2 external
The homepage links to 31 pages on plumbase.co.uk and 2 external pages.
4 checks passed
Meta description: 97 characters
Your meta description is 97 characters: “The UK's largest local plumbing supplier. We welcome both trade customers and the general public.”.
Title: 39 characters
Your title is a healthy 39 characters: “Plumbase - Plumbers Merchant - plumbase”.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.plumbase.co.uk/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. 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://www.plumbase.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.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.plumbase.co.uk/stores.html, whose canonical is https://www.plumbase.co.uk/locations.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://www.plumbase.co.uk/stores.html, https://www.plumbase.co.uk/esteem-bathrooms.html, https://www.plumbase.co.uk/get-in-touch.html and https://www.plumbase.co.uk/information/company-policy.html have no <h1> headline, so visitors and search engines get no clear main topic.
8 internal pages checked
We fetched 8 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 8 pages we checked loaded without an error.
Every page has a meta description
All 8 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 8 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://www.plumbase.co.uk' has been block…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
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.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. 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.
Only about 76 words
The homepage has only about 76 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.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Apply for an Account”, “Get in Touch” and “Sign In / Register”.
5 short forms
5 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
21 other companies contacted
Loading the homepage contacts 21 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 plumbase.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
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on plumbase.co.uk, including 18 speed issues, 5 SEO issues and 6 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.