mammothbrand.com website review

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

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

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

About 265 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.

8 third-party services load with your homepage (Vimeo, Google Tag Manager and Cookie-Script.com and others), adding 6.1 MB and 554 ms of main-thread time.

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

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

Vimeo costs a phone 275 ms of main-thread work and 5.5 MB 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.

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

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

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

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

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

3 KiB could be saved by minifying CSS.

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

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

Your largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A brand consultancy, specialising in clever answers to chal…”.

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

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

Chrome's UX Report (opens in a new tab) 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.

Your homepage downloads 7.9 MB in 130 requests on a phone: other files 4.1 MB (59), scripts 2.4 MB (35) and images 1.1 MB (16). Under 2 MB keeps phones on slow connections fast.

OnterrisNew-scaled.png weighs 985 KiB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example OnterrisNew-scaled.png at 2,560 px wide, shown at 358 px. Resized copies would save about 812 KiB.

1 image (985 KiB) is 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 2.25 g of CO₂e: 270.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 26 pages on mammothbrand.com and 6 external pages.

https://mammothbrand.com/project/onterris, https://mammothbrand.com/project/citeline, https://mammothbrand.com/project/university-of-warwick, https://mammothbrand.com/project/mmit and https://mammothbrand.com/project/university-of-birmingham have no meta description, so Google writes the search snippet from whatever text it finds.

https://mammothbrand.com/our-work, https://mammothbrand.com/mind-the-crest-why-heritage-reigns-supreme-in-university-logos, https://mammothbrand.com/wheres-the-pride-why-uk-universities-need-a-sporting-wake-up-call and https://mammothbrand.com/careers have no <h1> headline, so visitors and search engines get no clear main topic.

https://mammothbrand.com/contact and https://mammothbrand.com/careers have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

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

3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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.

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

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.

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Hotjar, HubSpot and LinkedIn Insight (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 2 cookies, 2 of them by other companies (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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.