22dabe22.com website review

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

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

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

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

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

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

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

8 third-party services load with your homepage (Clarity, omnisnippet1.com and Shopify and others), adding 327 KiB and 224 ms of main-thread time.

Polyfills for old browsers add 9 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.

2 KiB JavaScript is shipped twice across bundles.

2 KiB could be saved by minifying JavaScript.

Your largest element takes 9.0 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 9.0 s. Good is under 3.8 s.

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

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

DSC00652_copy_3600x.jpg weighs 1.2 MB. 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 DSC00652_copy_3600x.jpg at 3,600 px wide, shown at 360 px. Resized copies would save about 1.1 MB.

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

22dabe22_premium_streetwear_brand_banner_mobile_800x.png 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 0.54 g of CO₂e: 64.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

All page content should be contained by landmarks: 28 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: 2 elements on the page fail this check, rated moderate by axe-core.

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

Elements marked as presentational should be consistently ignored: 8 elements on the page fail this check, rated minor by axe-core.

Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

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

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

Structured data found (AccountingService, BreadcrumbList, ClothingStore and Organization) but with 1 problem, for example “Organization: missing name”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 111 pages on 22dabe22.com and 11 external pages.

https://www.22dabe22.com/policies/shipping-policy, https://www.22dabe22.com/collections/bracelets, https://www.22dabe22.com/collections/rings and https://www.22dabe22.com/collections/necklaces have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.22dabe22.com/collections/all-clothes-streetwear, https://www.22dabe22.com/collections/sunglasses, https://www.22dabe22.com/collections/bracelets, https://www.22dabe22.com/collections/rings, https://www.22dabe22.com/collections/necklaces and https://www.22dabe22.com/collections/sale-items and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Requests the notification permission on page load.

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: a star rating. 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.

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

The homepage carries about 895 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 mores (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 18 cookies (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 34 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.