artaper.com website review

35 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.3 s faster on a phone.

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

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

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

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

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

Google CDN costs a phone 104 ms of main-thread work and 298 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 third-party services load with your homepage (Google CDN, Shopify and Other Google APIs/SDKs and others), adding 670 KiB and 216 ms of main-thread time.

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

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

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

4 files are served with short cache lifetimes, so returning visitors download them again (38 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 7.2 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 11.1 s. Good is under 3.8 s.

Visually, the page fills in at 4.5 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 5.1 MB in 325 requests on a phone: images 3.0 MB (88), other files 1.1 MB (128) and scripts 653 KiB (94). Under 2 MB keeps phones on slow connections fast.

models-wearing-clothing-featuring-popular-paintings-like-the 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).

7 images are downloaded at several times the size a phone draws them, for example First_Touch_nbg.png at 800 px wide, shown at 175 px. Resized copies would save about 397 KiB.

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

8 elements use ARIA attributes their role does not allow, which confuses screen readers.

51 visible links have no text or label, so screen readers cannot say where they go.

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

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

Elements use prohibited ARIA attributes (2 elements).

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

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

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

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

The homepage links to 177 pages on artaper.com and 10 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://artaper.eu/collections/pop-culture-x-streetwear, https://artaper.eu/collections/best-sellers, https://artaper.eu/collections/t-shirts, https://artaper.eu/collections/polos, https://artaper.eu/collections/sweater-hoodies and https://artaper.eu/collections/pants and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://artaper.eu/collections/iconic-artworks, https://artaper.eu/collections/pop-culture-x-streetwear, https://artaper.eu/collections/artists-designers, https://artaper.eu/collections/eco-friendly-collection, https://artaper.eu/collections/best-sellers and https://artaper.eu/collections/custom-clothing and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://artaper.eu/collections/custom-clothing has 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 15 pages linked from your homepage (of 69 found) and read each the way a search engine does.

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

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: 5 trust badges. 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 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 1,000 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 11 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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.