Website review, no card needed
shma.co.uk website review
Visit site (opens in a new tab)Reviewed 2 November 202632 issues · 85 checks
This review found 32 issues worth fixing on shma.co.uk, 8 of them high impact, across 85 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.7 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 86 ms |
| May 23, 2026 | 87 ms |
| May 30, 2026 | 88 ms |
| Jun 6, 2026 | 90 ms |
| Jun 13, 2026 | 91 ms |
| Jun 20, 2026 | 89 ms |
| Jun 27, 2026 | 92 ms |
| Jul 4, 2026 | 93 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 96 ms |
| Jul 25, 2026 | 100 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 95 ms |
| Aug 15, 2026 | 94 ms |
| Aug 22, 2026 | 94 ms |
| Aug 29, 2026 | 95 ms |
| Sep 5, 2026 | 98 ms |
| Sep 12, 2026 | 105 ms |
| Sep 19, 2026 | 102 ms |
| Sep 26, 2026 | 102 ms |
| Oct 3, 2026 | 99 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 96 ms |
| Oct 24, 2026 | 101 ms |
| Oct 31, 2026 | 102 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
Speed
Render-blocking requests
1.4 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 477 KiB13 images could be 477 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused CSS
450 ms · 86 KiBAbout 86 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.
Use efficient cache lifetimes
300 ms · 174 KiB7 files are served with short cache lifetimes, so returning visitors download them again (174 KiB).
2,238 HTML elements
The page has 2,238 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Feefo.com adds 46 ms
46 msFeefo.com costs a phone 46 ms of main-thread work and 300 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.
FontAwesome CDN adds 4 ms
4 msFontAwesome CDN costs a phone 4 ms of main-thread work and 323 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.
Reduce unused JavaScript
150 ms · 237 KiBAbout 237 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.
5 third-party services on the page
5 third-party services load with your homepage (Cookiebot, Feefo.com and Cloudflare CDN and others), adding 896 KiB and 168 ms of main-thread time.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
49 KiB49 KiB could be saved by minifying JavaScript.
Legacy JavaScript
6 KiBPolyfills for old browsers add 6 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.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 382 ms of it running JavaScript. That is comfortably low.
Server response: 88 ms
88 msYour server sent the HTML in 88 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 6.5 s
6.5 sYour largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We don't just give legal advice, we redefine what's possibl…”.
Time to Interactive: 11.2 s
11.2 sThe page becomes fully interactive after 11.2 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.256
0.256The layout shifts by 0.256 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
Speed Index: 3.7 s
3.7 sVisually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 86 ms to 102 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 118 ms
118 msReal visitors wait 118 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 481 ms
481 msReal visitors wait 481 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 44% faster for real visitors
-44%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.7 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 10 ms
10 msScripts block the page for only 10 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.3 MB in 70 requests
2.3 MBYour homepage downloads 2.3 MB in 70 requests on a phone: images 1.0 MB (34), scripts 649 KiB (18) and fonts 515 KiB (7). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (126 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 (27 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.65 g of CO₂e: 78.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
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
22 links without text
22 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h4 and h3 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is long (83 characters)
Your title is 83 characters, so Google will cut it off around 60: “Leading Law Firm | Corporate, Family, Property Legal Advice | Shakespeare Martineau”.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
125 internal links, 6 external
The homepage links to 125 pages on shma.co.uk and 6 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Legal expertise with a purpose - a law firm delivering bold solutions with integrity and responsibility.”.
Canonical URL set
The canonical URL is https://www.shma.co.uk/.
Structured data in place
Structured data found: Organization, 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://www.shma.co.uk/sitemap_index.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing url, 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.shma.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,242 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.shma.co.uk/debt-payments is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
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.shma.co.uk/for-life/property-conveyancing/residential-conveyancing, whose canonical is https://www.shma.co.uk/for-life/property-conveyancing. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
2 pages without an H1
https://www.shma.co.uk/debt-payments and https://www.shma.co.uk/our-people 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 81 found) and read each the way a search engine does.
4 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
12 small tap targets
12 of 39 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
Missing source maps
Large scripts ship without source maps.
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
Thin social proof
Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
About 1,027 words of copy
The homepage carries about 1,027 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Call Us”.
9 calls to action
The homepage has 9 calls to action, for example “Contact Us”, “Call Us” and “Get in touch”.
2 short forms
2 short forms (4 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 13 phone links and 0 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 shma.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 Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on shma.co.uk, including 14 speed issues, 3 SEO issues and 1 conversion gap. 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.