Website review, no card needed
backhousejones.co.uk website review
Visit site (opens in a new tab)Reviewed 24 October 202637 issues · 86 checks
This review found 37 issues worth fixing on backhousejones.co.uk, 12 of them high impact, across 86 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.1 s |
| May 9, 2026 | 1.1 s |
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 994 ms |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.0 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 6, 2026 | 62 ms |
| Jun 13, 2026 | 56 ms |
| Jun 20, 2026 | 65 ms |
| Jun 27, 2026 | 73 ms |
| Jul 4, 2026 | 78 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 92 ms |
| Jul 25, 2026 | 87 ms |
| Aug 1, 2026 | 99 ms |
| Aug 8, 2026 | 104 ms |
| Aug 15, 2026 | 99 ms |
| Aug 22, 2026 | 91 ms |
| Aug 29, 2026 | 84 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 79 ms |
| Sep 19, 2026 | 72 ms |
| Sep 26, 2026 | 72 ms |
| Oct 3, 2026 | 74 ms |
| Oct 10, 2026 | 74 ms |
| Oct 17, 2026 | 71 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.6 s
1.2 s
1.7 s
2.3 s
2.9 s
3.5 s
4.1 s
4.6 s
Speed
Improve image delivery
1.4 s · 387 KiB3 images could be 387 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: 59
59/100Your mobile performance score is 59 (desktop: 94). 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 (hsappstatic.net, Hubspot and Google Tag Manager and others), adding 1.2 MB and 620 ms of main-thread time.
Use efficient cache lifetimes
500 ms · 127 KiB9 files are served with short cache lifetimes, so returning visitors download them again (127 KiB).
Render-blocking requests
600 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Reduce unused JavaScript
150 ms · 381 KiBAbout 381 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
hsappstatic.net adds 393 ms
393 mshsappstatic.net costs a phone 393 ms of main-thread work and 697 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 284 ms. During a long task the page ignores taps.
Legacy JavaScript
250 ms · 13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
Reduce unused CSS
150 ms · 66 KiBAbout 66 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Phones get a much slower page than desktops
Desktop scores 94 but mobile only 59. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 704 ms of it running JavaScript. That is comfortably low.
Server response: 101 ms
101 msYour server sent the HTML in 101 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: 8.2 s
8.2 sYour largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “To provide the best experiences, we use technologies like c…”.
Time to Interactive: 18.2 s
18.2 sThe page becomes fully interactive after 18.2 s. Good is under 3.8 s.
Speed Index: 7.4 s
7.4 sVisually, the page fills in at 7.4 s (Speed Index). Good is under 3.4 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 CLS: 0.14
0.14For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.
Tap response (INP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 62 ms to 71 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 72 ms
72 msReal visitors wait 72 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 411 ms
411 msReal visitors wait 411 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.085
0.085The layout barely moves while loading (CLS 0.085, good is under 0.1).
Total Blocking Time: 162 ms
162 msScripts block the page for only 162 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 15.8 MB in 89 requests
15.8 MBYour homepage downloads 15.8 MB in 89 requests on a phone: media 12.5 MB (2), images 1.3 MB (24) and scripts 1.1 MB (35). Under 2 MB keeps phones on slow connections fast.
10 images below the first screen load straight away
10 images further down the page (1,009 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (694 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.
About 4.5 g of CO₂ per visit
4.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.48 g of CO₂e: 537.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
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.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
41 links without text
41 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 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 17 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 3 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 social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
180 internal links, 4 external
The homepage links to 180 pages on backhousejones.co.uk and 4 external pages.
6 checks passed
Meta description: 115 characters
Your meta description is 115 characters: “Backhouse Jones delivers industry-specific legal support for HGV/PCV operators, logistics and transport businesses.”.
Title: 39 characters
Your title is a healthy 39 characters: “Award-winning road transport solicitors”.
Canonical URL set
The canonical URL is https://backhousejones.co.uk/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
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://backhousejones.co.uk/sitemap_index.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://backhousejones.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
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 (1,269 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages without a meta description
https://backhousejones.co.uk/expertise/award-winning-road-transport-solicitors/preliminary-hearings-senior-team-leader-meetings and https://backhousejones.co.uk/expertise/employment-hr-solutions/employment-tribunals have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://backhousejones.co.uk/contact, https://backhousejones.co.uk/expertise, https://backhousejones.co.uk/expertise/award-winning-road-transport-solicitors, https://backhousejones.co.uk/expertise/award-winning-road-transport-solicitors/driver-conduct-hearings, https://backhousejones.co.uk/expertise/award-winning-road-transport-solicitors/dvsa-police-investigations and https://backhousejones.co.uk/expertise/award-winning-road-transport-solicitors/environment-agency-animal-welfare and 9 others 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 78 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.
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.
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
4 small tap targets
4 of 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is 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 “Failed to load resource: net::ERR_FAILED”.
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.
Thin social proof
Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
About 408 words of copy
The homepage carries about 408 words of visible text.
5 checks passed
15 calls to action
The homepage has 15 calls to action, for example “Management Buy Ins & Outs”, “Business Start Ups” and “Register now”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and HubSpot (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.
5 cookies set on arrival
5Opening the homepage sets 5 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 backhousejones.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
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on backhousejones.co.uk, including 16 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.