Website review, no card needed
tide.co website review
Visit site (opens in a new tab)Reviewed 26 October 202642 issues · 93 checks
This review found 42 issues worth fixing on tide.co, 20 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
Read the full growth playbook for Tide
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
59FClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.5 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 194 ms |
| May 16, 2026 | 195 ms |
| May 23, 2026 | 199 ms |
| May 30, 2026 | 212 ms |
| Jun 6, 2026 | 221 ms |
| Jun 13, 2026 | 228 ms |
| Jun 20, 2026 | 233 ms |
| Jun 27, 2026 | 229 ms |
| Jul 4, 2026 | 228 ms |
| Jul 11, 2026 | 229 ms |
| Jul 18, 2026 | 231 ms |
| Jul 25, 2026 | 231 ms |
| Aug 1, 2026 | 229 ms |
| Aug 8, 2026 | 225 ms |
| Aug 15, 2026 | 222 ms |
| Aug 22, 2026 | 223 ms |
| Aug 29, 2026 | 228 ms |
| Sep 5, 2026 | 233 ms |
| Sep 12, 2026 | 244 ms |
| Sep 19, 2026 | 260 ms |
| Sep 26, 2026 | 359 ms |
| Oct 3, 2026 | 476 ms |
| Oct 10, 2026 | 559 ms |
| Oct 17, 2026 | 645 ms |
| Oct 24, 2026 | 692 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
Reduce unused JavaScript
8.3 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.3 s faster on a phone.
Use efficient cache lifetimes
1.4 s · 188 KiB20 files are served with short cache lifetimes, so returning visitors download them again (188 KiB).
Improve image delivery
1.3 s · 222 KiB1 image could be 222 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.
Mobile performance score: 12
12/100Your mobile performance score is 12 (desktop: 56). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.6 s
A phone's processor spends 7.6 s on main-thread work while loading, 3.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 626 ms. During a long task the page ignores taps.
Legacy JavaScript
300 ms · 29 KiBPolyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
zohocdn.com adds 122 ms
122 mszohocdn.com costs a phone 122 ms of main-thread work and 342 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.
1,524 HTML elements
The page has 1,524 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (zohocdn.com, kustomerapp.com and Trust Pilot and others), adding 824 KiB and 318 ms of main-thread time.
Minify JavaScript
150 ms · 29 KiB29 KiB could be saved by minifying JavaScript.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Reduce unused CSS
63 KiBAbout 63 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 56 but mobile only 12. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify CSS
7 KiB7 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 564 ms
564 msYour server sent the HTML in 564 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.46
0.46For real visitors the layout shifts by 0.46 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 59.5 s
59.5 sYour largest element takes 59.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 15.7 s
15.7 sVisually, the page fills in at 15.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 59.6 s
59.6 sThe page becomes fully interactive after 59.6 s. Good is under 3.8 s.
Total Blocking Time: 3.3 s
3.3 sScripts block taps and scrolling for 3.3 s in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.412
0.412The layout shifts by 0.412 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 301 ms
301 msReal visitors wait 301 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 244% slower for real visitors
+244%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 194 ms to 692 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 10.9 MB in 154 requests
10.9 MBYour homepage downloads 10.9 MB in 154 requests on a phone: images 6.5 MB (23), scripts 3.6 MB (45) and fonts 387 KiB (8). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
260126_TIDE_George_Ford_0955_rt-woBlue_1.svg weighs 5.9 MB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
47 KiB1 image is downloaded at several times the size a phone draws it, for example Everything_you_need_to_run_your_business.png at 1,300 px wide, shown at 330 px. Resized copies would save about 47 KiB.
About 3.1 g of CO₂ per visit
3.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.10 g of CO₂e: 372.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 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.
Accessibility
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
Orphan list items
Some list items are not inside a list.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (25 elements)
All page content should be contained by landmarks: 25 elements on the page fail this check, rated moderate by axe-core.
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.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4, h2 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 8 failed. 4 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 (“One account for all things business” and “”). One clear main headline is easier for people and search engines.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
157 internal links, 17 external
The homepage links to 157 pages on tide.co and 17 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “All your business finance needs in one app, from banking to credit. Join over 1.5 million SMEs worldwide, and get back …”.
Title: 44 characters
Your title is a healthy 44 characters: “Business banking made better | Tide Business”.
Canonical URL set
The canonical URL is https://www.tide.co/.
Structured data in place
Structured data found: Organization.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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.tide.co/sitemap.xml.
AI search readiness
Opted out of AI training for 4 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
4 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 (1,342 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.tide.co/llms.txt (11 KiB, 90 links), a plain-text guide to the site for AI tools.
Other pages
5 pages share a title
/, https://www.tide.co/business-loans, https://www.tide.co/business-savings-account, https://www.tide.co/business-savings-account/cash-isa and https://www.tide.co/business-current-account/switch-business-account all use the title “Business banking made better | Tide Business”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without an H1
https://www.tide.co/pricing has 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 100 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
8 of 9 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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 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.
About 1,074 words of copy
The homepage carries about 1,074 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
15 calls to action
The homepage has 15 calls to action, for example “Start Your Business”, “Learn more arrow_forward” and “Pricing”.
Analytics in place
Analytics detected: Google Tag Manager.
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 Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
8 cookies set on arrival
8Opening the homepage sets 8 cookies (measured from a US location before any click).
18 other companies contacted
Loading the homepage contacts 18 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 tide.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Angular
- Analytics
- Google Tag Manager
Hiring
- Hiring
- 102 open roles
- Teams
- One Platform (53), UK/ Europe Region (31), Enablement (7), One Platform - PCS Sales (6)
- Job board
- greenhouse
- Careers page
- www.tide.co/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on tide.co, including 22 speed issues, 3 SEO issues and 5 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.