onart.store website review

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

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

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

16 images could be 659 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

4 third-party services load with your homepage (Shopify, debutify.com and shop.app and others), adding 3.8 MB and 140 ms of main-thread time.

Google Fonts costs a phone 0 ms of main-thread work and 3.3 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,057 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

About 42 KiB of JavaScript is downloaded but never used on this page.

18 KiB JavaScript is shipped twice across bundles.

About 11 KiB of CSS is downloaded but never applied on this page.

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

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

Visually, the page fills in at 6.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 6.3 MB in 329 requests on a phone: fonts 3.4 MB (5), images 1.2 MB (32) and other files 875 KiB (97). Under 2 MB keeps phones on slow connections fast.

SMP-NEEDLES-packaging-PRODUCT-SHOTS-2.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 SMP-NEEDLES-packaging-PRODUCT-SHOTS-2.jpg at 1,100 px wide, shown at 360 px. Resized copies would save about 3 KiB.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

5 elements hidden from screen readers can still receive keyboard focus.

autocomplete attribute must be used correctly: 2 elements on the page fail this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 19 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.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

There are 3 <h1> headlines (“”, “Tattoo • SMP • PMU • Aftercare” and “Bishop SMP Needles”). One clear main headline is easier for people and search engines.

Structured data found (BreadcrumbList, Organization, ProductGroup and WebSite) but with 2 problems, for example “Organization: sameAs is not an absolute URL ("#")”.

The homepage links to 84 pages on onart.store and 4 external pages.

https://www.onart.store/collections/all, https://www.onart.store/collections/shop, https://www.onart.store/collections/needles, https://www.onart.store/collections/pigments, https://www.onart.store/collections/machines and https://www.onart.store/collections/smp-aftercare and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.onart.store/collections/shop/Sale, whose canonical is https://www.onart.store/collections/shop/sale. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.onart.store/collections/shop took over 3 s to send its HTML from our server.

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

2 images failed to load on a phone, for example https://www.onart.store/.

19 of 58 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 “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

Social proof on the homepage: 4 testimonial or review blocks. 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.

The homepage carries about 422 words of visible text.

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