Website review, no card needed
bibbyfinancialservices.com website review
Visit site (opens in a new tab)Reviewed 31 October 202626 issues · 87 checks
This review found 26 issues worth fixing on bibbyfinancialservices.com, 6 of them high impact, across 87 checks. The most urgent: fails Core Web Vitals for real visitors. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.0 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.6 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 154 ms |
| May 16, 2026 | 162 ms |
| May 23, 2026 | 159 ms |
| May 30, 2026 | 177 ms |
| Jun 6, 2026 | 177 ms |
| Jun 13, 2026 | 169 ms |
| Jun 20, 2026 | 169 ms |
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 170 ms |
| Jul 11, 2026 | 194 ms |
| Jul 18, 2026 | 179 ms |
| Jul 25, 2026 | 179 ms |
| Aug 1, 2026 | 171 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 120 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 117 ms |
| Oct 10, 2026 | 115 ms |
| Oct 17, 2026 | 117 ms |
| Oct 24, 2026 | 120 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.3 s
1.9 s
2.5 s
3.2 s
3.8 s
4.5 s
5.1 s
Speed
Reduce unused JavaScript
750 ms · 866 KiBAbout 866 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
Mobile performance score: 64
64/100Your mobile performance score is 64. 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 (Google Tag Manager, Trust Pilot and Vimeo and others), adding 1.7 MB and 393 ms of main-thread time.
Use efficient cache lifetimes
304 KiB23 files are served with short cache lifetimes, so returning visitors download them again (304 KiB).
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 232 ms
232 msGoogle Tag Manager costs a phone 232 ms of main-thread work and 535 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.
Vimeo adds 35 ms
35 msVimeo costs a phone 35 ms of main-thread work and 517 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.
LiveChat adds 20 ms
20 msLiveChat costs a phone 20 ms of main-thread work and 363 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.
Improve image delivery
233 KiB2 images could be 233 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
150 ms · 22 KiBAbout 22 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 154 ms. During a long task the page ignores taps.
Render-blocking requests
150 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Legacy JavaScript
47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
8 KiB8 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 185 ms
185 msYour server sent the HTML in 185 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 CLS: 0.53
0.53For real visitors the layout shifts by 0.53 (75th percentile). Good is under 0.1.
Time to Interactive: 19.9 s
19.9 sThe page becomes fully interactive after 19.9 s. Good is under 3.8 s.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Two women looking at a screen in an office”.
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 234 ms
234 msScripts block taps and scrolling for 234 ms in total while the page loads. Good is under 200 ms.
7 checks passed
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: 140 ms
140 msReal visitors wait 140 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 760 ms
760 msReal visitors wait 760 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 25% faster for real visitors
-25%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 154 ms to 120 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 39% faster for real visitors
-39%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 1.5 s 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: 3.1 MB in 145 requests
3.1 MBYour homepage downloads 3.1 MB in 145 requests on a phone: scripts 2.3 MB (87), images 417 KiB (13) and HTML 207 KiB (5). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.88 g of CO₂e: 105.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h6 and h2 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (3 elements).
1 checks passed
Every image has alt text
All 16 images in the HTML carry an alt attribute.
SEO
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Invoice Finance | Invoice Discounting | Invoice Factoring | Bibby FS”.
No social preview image
No Open Graph image (also missing: og:title, og:description), 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.
49 internal links, 7 external
The homepage links to 49 pages on bibbyfinancialservices.com and 7 external pages.
6 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Bibby Financial Services is the UK’s leading independent invoice finance specialist, currently providing cash flow fund…”.
One H1 headline
Your main headline reads: “How Bibby Financial Servicescan help your business...”.
Canonical URL set
The canonical URL is https://www.bibbyfinancialservices.com/.
Structured data in place
Structured data found: Organization.
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.bibbyfinancialservices.com/sitemap-en-gb.xml.
AI search readiness
No llms.txt
There is no https://www.bibbyfinancialservices.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 contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (982 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 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
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=30006106&Ver=2&mid=871cf261-6518-467d-8ba4-b00edcdde272&bo=1&sid=f5a8e6b0d57811f1860dc3fa8d1a4a9b&vid=f5a914a0d57811f1b6c9f1f70806c049&vids=1&msclkid=N&pi=918639831&lg.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
2 third-party cookies
2 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://c-eudc.lytics.io/static/pathfora.min.css' from origin 'https://www.bibbyfinancials…”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
14 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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 969 words of copy
The homepage carries about 969 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: “Get started”.
3 calls to action
The homepage has 3 calls to action, for example “Get started”, “Call us today” and “Contact us”.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks, 1 customer or partner logo and “over 8,500 businesses”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 4 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 Ads (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
26 cookies set on arrival
26Opening the homepage sets 26 cookies, 6 of them by other companies (measured from a US location before any click).
38 other companies contacted
Loading the homepage contacts 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 bibbyfinancialservices.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Company
- Founded
- 1982
- Headquarters
- Brno
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on bibbyfinancialservices.com, including 15 speed issues, 2 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.