amacx.co.uk website review

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

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

8 third-party services load with your homepage (hcaptcha.com, Clarity and Shopify and others), adding 1.5 MB and 955 ms of main-thread time.

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

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

hcaptcha.com costs a phone 742 ms of main-thread work and 1.2 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.

About 722 KiB of JavaScript is downloaded but never used on this page.

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

16 images could be 305 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

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

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

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.

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

Your largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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 4.9 MB in 277 requests on a phone: scripts 1.9 MB (60), images 1.5 MB (48) and other files 887 KiB (144). Under 2 MB keeps phones on slow connections fast.

IM-YOURI-MOBILE-EN.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

[role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

8 links have no real href, so search engines can't follow them.

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

The homepage links to 138 pages on amacx.co.uk and 33 external pages.

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

https://www.amacx.co.uk/policies/shipping-policy, https://www.amacx.co.uk/pages/about-us and https://www.amacx.co.uk/pages/become-an-amacx-reseller have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.amacx.co.uk/collections/shop-all and https://www.amacx.co.uk/collections/other use the same meta description. A description written for each page earns more clicks.

https://www.amacx.co.uk/pages/become-an-amacx-reseller has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 error was logged to the browser console while the page loaded, for example “Snippet included twice.”.

Large scripts ship without source maps.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Meta Pixel 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 16 cookies, 1 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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.