skinscript.com website review

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

Your mobile performance score is 60 (desktop: 99). Pages that score under 90 lose visitors before the first paint.

About 129 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

3 third-party services load with your homepage (Google Tag Manager, Klaviyo and Google Analytics), adding 361 KiB and 255 ms of main-thread time.

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

38 KiB could be saved by minifying CSS.

22 KiB could be saved by minifying JavaScript.

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

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

3 long tasks block the main thread while loading, the longest for 102 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).

Desktop scores 99 but mobile only 60. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 11.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Desert Collection - Prickly Pear and Verde Vine Duo Cover b…”.

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

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

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

Real visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

srx_mega_menu_product_image.webp 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 dc3_cover.webp at 2,048 px wide, shown at 342 px. Resized copies would save about 124 KiB.

1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

1 element hidden from screen readers can still receive keyboard focus.

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

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

All page content should be contained by landmarks: 64 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

4 links have no real href, so search engines can't follow them.

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 140 pages on skinscript.com and 10 external pages.

Your Organization JSON-LD is missing logo, 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.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

1 link from your homepage to your own site is broken, for example https://skinscript.com/cdn-cgi/l/email-protection (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

skinscript.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

skinscript.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

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

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

DMARC is set to p=none, so mail pretending to be skinscript.com is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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