Website review, no card needed

eurail.com logo

eurail.com website review

Visit site (opens in a new tab)Reviewed 4 November 202632 issues · 81 checks

This review found 32 issues worth fixing on eurail.com, 14 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.5 sJun 6Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
Jun 6, 20261.5 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
239 ms203 msJun 6Oct 31216 ms
Show as table
DateReal-visitor tap response (INP)
Jun 6, 2026207 ms
Jun 13, 2026209 ms
Jun 20, 2026211 ms
Jun 27, 2026213 ms
Jul 4, 2026217 ms
Jul 11, 2026222 ms
Jul 18, 2026225 ms
Jul 25, 2026226 ms
Aug 1, 2026225 ms
Aug 8, 2026222 ms
Aug 15, 2026221 ms
Aug 22, 2026223 ms
Aug 29, 2026227 ms
Sep 5, 2026232 ms
Sep 12, 2026235 ms
Sep 19, 2026229 ms
Sep 26, 2026227 ms
Oct 3, 2026228 ms
Oct 10, 2026227 ms
Oct 17, 2026227 ms
Oct 24, 2026225 ms
Oct 31, 2026216 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

Full-page screenshot of eurail.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eurail.com at 0.4 s0.4 s
  2. eurail.com at 0.8 s0.8 s
  3. eurail.com at 1.2 s1.2 s
  4. eurail.com at 1.6 s1.6 s
  5. eurail.com at 2.0 s2.0 s
  6. eurail.com at 2.4 s2.4 s
  7. eurail.com at 2.8 s2.8 s
  8. eurail.com at 3.2 s3.2 s

Speed

10 to fix39
  • Use efficient cache lifetimes

    2.0 s · 2.1 MB

    75 files are served with short cache lifetimes, so returning visitors download them again (2.1 MB).

  • Reduce unused JavaScript

    2.5 s · 740 KiB

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

  • Mobile performance score: 39

    39/100

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

  • 3,822 HTML elements

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (interrail.eu, Google Tag Manager and Cookiebot and others), adding 847 KiB and 876 ms of main-thread time.

  • Improve image delivery

    150 ms · 810 KiB

    8 images could be 810 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.

  • Render-blocking requests

    650 ms

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

  • interrail.eu adds 480 ms

    480 ms

    interrail.eu costs a phone 480 ms of main-thread work and 467 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.

  • Main-thread work: 3.9 s

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

  • 14 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 48 KiB

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

  • Legacy JavaScript

    8 KiB

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

  • 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.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 14.6 s

    14.6 s

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

  • Time to Interactive: 19.8 s

    19.8 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

    The first text or image appears after 4.2 s on a phone. Good is under 1.8 s.

  • Speed Index: 7.4 s

    7.4 s

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

  • Total Blocking Time: 912 ms

    912 ms

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

  • 27 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +6%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

7 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: 1.4 s

    1.4 s

    Real visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 152 ms

    152 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.9 s

    0.9 s

    Real visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 337 ms

    337 ms

    Real visitors wait 337 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix28
  • Page weight: 6.4 MB in 100 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 100 requests on a phone: images 2.5 MB (60), media 1.8 MB (1) and scripts 1.7 MB (18). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Mediterranean-itinerary-Trip-Planner-map.png weighs 630 KiB. On a phone connection a single image that size takes seconds.

  • 8 images in older formats

    8 images (2.1 MB) 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.

  • 3 images far larger than shown

    411 KiB

    3 images are downloaded at several times the size a phone draws them, for example itinerary-mediterranean-cannes.jpg at 1,600 px wide, shown at 320 px. Resized copies would save about 411 KiB.

  • 3 images below the first screen load straight away

    3 images further down the page (642 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.83 g

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

Accessibility

4 to fixGoogle 9495
  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 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.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate 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. (1 element).

2 checks passed
  • Every image has alt text

    All 60 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10091
  • Meta description is long (185 characters)

    Your meta description is 185 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 4 problems

    Structured data found ((untyped) and Organization) but with 4 problems, for example “Organization: missing name”.

  • 52 internal links, 8 external

    The homepage links to 52 pages on eurail.com and 8 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “One Pass. All of Europe.”.

  • Title: 62 characters

    Your title is a healthy 62 characters: “Travel through Europe by Train | 33 Countries with 1 Rail Pass”.

  • Canonical URL set

    The canonical URL is https://www.interrail.com/en.

  • 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.interrail.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.interrail.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.

2 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 (1,235 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

7 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.

  • 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

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    17 of 21 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 812 words of copy

    The homepage carries about 812 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Order overview”, “Book seats” and “GET STARTED”.

  • 1 short form

    A short form (4 fields at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 8 cookies set on arrival

    8

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

  • 7 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 eurail.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
CloudFront

Hiring

Hiring
1 open role
Teams
Product (1)
Job board
recruitee

Company

Founded
2019
Headquarters
Utrecht

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on eurail.com, including 16 speed issues, 2 SEO issues and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25