mugman.co.za website review

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

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

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

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

Reduce initial server response time. Google estimates savings of 602 ms on a phone.

The HTML itself could arrive about 600 ms sooner: redirects, a slow server response or missing compression delay everything after it.

About 83 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

Google CDN costs a phone 206 ms of main-thread work and 298 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.

Your server takes 702 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

5 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 520 KiB and 362 ms of main-thread time.

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

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

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

7 KiB could be saved by minifying CSS.

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

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.

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

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

Real visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

1 image (60 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.

2 images further down the page (80 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 0.54 g of CO₂e: 64.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Your title is only 4 characters: “Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 4 characters: “Home”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 285 pages on mugman.co.za and 1 external page.

There is no https://mugman.co.za/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.

Your homepage links to https://mugman.co.za/product-category/mdf-blanks-for-laser-engraving-craft, which answers with an error. Visitors hit a dead end and search engines drop it.

https://mugman.co.za/shop, https://mugman.co.za/product-category/a4-sublimation-printing, https://mugman.co.za/product-category/baby-grows-onesies-personalised-designs, https://mugman.co.za/product-category/braai-aprons-south-african-gifts-for-the-braai-master, https://mugman.co.za/bulk-mug-order and https://mugman.co.za/product-category/cutting-boards and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://mugman.co.za/product-category/braai-aprons-south-african-gifts-for-the-braai-master and https://mugman.co.za/bulk-mug-order took over 3 s to send their HTML from our server.

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

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

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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.

The homepage carries about 314 words of visible text.

Before a visitor clicks anything, the page loads Google Tag Manager (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.

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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.