Website review, no card needed
thewigcompany.com website review
Visit site (opens in a new tab)Reviewed 11 November 202629 issues · 80 checks
This review found 29 issues worth fixing on thewigcompany.com, 12 of them high impact, across 80 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
85B- #16,022 of 118,069 reviewed websitesbeats 82%
- #10,193 of 67,110 online storesbeats 79%
- #9,906 of 61,191 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.5 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 2.4 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 181 ms |
| May 30, 2026 | 172 ms |
| Jun 6, 2026 | 171 ms |
| Jun 13, 2026 | 170 ms |
| Jun 20, 2026 | 163 ms |
| Jun 27, 2026 | 163 ms |
| Jul 4, 2026 | 171 ms |
| Jul 11, 2026 | 166 ms |
| Jul 18, 2026 | 166 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 153 ms |
| Aug 8, 2026 | 154 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 154 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 155 ms |
| Sep 12, 2026 | 161 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 164 ms |
| Oct 3, 2026 | 163 ms |
| Oct 10, 2026 | 155 ms |
| Oct 17, 2026 | 148 ms |
| Oct 24, 2026 | 148 ms |
| Oct 31, 2026 | 144 ms |
| Nov 7, 2026 | 153 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
1.9 s
2.3 s
2.7 s
3.1 s
Speed
6,204 HTML elements
The page has 6,204 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 5.5 s
A phone's processor spends 5.5 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
200 ms · 812 KiB27 images could be 812 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Mobile performance score: 78
78/100Your mobile performance score is 78. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
8 third-party services on the page
8 third-party services load with your homepage (gotolstoy.com, Shopify and Klaviyo and others), adding 465 KiB and 349 ms of main-thread time.
Reduce unused JavaScript
160 ms · 52 KiBAbout 52 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 160 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 37 KiB9 files are served with short cache lifetimes, so returning visitors download them again (37 KiB).
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 112 ms. During a long task the page ignores taps.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
Reduce unused CSS
14 KiBAbout 14 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.
Duplicated JavaScript
5 KiB5 KiB JavaScript is shipped twice across bundles.
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: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 4.8 s
4.8 sYour largest element takes 4.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 7.8 s
7.8 sThe page becomes fully interactive after 7.8 s. Good is under 3.8 s.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
9 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 165 ms
165 msReal visitors wait 165 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 740 ms
740 msReal visitors wait 740 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 181 ms to 153 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 108 ms
108 msScripts block the page for only 108 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.7 MB in 274 requests
5.7 MBYour homepage downloads 5.7 MB in 274 requests on a phone: images 4.3 MB (92), scripts 592 KiB (79) and other files 583 KiB (57). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
HP--hero_TWCExcl2_Mobile_fc3a11eb-861f-4b2e-8f3d-ae3ec6cbe33 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).
6 images in older formats
6 images (283 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.
About 1.6 g of CO₂ per visit
1.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.62 g of CO₂e: 194.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 text elements with low contrast
2 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)
Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 393 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No page title
Your page has no <title>, so Google has to invent the blue link in search results.
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
412 internal links, 17 external
The homepage links to 412 pages on thewigcompany.com and 17 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.thewigcompany.com/.
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://www.thewigcompany.com/sitemap.xml.
AI search readiness
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.
No llms.txt
There is no https://www.thewigcompany.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.
2 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,073 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages without a title
https://www.thewigcompany.com/policies/shipping-policy, https://www.thewigcompany.com/products/ignite-short-lace-front-wig-jon-renau, https://www.thewigcompany.com/products/sky-short-wig-best-seller-noriko, https://www.thewigcompany.com/products/reese-short-wig-best-seller-noriko, https://www.thewigcompany.com/collections/buy-more-save-more-twc-exclusive-wigs and https://www.thewigcompany.com/collections/womens-wigs and 1 other have no <title>, so Google invents the link text in results.
7 pages without a meta description
https://www.thewigcompany.com/policies/shipping-policy, https://www.thewigcompany.com/products/ignite-short-lace-front-wig-jon-renau, https://www.thewigcompany.com/products/sky-short-wig-best-seller-noriko, https://www.thewigcompany.com/products/reese-short-wig-best-seller-noriko, https://www.thewigcompany.com/collections/buy-more-save-more-twc-exclusive-wigs and https://www.thewigcompany.com/collections/womens-wigs and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages without an H1
https://www.thewigcompany.com/policies/shipping-policy, https://www.thewigcompany.com/products/ignite-short-lace-front-wig-jon-renau, https://www.thewigcompany.com/products/sky-short-wig-best-seller-noriko, https://www.thewigcompany.com/products/reese-short-wig-best-seller-noriko, https://www.thewigcompany.com/collections/buy-more-save-more-twc-exclusive-wigs and https://www.thewigcompany.com/collections/womens-wigs and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://www.thewigcompany.com/products/ignite-short-lace-front-wig-jon-renau and https://www.thewigcompany.com/products/reese-short-wig-best-seller-noriko took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 151 found) and read each the way a search engine does.
3 checks passed
Linked pages load
7 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
121 of 121 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
About 1,164 words of copy
The homepage carries about 1,164 words of visible text.
6 checks passed
19 calls to action
The homepage has 19 calls to action, for example “Buy More, Save More”, “Shop All” and “Shop Products”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 55 testimonial or review blocks, a star rating and “OVER 350,000 HAPPY CUSTOMERS”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, Hotjar and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 3 mores (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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
44 other companies contacted
Loading the homepage contacts 44 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 thewigcompany.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Okendo · Linkedoption · Tolstoy · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · Quantity X · 506.io · rebuyengine.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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- Shopify
Company
- Headquarters
- Pittsburgh
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on thewigcompany.com, including 10 speed issues, 5 SEO issues and 1 conversion gap. 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.