madido.com website review

About 762 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

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

6 third-party services load with your homepage (YouTube, Shopify and Klaviyo and others), adding 1.6 MB and 492 ms of main-thread time.

YouTube costs a phone 414 ms of main-thread work and 1.0 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.

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

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

Shopify costs a phone 38 ms of main-thread work and 342 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.

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

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

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

24 KiB JavaScript is shipped twice across bundles.

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

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 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “By clicking “Accept all”, you agree that our website can st…”.

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

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

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 3.3 MB in 174 requests on a phone: scripts 1.4 MB (66), images 959 KiB (43) and other files 476 KiB (30). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (39 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.92 g of CO₂e: 110.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 dropdown has no label.

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

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

10 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.

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

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

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

Your <h1> is empty.

The homepage links to 276 pages on madido.com and 3 external pages.

Your Organization JSON-LD is missing 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://madido.com/collections/pavement-breaker-shank-7-8-hex-x-3-1-4, https://madido.com/collections/pavement-breaker-shank-7-8-hex-x-3-1-4-copy, https://madido.com/collections/pavement-breaker-shank-1-hex-x-4-1-4-copy, https://madido.com/collections/pavement-breaker-shank-1-1-8-hex-x-6-copy, https://madido.com/collections/usn-chipper-hex-shank-round-collar and https://madido.com/collections/usn-chipper-hex-shank-oval-collar and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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.

Social proof on the homepage: “20+ Brands”. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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 2,334 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Klaviyo (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, 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.