supergoop.com website review

Google Tag Manager costs a phone 1.1 s of main-thread work and 880 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.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and Yotpo and others), adding 4.0 MB and 2.8 s of main-thread time.

90 files are served with short cache lifetimes, so returning visitors download them again (2.3 MB).

About 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

Shopify costs a phone 394 ms of main-thread work and 1.6 MB 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.

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

Yotpo costs a phone 370 ms of main-thread work and 531 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.

rise-ai.com costs a phone 192 ms of main-thread work and 395 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 71 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.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

Polyfills for old browsers add 65 KiB JavaScript that modern phones do not need.

37 KiB could be saved by minifying JavaScript.

26 KiB JavaScript is shipped twice across bundles.

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.

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

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

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

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

Real visitors wait 213 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

23 images 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 211 ms to 237 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 9.2 MB in 598 requests on a phone: scripts 5.0 MB (199), images 2.0 MB (102) and other files 1.1 MB (245). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example ResettingPowder_Translucent_Img1_new.jpg at 1,180 px wide, shown at 165 px. Resized copies would save about 68 KiB.

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

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

There is no <h1>, so neither visitors nor Google get a clear main headline.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

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

The homepage links to 88 pages on supergoop.com and 4 external pages.

https://supergoop.com/collections/supersteals is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://supergoop.com/collections/supersteals and https://supergoop.com/pages/bulk-gifting have no meta description, so Google writes the search snippet from whatever text it finds.

https://supergoop.com/products/glowscreen-spf-40, https://supergoop.com/products/everyday-sunscreen, https://supergoop.com/products/antioxidant-infused-sunscreen-mist-with-vitamin-c and https://supergoop.com/products/smooth-and-poreless-mattescreen have no <h1> headline, so visitors and search engines get no clear main topic.

https://supergoop.com/products/unseen-sunscreen-spf-50, https://supergoop.com/products/glowscreen-spf-40, https://supergoop.com/products/everyday-sunscreen, https://supergoop.com/products/antioxidant-infused-sunscreen-mist-with-vitamin-c and https://supergoop.com/products/smooth-and-poreless-mattescreen 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 51 found) and read each the way a search engine does.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

Chrome logged issues while loading the page (“Cookie”).

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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.

The homepage carries about 636 words of visible text.

Before a visitor clicks anything, the page loads Amazon Ads, Criteo, Google Ads, Google Analytics and Google Tag Manager and 6 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 43 cookies (measured from a US location before any click).

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