Website review, no card needed
gscsolicitors.com website review
Visit site (opens in a new tab)Reviewed 6 November 202630 issues · 84 checks
This review found 30 issues worth fixing on gscsolicitors.com, 13 of them high impact, across 84 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.8 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 4.7 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.6 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.3 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.7 s |
| Oct 24, 2026 | 3.6 s |
| Oct 31, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 118 ms |
| May 23, 2026 | 114 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 148 ms |
| Jun 13, 2026 | 150 ms |
| Jun 20, 2026 | 148 ms |
| Jun 27, 2026 | 147 ms |
| Jul 4, 2026 | 113 ms |
| Jul 11, 2026 | 113 ms |
| Jul 18, 2026 | 110 ms |
| Jul 25, 2026 | 113 ms |
| Aug 1, 2026 | 104 ms |
| Aug 8, 2026 | 94 ms |
| Aug 15, 2026 | 98 ms |
| Aug 22, 2026 | 90 ms |
| Aug 29, 2026 | 101 ms |
| Sep 5, 2026 | 92 ms |
| Sep 12, 2026 | 98 ms |
| Sep 19, 2026 | 102 ms |
| Sep 26, 2026 | 103 ms |
| Oct 3, 2026 | 116 ms |
| Oct 10, 2026 | 112 ms |
| Oct 17, 2026 | 110 ms |
| Oct 24, 2026 | 95 ms |
| Oct 31, 2026 | 94 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
1.6 s49 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Main-thread work: 6.5 s
A phone's processor spends 6.5 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 691 KiBAbout 691 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Clarity and trustindex.io and others), adding 1.2 MB and 708 ms of main-thread time.
Google Tag Manager adds 573 ms
573 msGoogle Tag Manager costs a phone 573 ms of main-thread work and 904 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.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 258 ms. During a long task the page ignores taps.
2,569 HTML elements
The page has 2,569 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 60 KiBAbout 60 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.
Use efficient cache lifetimes
66 KiB16 files are served with short cache lifetimes, so returning visitors download them again (66 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
15 KiB1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 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.
Real-user FCP: 3.6 s
3.6 sReal visitors see the first content after 3.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.6 s
2.6 sReal visitors wait 2.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 43.8 s
43.8 sThe page becomes fully interactive after 43.8 s. Good is under 3.8 s.
Speed Index: 9.8 s
9.8 sVisually, the page fills in at 9.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 856 ms
856 msScripts block taps and scrolling for 856 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 3.9 s
3.9 sYour largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “From our offices in Fitzrovia, in London’s West End, we adv…”. Most of its time is element render delay (2.3 s).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 102 ms
102 msReal visitors wait 102 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.
Tap response (INP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 118 ms to 94 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 12.5 MB in 185 requests
12.5 MBYour homepage downloads 12.5 MB in 185 requests on a phone: images 10.5 MB (53), scripts 1.5 MB (57) and stylesheets 206 KiB (54). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (57 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 3.5 g of CO₂ per visit
3.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.54 g of CO₂e: 424.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must be contained by particular parents (4 elements)
Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h6, h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 68 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Seddons GSC. Experience matters.” and “Seddons GSC. Experience matters.”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
177 internal links, 8 external
The homepage links to 177 pages on gscsolicitors.com and 8 external pages.
6 checks passed
Meta description: 141 characters
Your meta description is 141 characters: “Seddons GSC is a leading law firm in London. Our solicitors provide expert legal advice for individuals and businesses …”.
Title: 52 characters
Your title is a healthy 52 characters: “Seddons GSC | Expert Solicitors & Law Firm in London”.
Canonical URL set
The canonical URL is https://seddons-gsc.com/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and Place.
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://seddons-gsc.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://seddons-gsc.com/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.
3 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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,259 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://seddons-gsc.com/business/dispute-resolution and https://seddons-gsc.com/private/dispute-resolution all use the title “Dispute Resolution Solicitors in London | Seddons GSC”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://seddons-gsc.com/business/dispute-resolution and https://seddons-gsc.com/private/dispute-resolution use the same meta description. A description written for each page earns more clicks.
7 pages slow to respond
https://seddons-gsc.com/contact-us, https://seddons-gsc.com/business/dispute-resolution, https://seddons-gsc.com/business/real-estate-finance, https://seddons-gsc.com/business/corporate-immigration, https://seddons-gsc.com/private/dispute-resolution and https://seddons-gsc.com/private/employment-for-executives and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 73 found) and read each the way a search engine does.
6 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 11 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Creating a worker from 'blob:https://seddons-gsc.com/1801fca9-ab32-4e1a-84a8-c1c920ed29c9' violates the following Conte…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
16 of 17 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Only about 180 words
The homepage has only about 180 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 risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact Us”.
2 calls to action
The homepage has 2 calls to action, for example “Contact Us”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 35 testimonial or review blocks and 49 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call 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 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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
17 other companies contacted
Loading the homepage contacts 17 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 gscsolicitors.com, 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 | Google Tag Manager | Microsoft Clarity
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on gscsolicitors.com, including 17 speed issues, 2 SEO issues and 2 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.