thetrainline.com website review

About 1,006 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

1 image could be 132 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

About 75 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

11 long tasks block the main thread while loading, the longest for 336 ms. During a long task the page ignores taps.

A phone's processor spends 3.2 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 1,930 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Optanon costs a phone 65 ms of main-thread work and 383 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.

8 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Optanon and others), adding 998 KiB and 456 ms of main-thread time.

8 files are served with short cache lifetimes, so returning visitors download them again (149 KiB).

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

The page becomes fully interactive after 17.3 s. Good is under 3.8 s.

Your largest element takes 7.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

Scripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.

Visually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.

Real visitors wait 488 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

3 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 453 ms to 522 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 2.7 MB in 79 requests on a phone: scripts 2.0 MB (21), other files 264 KiB (30) and images 235 KiB (22). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.76 g of CO₂e: 91.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

ARIA tab nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (2 elements).

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 209 pages on thetrainline.com and 14 external pages.

https://www.thetrainline.com/live has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.thetrainline.com/live 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.

We fetched 15 pages linked from your homepage (of 170 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Your longest form asks for 8 fields (0 required). Every extra field lowers completion.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 695 words of visible text.

Before a visitor clicks anything, the page loads Google Ads 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.

Opening the homepage sets 10 cookies (measured from a US location before any click).

Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.