mazaeus.com website review

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

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

8 third-party services load with your homepage (Google Tag Manager, Clarity and Klaviyo and others), adding 892 KiB and 658 ms of main-thread time.

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

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

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

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

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

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

2 images could be 25 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.

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

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.

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

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

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

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

2 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 2.3 MB in 184 requests on a phone: scripts 1.1 MB (64), other files 775 KiB (95) and images 397 KiB (15). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (24 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

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 (h1 → h3), which makes the page harder to scan with a screen reader.

There are 3 <h1> headlines (“”, “Product's name” and “Product's name”). One clear main headline is easier for people and search engines.

Your meta description is 187 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.

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

The homepage links to 49 pages on mazaeus.com and 5 external pages.

https://www.mazaeus.com/blogs/news, https://www.mazaeus.com/pages/wholesale, https://www.mazaeus.com/pages/contact-us-page and https://www.mazaeus.com/pages/all-reviews have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mazaeus.com/pages/all-reviews has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=134631221&Ver=2&mid=6f050799-c32b-4a98-8158-48cc3dd987a3&bo=1&sid=1760e880db8b11f19a1bc7df43090f97&vid=176110b0db8b11f190c5a377a6329239&vids=1&msclkid=N&pi=918639831&l.

5 of 11 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 “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

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.

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

Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 561 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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