Website review, no card needed
allbirds.co.uk website review
Visit site (opens in a new tab)Reviewed 7 November 202634 issues · 81 checks
This review found 34 issues worth fixing on allbirds.co.uk, 14 of them high impact, across 81 checks. The most urgent: improve image delivery. 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
77C- #70,010 of 126,442 reviewed websitesbeats 39%
- #44,938 of 70,471 online storesbeats 31%
- #42,693 of 63,972 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 129 ms |
| May 23, 2026 | 128 ms |
| May 30, 2026 | 128 ms |
| Jun 6, 2026 | 128 ms |
| Jun 13, 2026 | 126 ms |
| Jun 20, 2026 | 119 ms |
| Jun 27, 2026 | 113 ms |
| Jul 4, 2026 | 108 ms |
| Jul 11, 2026 | 105 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 102 ms |
| Aug 8, 2026 | 98 ms |
| Aug 15, 2026 | 96 ms |
| Aug 22, 2026 | 95 ms |
| Aug 29, 2026 | 96 ms |
| Sep 5, 2026 | 99 ms |
| Sep 12, 2026 | 104 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 124 ms |
| Oct 10, 2026 | 123 ms |
| Oct 17, 2026 | 123 ms |
| Oct 24, 2026 | 122 ms |
| Oct 31, 2026 | 121 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
1.0 s
2.0 s
3.0 s
4.1 s
5.1 s
6.1 s
7.1 s
8.1 s
Speed
Improve image delivery
2.8 s · 2.4 MB28 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.8 s faster on a phone.
Mobile performance score: 41
41/100Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.5 s
A phone's processor spends 6.5 s on main-thread work while loading, 3.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,061 HTML elements
The page has 4,061 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
900 ms · 403 KiBAbout 403 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Attentive and allbirds.com and others), adding 1.5 MB and 916 ms of main-thread time.
Render-blocking requests
800 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 798 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
788 KiB17 files are served with short cache lifetimes, so returning visitors download them again (788 KiB).
Google Tag Manager adds 668 ms
668 msGoogle Tag Manager costs a phone 668 ms of main-thread work and 520 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.
Attentive adds 91 ms
91 msAttentive costs a phone 91 ms of main-thread work and 829 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.
Legacy JavaScript
150 ms · 9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.
1 checks passed
Server response: 21 ms
21 msYour server sent the HTML in 21 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.
Largest Contentful Paint: 21.2 s
21.2 sYour largest element takes 21.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 26.1 s
26.1 sThe page becomes fully interactive after 26.1 s. Good is under 3.8 s.
Speed Index: 12.3 s
12.3 sVisually, the page fills in at 12.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 129 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 103 ms
103 msReal visitors wait 103 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.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 444 ms
444 msReal visitors wait 444 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 9.2 MB in 257 requests
9.2 MBYour homepage downloads 9.2 MB in 257 requests on a phone: images 6.8 MB (61), scripts 1.3 MB (100) and other files 700 KiB (77). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
403 KiB7 images are downloaded at several times the size a phone draws them, for example A12286_26Q1_Dasher-NZ-Seagrass-Parchment_PDP_LEFT_cd818a12-6 at 1,600 px wide, shown at 300 px. Resized copies would save about 403 KiB.
4 images below the first screen load straight away
4 images further down the page (302 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.6 g of CO₂ per visit
2.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.61 g of CO₂e: 313.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
7 H1 headlines
There are 7 <h1> headlines (“Wildly Comfortable. Super Natural.”, “Wildly Comfortable. Super Natural.” and “Privacy Policy”). One clear main headline is easier for people and search engines.
198 internal links, 14 external
The homepage links to 198 pages on allbirds.co.uk and 14 external pages.
6 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Allbirds: The world’s most comfortable shoes, flats, and clothing made with natural materials like merino wool and euca…”.
Title: 50 characters
Your title is a healthy 50 characters: “Allbirds: Comfortable, Sustainable Shoes & Apparel”.
Canonical URL set
The canonical URL is https://www.allbirds.co.uk/.
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.allbirds.co.uk/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
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.
Text is in the HTML
Your server sends the page's text in the HTML (14,766 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.allbirds.co.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a title
https://www.allbirds.co.uk/pages/terralux-collection and https://www.allbirds.co.uk/pages/varsity-collection have no <title>, so Google invents the link text in results.
5 pages without a meta description
https://www.allbirds.co.uk/pages/store-locator, https://www.allbirds.co.uk/pages/help-center, https://www.allbirds.co.uk/pages/terralux-collection, https://www.allbirds.co.uk/pages/varsity-collection and https://www.allbirds.co.uk/collections/mens-waterproof have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://www.allbirds.co.uk/collections/mens-shoes, https://www.allbirds.co.uk/collections/womens-shoes, https://www.allbirds.co.uk/collections/mens-mizzle-collection, https://www.allbirds.co.uk/collections/womens-bestsellers, https://www.allbirds.co.uk/collections/mens-bestsellers and https://www.allbirds.co.uk/collections/mens-trainers and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.allbirds.co.uk/collections/mens-mizzle-collection has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
2 pages slow to respond
https://www.allbirds.co.uk/collections/womens-shoes and https://www.allbirds.co.uk/collections/womens-bestsellers took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 83 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://shopify-extension.getredo.com/7036-a115bc9f.css' from origin 'https://www.allbirds…”.
2 checks passed
Tap targets are thumb-sized
49 of 52 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 355 words of copy
The homepage carries about 355 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: “SHOP WOMENS” and “SHOP MENS”.
39 calls to action
The homepage has 39 calls to action, for example “Shop All”, “Shop New Dasher NZ” and “Shop New Arrivals”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Phone number on the homepage
Your phone number is on the homepage.
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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta Pixel (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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
26 other companies contacted
Loading the homepage contacts 26 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 allbirds.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Redo · Attentive · Triplewhale · trustpilot.com · integrations-itbl.co · cloudfront.net
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on allbirds.co.uk, 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.