skinnytan.com website review

minmaxify.com costs a phone 1.4 s of main-thread work and 21 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (minmaxify.com, POWr and Cookiebot and others), adding 1.1 MB and 3.0 s of main-thread time.

Cookiebot costs a phone 517 ms of main-thread work and 161 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.

POWr costs a phone 530 ms of main-thread work and 13 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.

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

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

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

Klaviyo costs a phone 237 ms of main-thread work and 346 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 93 ms of main-thread work and 306 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.

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

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

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

Polyfills for old browsers add 40 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 18.4 s. Good is under 3.8 s.

Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

Your homepage downloads 11.3 MB in 244 requests on a phone: media 8.1 MB (1), scripts 1.3 MB (140) and other files 657 KiB (53). Under 2 MB keeps phones on slow connections fast.

SKIN_TAN_MOBILE_SUMMER.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 (75 KiB) are 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 3.21 g of CO₂e: 385.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

Documents must have <title> element to aid in navigation: 1 element on the page fails 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.

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

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

Headings skip levels (h1 → h3), 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.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“” and “Product title”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 198 pages on skinnytan.com and 6 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

Your homepage links to https://www.skinandtan.co.uk/collections/instant-tan and https://www.skinandtan.co.uk/collections/mousse, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.skinandtan.co.uk/collections/shopall and https://www.skinandtan.co.uk/collections/best-sellers have no <title>, so Google invents the link text in results.

/, https://www.skinandtan.co.uk/pages/delivery, https://www.skinandtan.co.uk/pages/skin-and-tan-uk-reviews, https://www.skinandtan.co.uk/collections/face, https://www.skinandtan.co.uk/collections/gradual-tan and https://www.skinandtan.co.uk/collections/oils-serums and 6 others all use the title “American Express”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.skinandtan.co.uk/pages/delivery, https://www.skinandtan.co.uk/pages/skin-and-tan-uk-reviews, https://www.skinandtan.co.uk/collections/shopall, https://www.skinandtan.co.uk/collections/face, https://www.skinandtan.co.uk/collections/gradual-tan and https://www.skinandtan.co.uk/collections/oils-serums and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.skinandtan.co.uk/collections/shopall, https://www.skinandtan.co.uk/collections/gradual-tan and https://www.skinandtan.co.uk/collections/best-sellers have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.skinandtan.co.uk/collections/gradual-tan, https://www.skinandtan.co.uk/collections/oils-serums, https://www.skinandtan.co.uk/collections/accessories and https://www.skinandtan.co.uk/collections/tan-removal-exfoliators took over 3 s to send their HTML from our server.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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

Before a visitor clicks anything, the page loads Klaviyo (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 11 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 27 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.