weardott.com website review

8 third-party services load with your homepage (Google Tag Manager, Facebook and Shopify and others), adding 9.1 MB and 525 ms of main-thread time.

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

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

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

Shopify costs a phone 68 ms of main-thread work and 8.5 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 363 KiB of JavaScript is downloaded but never used on this page.

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

Google Tag Manager costs a phone 229 ms of main-thread work and 317 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.4 s on main-thread work while loading, 946 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

About 22 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.

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

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying JavaScript.

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

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

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

The layout shifts by 0.161 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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 241 ms in total while the page loads. Good is under 200 ms.

4 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 11.4 MB in 335 requests on a phone: media 7.9 MB (1), scripts 1.3 MB (123) and other files 1.0 MB (179). Under 2 MB keeps phones on slow connections fast.

2 images (297 KiB) are 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.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

<dt> and <dd> elements must be contained by a <dl>: 4 elements on the page fail this check, rated serious by axe-core.

3 tap targets are too small or too close together to hit reliably with a finger.

<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 1 element on the page fails this check, rated serious by axe-core.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There are 2 <h1> headlines (“<img src="//weardott.com/cdn/shop/files/Dott_Circ…” and “The Future Of Digital Artwork Is Here”). One clear main headline is easier for people and search engines.

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

The homepage links to 16 pages on weardott.com and 6 external pages.

https://weardott.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://weardott.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://weardott.com/products/dott all use the title “Dott”. Search engines can't tell which page to show for a search, so each competes with the others.

https://weardott.com/customer_authentication/redirect and https://weardott.com/pages/wholesale have no meta description, so Google writes the search snippet from whatever text it finds.

https://weardott.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

https://weardott.com/pages/contact and https://weardott.com/pages/wholesale have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 6 pages linked from your homepage 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”.

Social proof on the homepage: 15 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.

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

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