temporarytattoos.com website review

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

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

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

8 third-party services load with your homepage (Klaviyo, Shopify and Clarity and others), adding 1.8 MB and 728 ms of main-thread time.

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

11 images could be 239 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.

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

Klaviyo costs a phone 324 ms of main-thread work and 639 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 147 ms of main-thread work and 599 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.

azurefd.net costs a phone 73 ms of main-thread work and 321 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.

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

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

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

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

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

Your largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Person with temporary tattoos on arms against a dark backgr…”.

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

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

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' tap response (inp) went from 182 ms to 213 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.7 MB in 348 requests on a phone: scripts 1.6 MB (175), images 779 KiB (32) and other files 666 KiB (87). Under 2 MB keeps phones on slow connections fast.

TT_Custom_Header_Testing_SemiPerm_Mobile_01_bdd2a200-2bb7-42 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 acb0ac39-af96-40ee-ae61-ff29dbfc7199.png at 500 px wide, shown at 122 px. Resized copies would save about 89 KiB.

1 image (192 KiB) is 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.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is 82 characters, so Google will cut it off around 60: “TemporaryTattoos.com ⋅ Custom Tattoo Shop & Manufacturer ⭐⭐⭐⭐⭐ – Temporary Tattoos”.

The homepage links to 540 pages on temporarytattoos.com and 5 external pages.

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

/customer_authentication/redirect, /products/app-semi-permanent-tattoo, /products/app-glow-in-the-dark-custom-tattoo and /products/app-metallic-custom-tattoo are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/policies/shipping-policy, /customer_authentication/redirect, /collections/new-arrivals and /pages/brands have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/all, /policies/shipping-policy, /pages/contact, /customer_authentication/redirect, /pages/tattoo-designer and /pages/halloween-temporary-tattoos and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/collections/all, /collections/new-arrivals, /collections/best-sellers, /collections/classic-temporary-tattoos and /collections/semi-permanent-tattoos 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 15 pages linked from your homepage (of 198 found) and read each the way a search engine does.

3 errors were logged to the browser console while the page loaded, for example “[bugsnag] Session failed to send… Error: Request failed with status 0”.

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 2,142 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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