tus.ie website review

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

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

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

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

Google Tag Manager costs a phone 383 ms of main-thread work and 185 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.

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

4 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and Google Fonts and others), adding 249 KiB and 428 ms of main-thread time.

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

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

Polyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

Desktop scores 94 but mobile only 68. 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.

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.

Your largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enhance your browsing experience, serve p…”.

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

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

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

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

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

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

4 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 215 ms to 230 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 1.8 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.9 MB in 49 requests on a phone: media 3.2 MB (1), scripts 344 KiB (13) and images 194 KiB (18). Under 2 MB keeps phones on slow connections fast.

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

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

2 dropdowns have no label.

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

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

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

The homepage links to 177 pages on tus.ie and 15 external pages.

https://tus.ie/contact-us, https://tus.ie/news, https://tus.ie/events and https://tus.ie/courses have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://tus.ie/contact-us, whose canonical is https://tus.ie/contacts. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

6 errors were logged to the browser console while the page loaded, for example “The source list for the Content Security Policy directive 'script-src' contains an invalid source: 'https://.hs-banner.…”.

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.

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 476 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 (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 1 cookie (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.