Website review, no card needed

superbwigs.com logo

superbwigs.com website review

Visit site (opens in a new tab)Reviewed 11 November 202628 issues · 70 checks

This review found 28 issues worth fixing on superbwigs.com, 3 of them high impact, across 70 checks. The most urgent: 5,178 HTML elements. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of superbwigs.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. superbwigs.com at 0.7 s0.7 s
  2. superbwigs.com at 1.3 s1.3 s
  3. superbwigs.com at 2.0 s2.0 s
  4. superbwigs.com at 2.7 s2.7 s
  5. superbwigs.com at 3.3 s3.3 s
  6. superbwigs.com at 4.0 s4.0 s
  7. superbwigs.com at 4.7 s4.7 s
  8. superbwigs.com at 5.3 s5.3 s

Speed

6 to fix71
  • 5,178 HTML elements

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

  • Mobile performance score: 71

    71/100

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

  • Improve image delivery

    500 ms · 200 KiB

    2 images could be 200 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.

  • Render-blocking requests

    450 ms

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 449 ms. During a long task the page ignores taps.

  • Main-thread work: 2.1 s

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

  • Reduce unused JavaScript

    150 ms · 50 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (improvedcontactform.com, Shopify and Google CDN and others), adding 223 KiB and 150 ms of main-thread time.

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    39 KiB

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

  • Reduce unused CSS

    21 KiB

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

  • Chained critical requests

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 9 ms

    9 ms

    Your server sent the HTML in 9 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix65
  • Largest Contentful Paint: 4.9 s

    4.9 s

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

  • Total Blocking Time: 399 ms

    399 ms

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

  • Time to Interactive: 4.9 s

    4.9 s

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

  • Speed Index: 3.8 s

    3.8 s

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

  • 10 images without width and height

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix90
  • 2 images far larger than shown

    87 KiB

    2 images are downloaded at several times the size a phone draws them, for example b_binner_27761fee-64f3-440f-98d1-13b68713ea81_x800.png at 1,600 px wide, shown at 468 px. Resized copies would save about 87 KiB.

  • About 0.5 g of CO₂ per visit

    0.46 g

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

3 checks passed
  • Page weight: 1.6 MB in 164 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 164 requests on a phone: other files 734 KiB (87), images 385 KiB (21) and scripts 376 KiB (46). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 8995
  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Zoom is disabled

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

  • All page content should be contained by landmarks (1 element)

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

  • 1 text element with low contrast

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

2 checks passed
  • Every image has alt text

    All 205 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10083
  • Title is long (81 characters)

    Your title is 81 characters, so Google will cut it off around 60: “Online Wigs Shop, Wigs Manufacturers, Wigs Suppliers, Wigs Exporters – superbwigs”.

  • Meta description is long (304 characters)

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

  • No social preview image

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 427 internal links, 1 external

    The homepage links to 427 pages on superbwigs.com and 1 external page.

5 checks passed
  • One H1 headline

    Your main headline reads: “superbwigs”.

  • Canonical URL set

    The canonical URL is https://superbwigs.com/.

  • Structured data in place

    Structured data found: BreadcrumbList.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://superbwigs.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,114 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://superbwigs.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 5 small tap targets

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

  • 3 JavaScript errors while loading

    3 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 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix71
  • Thin social proof

    Social proof on the homepage: 98 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • Only about 233 words

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact US”, “Contact USContact US” and “SHOP NOW”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.

  • 11 cookies set on arrival

    11

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

  • No consent tool detected

    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.

  • 20 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at superbwigs.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Ali Reviews · improvedcontactform.com · amazonaws.com · mailerlite.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on superbwigs.com, including 11 speed issues, 4 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25