apoftattoo.com website review

About 215 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Evidon, Klaviyo and Clarity and others), adding 665 KiB and 800 ms of main-thread time.

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

Evidon costs a phone 454 ms of main-thread work and 72 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.7 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

Klaviyo costs a phone 134 ms of main-thread work and 311 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.

Polyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

16 files are served with short cache lifetimes, so returning visitors download them again (44 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 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use technologies to personalize and enhance your experie…”.

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

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

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

The first text or image appears after 2.4 s on a phone. Good is under 1.8 s.

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

Your homepage downloads 2.5 MB in 278 requests on a phone: scripts 964 KiB (100), images 703 KiB (34) and other files 686 KiB (88). Under 2 MB keeps phones on slow connections fast.

APOF-SeptTopPiecesMain_Mobile_Banner.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).

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

18 buttons have no accessible name, so screen readers announce just “button”.

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

1 element has a tabindex above 0, which scrambles the keyboard order.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

Your <h1> is empty.

The homepage links to 214 pages on apoftattoo.com and 6 external pages.

https://apoftattoo.com/collections/all, https://apoftattoo.com/pages/shipping-policy, https://apoftattoo.com/collections/backpieces, https://apoftattoo.com/collections/tattooable-pierceable-head and https://apoftattoo.com/collections/lips have no meta description, so Google writes the search snippet from whatever text it finds.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

2 errors were logged to the browser console while the page loaded, for example “Shopify's Google Analytics stub called with: [array Array] See https://help.shopify.com/manual/promoting-marketing/pixe…”.

Chrome logged issues while loading the page (“Content security policy”).

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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

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

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