trafalgar.com website review

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

Google Tag Manager costs a phone 1.6 s of main-thread work and 873 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Cookiebot and decagon.ai and others), adding 2.5 MB and 3.3 s of main-thread time.

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

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

Cookiebot costs a phone 713 ms of main-thread work and 40 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.

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

decagon.ai costs a phone 284 ms of main-thread work and 699 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.

Feefo.com costs a phone 53 ms of main-thread work and 299 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.

12 images could be 226 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

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

30 KiB could be saved by minifying JavaScript.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

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

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

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

Your largest element takes 15.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Budapest skyline in Hungary with a bridge over the Danube R…”.

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

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

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

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

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

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

11 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-31, real Chrome visitors' largest content (lcp) went from 3.1 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.6 MB in 218 requests on a phone: scripts 3.7 MB (99), fonts 777 KiB (8) and images 713 KiB (31). Under 2 MB keeps phones on slow connections fast.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

1 button has no accessible name, so screen readers announce just “button”.

26 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 107 pages on trafalgar.com and 13 external pages.

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

https://www.trafalgar.com/en-gb/small-groups, https://www.trafalgar.com/en-gb/deals/loyalty and https://www.trafalgar.com/en-gb/resources/travel-flexibility took over 3 s to send their HTML from our server.

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

19 of 41 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Framing 'https://consentcdn.cookiebot.com/' violates the following report-only Content Security Policy directive: "fram…”.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

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.

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

There is no form on the homepage, so every lead has to click through to another page first.

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 1,085 words of visible text.

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

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

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