supernovawigs.com website review

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

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

19 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, PayPal and Facebook and others), adding 1.3 MB and 889 ms of main-thread time.

The page goes through 1 redirect before it starts loading, costing about 751 ms. Link and advertise the final URL directly.

The HTML itself could arrive about 500 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Google Tag Manager costs a phone 297 ms of main-thread work and 452 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.2 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

About 70 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.

19 KiB could be saved by minifying JavaScript.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

The layout shifts by 0.658 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

34 images have no width and height attributes, so the layout jumps as each one loads.

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.0 MB in 234 requests on a phone: images 2.4 MB (96), scripts 1.4 MB (44) and other files 129 KiB (86). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

1 link inside paragraphs relies on colour alone to stand out.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

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

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 168 characters; Google truncates after about 160, so the end of your pitch is cut.

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

No XML sitemap at https://www.supernovahair.com/image/sitemap.xml, so Google discovers your pages only by following links.

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

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

The homepage links to 139 pages on supernovawigs.com and 28 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.

There is no https://www.supernovawigs.com/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 120 found) and read each the way a search engine does.

3 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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

1 error was logged to the browser console while the page loaded, for example “oneidInit error: TypeError: Cannot read properties of null (reading 'appendChild')”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

The homepage has only about 26 words of visible text; thin pages give Google and first-time buyers little to go on.

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