mass.co.uk website review

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

2 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.

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

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

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

6 third-party services load with your homepage (Google Tag Manager, Clarity and Google CDN and others), adding 289 KiB and 236 ms of main-thread time.

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

About 20 KiB of CSS is downloaded but never applied on this page.

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

Your largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “UK defence personnel being given a software tutorial by MASS”.

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

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

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

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

106-MASS_Lincoln-8162_2500px.jpg weighs 1.3 MB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example 106-MASS_Lincoln-8162_2500px.jpg at 2,500 px wide, shown at 390 px. Resized copies would save about 1.2 MB.

Your homepage downloads 2.2 MB in 35 requests on a phone: images 1.7 MB (9), scripts 324 KiB (10) and fonts 122 KiB (5). Under 2 MB keeps phones on slow connections fast.

2 images (1.6 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.

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

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

Your page has no <title>, so Google has to invent the blue link in search results.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

There is no robots.txt at mass.co.uk/robots.txt, the first file search crawlers ask for.

The homepage links to 66 pages on mass.co.uk and 6 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) 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.

There is no https://www.mass.co.uk/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.mass.co.uk/what-we-do, https://www.mass.co.uk/what-we-do/cema-and-ew-services, https://www.mass.co.uk/what-we-do/cema-and-ew-services/ew-training, https://www.mass.co.uk/what-we-do/cema-and-ew-services/ew-training-courses, https://www.mass.co.uk/what-we-do/cema-and-ew-services/mission-data-management and https://www.mass.co.uk/what-we-do/cema-and-ew-services/countermeasures and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mass.co.uk/what-we-do/cema-and-ew-services/mission-planning has no <h1> headline, so visitors and search engines get no clear main topic.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

The homepage has only about 155 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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