artdot.com website review

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

Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (loloyal.com, Shopify and Google CDN and others), adding 2.2 MB and 1.8 s of main-thread time.

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

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

loloyal.com costs a phone 623 ms of main-thread work and 719 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.

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

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

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

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

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

About 51 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 11 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.

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

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

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.

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 122 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 image have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.3 MB in 434 requests on a phone: images 2.5 MB (61), scripts 2.0 MB (128) and other files 1.3 MB (210). Under 2 MB keeps phones on slow connections fast.

mobile_a9408749-4b3f-4da8-b404-256fc96edc3f.jpg 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).

1 image is downloaded at several times the size a phone draws it, for example sparkle_bob.png at 452 px wide, shown at 60 px. Resized copies would save about 42 KiB.

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

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

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

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (5 elements).

Your title is 68 characters, so Google will cut it off around 60: “ARTDOT® : Shop the Best Diamond Painting Kits, Storage & Accessories”.

There are 3 <h1> headlines (“ARTDOT”, “Discover Your Diamond Painting Soul Type” and “SPARKLE DROP”). 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.

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

The homepage links to 247 pages on artdot.com and 7 external pages.

/collections/2026-best-sell has no meta description, so Google writes the search snippet from whatever text it finds.

/collections/2026-best-sell has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://www.artdot.com/.

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

6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Requests the notification permission on page load.

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

artdot.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

The homepage carries about 1,784 words of visible text.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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