Website review, no card needed
britishairways.com website review
Visit site (opens in a new tab)Reviewed 12 October 202647 issues · 73 checks
This review found 47 issues worth fixing on britishairways.com, 15 of them high impact, across 73 checks. The most urgent: reduce unused CSS. 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
60DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.2 s
4.8 s
Speed
Reduce unused CSS
2.8 s · 568 KiBAbout 568 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.8 s faster on a phone.
Render-blocking requests
3.0 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 3.0 s.
Avoid multiple page redirects
2.1 sThe page goes through 4 redirects before it starts loading, costing about 2.1 s. Link and advertise the final URL directly.
Mobile performance score: 43
43/100Your mobile performance score is 43 (desktop: 51). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Document request latency
900 msThe HTML itself could arrive about 900 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Use efficient cache lifetimes
150 ms · 720 KiB18 files are served with short cache lifetimes, so returning visitors download them again (720 KiB).
Reduce unused JavaScript
818 KiBAbout 818 KiB of JavaScript is downloaded but never used on this page.
Improve image delivery
150 ms · 559 KiB9 images could be 559 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 433 ms. During a long task the page ignores taps.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3 third-party services on the page
3 third-party services load with your homepage (Optanon, mPulse and Adobe Scene7), adding 1.2 MB and 112 ms of main-thread time.
Adobe Scene7 adds 0 ms
0 msAdobe Scene7 costs a phone 0 ms of main-thread work and 911 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 · 29 KiBPolyfills for old browsers add 29 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.
1 checks passed
Server response: 22 ms
22 msYour server sent the HTML in 22 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.
Time to Interactive: 22.9 s
22.9 sThe page becomes fully interactive after 22.9 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.
First Contentful Paint: 5.4 s
5.4 sThe first text or image appears after 5.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 6.6 s
6.6 sYour largest element takes 6.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A view of Tower Bridge and the London skyline at sunset.”.
Real-user INP: 221 ms
221 msReal visitors wait 221 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 444 ms
444 msScripts block taps and scrolling for 444 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.113
0.113The layout shifts by 0.113 while loading, so content jumps under the reader's thumb. Good is under 0.1.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
1 checks passed
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.
Images and page weight
Page weight: 3.9 MB in 113 requests
3.9 MBYour homepage downloads 3.9 MB in 113 requests on a phone: scripts 2.0 MB (15), images 1.2 MB (51) and stylesheets 571 KiB (1). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.12 g of CO₂e: 134.3 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
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
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.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (5 elements).
2 checks passed
Every image has alt text
All 1 image 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 3 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex”: Google is told not to list this page at all.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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 XML sitemap
No XML sitemap at https://britishairways.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at britishairways.com/robots.txt, the first file search crawlers ask for.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
2 checks passed
One H1 headline
Your main headline reads: “Welcome to ba.com”.
Title: 34 characters
Your title is a healthy 34 characters: “British Airways - Information Page”.
AI search readiness
Most text only appears after JavaScript runs
3%A phone browser shows 656 words, but the HTML your server sends has only 20. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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.
No llms.txt
There is no https://britishairways.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.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use …”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
43 of 47 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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 656 words of copy
The homepage carries about 656 words of visible text.
Privacy and tracking
17 cookies set on arrival
17Opening the homepage sets 17 cookies (measured from a US location before any click).
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 britishairways.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 47 issues on britishairways.com, including 24 speed issues, 10 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.