Website review, no card needed
whitbread.com website review
Visit site (opens in a new tab)Reviewed 20 October 202629 issues · 81 checks
This review found 29 issues worth fixing on whitbread.com, 11 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
82BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.9 s |
| May 9, 2026 | 2.6 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 102 ms |
| May 9, 2026 | 104 ms |
| Jun 6, 2026 | 104 ms |
| Jun 13, 2026 | 103 ms |
| Jun 20, 2026 | 99 ms |
| Jun 27, 2026 | 103 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 107 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 110 ms |
| Aug 1, 2026 | 111 ms |
| Aug 8, 2026 | 110 ms |
| Aug 15, 2026 | 109 ms |
| Aug 22, 2026 | 109 ms |
| Aug 29, 2026 | 106 ms |
| Sep 5, 2026 | 106 ms |
| Sep 12, 2026 | 106 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 105 ms |
| Oct 3, 2026 | 106 ms |
| Oct 10, 2026 | 105 ms |
| Oct 17, 2026 | 107 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.5 s
1.0 s
1.5 s
2.0 s
2.5 s
3.0 s
3.6 s
4.1 s
Speed
Improve image delivery
17.3 s · 3.4 MB6 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 17.3 s faster on a phone.
Use efficient cache lifetimes
1.6 s · 3.1 MB27 files are served with short cache lifetimes, so returning visitors download them again (3.1 MB).
Mobile performance score: 63
63/100Your mobile performance score is 63 (desktop: 48). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
750 ms · 130 KiBAbout 130 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.
Render-blocking requests
800 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Reduce unused CSS
450 ms · 64 KiBAbout 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Font display
300 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, brighterir.com and Google Analytics and others), adding 309 KiB and 114 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 56 ms. During a long task the page ignores taps.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 166 ms of it running JavaScript. That is comfortably low.
Server response: 23 ms
23 msYour server sent the HTML in 23 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 39.7 s
39.7 sYour largest element takes 39.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “You can find out more about which cookies we are using or s…”.
Time to Interactive: 40.5 s
40.5 sThe page becomes fully interactive after 40.5 s. Good is under 3.8 s.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
Speed Index: 6.1 s
6.1 sVisually, the page fills in at 6.1 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 102 ms to 107 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 107 ms
107 msReal visitors wait 107 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 664 ms
664 msReal visitors wait 664 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 29% faster for real visitors
-29%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.0 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).
Total Blocking Time: 6 ms
6 msScripts block the page for only 6 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 10.3 MB in 55 requests
10.3 MBYour homepage downloads 10.3 MB in 55 requests on a phone: images 9.7 MB (17), scripts 358 KiB (19) and fonts 114 KiB (5). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
8 KiB1 image is downloaded at several times the size a phone draws it, for example Top_Employer_United_Kingdom_2025_small.png at 600 px wide, shown at 185 px. Resized copies would save about 8 KiB.
2 images in older formats
2 images (88 KiB) are 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.
2 images below the first screen load straight away
2 images further down the page (88 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.9 g of CO₂ per visit
2.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.91 g of CO₂e: 349.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
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 (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h5 and h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (20 characters)
Your title is only 20 characters: “Home - Whitbread PLC”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
81 internal links, 14 external
The homepage links to 81 pages on whitbread.com and 14 external pages.
5 checks passed
Meta description: 129 characters
Your meta description is 129 characters: “Welcome to Whitbread PLC. Whitbread is a leading hospitality business and the owner of Premier Inn, the UK’s biggest ho…”.
Canonical URL set
The canonical URL is https://www.whitbread.co.uk/.
Structured data in place
Structured data found: Article, Corporation, Organization, Person and WebPage.
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.whitbread.co.uk/sitemap_index.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (827 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.whitbread.co.uk/llms.txt (47 KiB, 166 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.whitbread.co.uk/esg-report has no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.
6 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.
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
9 small tap targets
9 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://s.go-mpulse.net/boomerang/TCBVS-VMJ35-KKET5-X4PYU-J56CR' violates the following Content Sec…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
1 checks passed
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.
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 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 281 words of copy
The homepage carries about 281 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “BOOK A ROOM” and “CONTACT”.
2 calls to action
The homepage has 2 calls to action, for example “Book a room” and “Contact”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
8 other companies contacted
Loading the homepage contacts 8 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 whitbread.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on whitbread.com, including 11 speed issues, 5 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.