transluxcoach.com website review

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

Your mobile performance score is 63 (desktop: 91). Pages that score under 90 lose visitors before the first paint.

14 images could be 262 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 122 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 620 ms faster on a phone.

About 368 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.

Your homepage downloads 2.5 MB in 59 requests on a phone: images 974 KiB (30), scripts 810 KiB (11) and fonts 572 KiB (4). Under 2 MB keeps phones on slow connections fast.

5 third-party services load with your homepage (Google Tag Manager, Clarity and Google Fonts and others), adding 675 KiB and 499 ms of main-thread time.

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

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

1 file is served with short cache lifetimes, so returning visitors download them again (10 KiB).

Desktop scores 91 but mobile only 63. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

4 KiB could be saved by minifying CSS.

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Luxury Charter Bus Service”.

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

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

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

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

The layout shifts by 0.101 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Chrome's UX Report has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

7 images have no alt text, which hurts accessibility and image search.

3 buttons have no accessible name, so screen readers announce just “button”.

7 visible links have no text or label, so screen readers cannot say where they go.

5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

The page declares lang=“zxx”, which is not a usable language code (“zxx” means “no linguistic content”), so screen readers and translation tools guess.

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 58 pages on transluxcoach.com and 7 external pages.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

3 images are served at too low a resolution for sharp phone screens.

1 link from your homepage to your own site is broken, for example https://www.transluxcoach.com/contact.php (409).

1 link to other sites is dead, for example https://book.mylimobiz.com/v4/transluxcoach (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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 898 words of visible text.