Website review, no card needed
shawbrook.co.uk website review
Visit site (opens in a new tab)Reviewed 31 October 202616 issues · 78 checks
This review found 16 issues worth fixing on shawbrook.co.uk, 2 of them high impact, across 78 checks. The most urgent: no call to action on the first screen. 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
91AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.1 s |
| May 16, 2026 | 1.1 s |
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 6, 2026 | 1.1 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
| Oct 10, 2026 | 1.1 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 173 ms |
| May 16, 2026 | 174 ms |
| May 23, 2026 | 176 ms |
| May 30, 2026 | 179 ms |
| Jun 6, 2026 | 179 ms |
| Jun 13, 2026 | 179 ms |
| Jun 20, 2026 | 179 ms |
| Jun 27, 2026 | 175 ms |
| Jul 4, 2026 | 177 ms |
| Jul 11, 2026 | 179 ms |
| Jul 18, 2026 | 181 ms |
| Jul 25, 2026 | 185 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 186 ms |
| Aug 15, 2026 | 184 ms |
| Aug 22, 2026 | 180 ms |
| Aug 29, 2026 | 179 ms |
| Sep 5, 2026 | 183 ms |
| Sep 12, 2026 | 188 ms |
| Sep 19, 2026 | 193 ms |
| Sep 26, 2026 | 195 ms |
| Oct 3, 2026 | 193 ms |
| Oct 10, 2026 | 190 ms |
| Oct 17, 2026 | 187 ms |
| Oct 24, 2026 | 184 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
Improve image delivery
800 ms · 445 KiB4 images could be 445 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.
Reduce unused JavaScript
920 ms · 189 KiBAbout 189 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 920 ms faster on a phone.
Mobile performance score: 74
74/100Your mobile performance score is 74. Pages that score under 90 lose visitors before the first paint.
5 third-party services on the page
5 third-party services load with your homepage (piwik.pro, Google Tag Manager and AB Tasty and others), adding 419 KiB and 269 ms of main-thread time.
Reduce unused CSS
190 ms · 32 KiBAbout 32 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 190 ms faster on a phone.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 100 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).
Render-blocking requests
50 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 50 ms.
Use efficient cache lifetimes
36 KiB4 files are served with short cache lifetimes, so returning visitors download them again (36 KiB).
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.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 370 ms of it running JavaScript. That is comfortably low.
Server response: 21 ms
21 msYour server sent the HTML in 21 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.2 s
7.2 sYour largest element takes 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses cookies. If a cookie is not essential to …”.
Time to Interactive: 7.2 s
7.2 sThe page becomes fully interactive after 7.2 s. Good is under 3.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 173 ms to 184 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 182 ms
182 msReal visitors wait 182 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.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: 474 ms
474 msReal visitors wait 474 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Speed Index: 3.2 s
3.2 sVisually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 87 ms
87 msScripts block the page for only 87 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.012
0.012The layout barely moves while loading (CLS 0.012, good is under 0.1).
Images and page weight
1 image far larger than shown
76 KiB1 image is downloaded at several times the size a phone draws it, for example savings-awards-lockup-horizontal.png at 1,392 px wide, shown at 358 px. Resized copies would save about 76 KiB.
1 image in older formats
1 image (188 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.
1 image below the first screen load straight away
1 image further down the page (188 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.4 g of CO₂ per visit
0.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.38 g of CO₂e: 45.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.3 MB in 43 requests
1.3 MBYour homepage downloads 1.3 MB in 43 requests on a phone: scripts 506 KiB (17), images 505 KiB (10) and fonts 286 KiB (5). That is a lean page.
Accessibility
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (BreadcrumbList, LocalBusiness, Organization and WebPage) but with 1 problem, for example “LocalBusiness: missing name”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
63 internal links, 5 external
The homepage links to 63 pages on shawbrook.co.uk and 5 external pages.
6 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Shawbrook: Award-winning savings and lending bank, offering buy-to-let and commercial mortgages, business finance, and …”.
One H1 headline
Your main headline reads: “Give your ISA savings a boost”.
Title: 55 characters
Your title is a healthy 55 characters: “Shawbrook | Savings, Loans, Business & Property Finance”.
Canonical URL set
The canonical URL is https://www.shawbrook.co.uk/.
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.shawbrook.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.shawbrook.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 (604 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a meta description
https://www.shawbrook.co.uk/savings/help and https://www.shawbrook.co.uk/loans/help use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.
7 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.
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 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 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
14 of 14 tappable elements near the top are at least 24 px.
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.
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 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.
About 582 words of copy
The homepage carries about 582 words of visible text.
6 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact”.
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: 1 trust badge and “over 540,000 customers”.
Analytics in place
Analytics detected: Google Analytics.
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.
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 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads 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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
6 other companies contacted
Loading the homepage contacts 6 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 shawbrook.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
- Bootstrap
- Analytics
- Google Analytics
- Hosting
- F5
Company
- Founded
- 2011
- Headquarters
- Brentwood
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 16 issues on shawbrook.co.uk, including 6 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.