Website review, no card needed

ywigs.com logo

ywigs.com website review

Visit site (opens in a new tab)Reviewed 7 November 202649 issues · 94 checks

This review found 49 issues worth fixing on ywigs.com, 16 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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

Real-visitor load time (LCP)75th percentile, phones
1.9 s1.6 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.9 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.9 s
Oct 24, 20261.8 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
133 ms101 msMay 16Oct 31129 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026105 ms
May 23, 2026105 ms
May 30, 2026105 ms
Jun 6, 2026106 ms
Jun 13, 2026109 ms
Jun 20, 2026108 ms
Jun 27, 2026110 ms
Jul 4, 2026110 ms
Jul 11, 2026110 ms
Jul 18, 2026111 ms
Jul 25, 2026111 ms
Aug 1, 2026112 ms
Aug 8, 2026113 ms
Aug 15, 2026119 ms
Aug 22, 2026120 ms
Aug 29, 2026117 ms
Sep 5, 2026113 ms
Sep 12, 2026119 ms
Sep 19, 2026118 ms
Sep 26, 2026120 ms
Oct 3, 2026120 ms
Oct 10, 2026121 ms
Oct 17, 2026122 ms
Oct 24, 2026127 ms
Oct 31, 2026129 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

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

How it loaded on a phone

  1. ywigs.com at 1.4 s1.4 s
  2. ywigs.com at 2.9 s2.9 s
  3. ywigs.com at 4.3 s4.3 s
  4. ywigs.com at 5.8 s5.8 s
  5. ywigs.com at 7.2 s7.2 s
  6. ywigs.com at 8.7 s8.7 s
  7. ywigs.com at 10.1 s10.1 s
  8. ywigs.com at 11.5 s11.5 s

Speed

14 to fix45
  • Reduce unused JavaScript

    2.9 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.9 s faster on a phone.

  • Render-blocking requests

    1.6 s

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

  • Mobile performance score: 45

    45/100

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

  • Main-thread work: 6.6 s

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

  • 5,722 HTML elements

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

  • Use efficient cache lifetimes

    150 ms · 20.5 MB

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

  • Improve image delivery

    800 ms · 6.3 MB

    58 images could be 6.3 MB 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (loox.io, quickcep.com and vidhash.net and others), adding 5.3 MB and 1.2 s of main-thread time.

  • Reduce unused CSS

    600 ms · 247 KiB

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

  • Minify CSS

    600 ms · 107 KiB

    107 KiB could be saved by minifying CSS.

  • Shopify adds 99 ms

    99 ms

    Shopify costs a phone 99 ms of main-thread work and 3.2 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.

  • loox.io adds 328 ms

    328 ms

    loox.io costs a phone 328 ms of main-thread work and 28 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.

  • quickcep.com adds 191 ms

    191 ms

    quickcep.com costs a phone 191 ms of main-thread work and 560 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.

  • vidhash.net adds 164 ms

    164 ms

    vidhash.net costs a phone 164 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.

  • Legacy JavaScript

    150 ms · 73 KiB

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

  • 8 long tasks on the main thread

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

  • 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: 10 ms

    10 ms

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

Core Web Vitals

10 to fix67
  • 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: 25.8 s

    25.8 s

    Your largest element takes 25.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “black friday mega sale”.

  • Speed Index: 28.7 s

    28.7 s

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

  • Time to Interactive: 96.6 s

    96.6 s

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

  • Cumulative Layout Shift: 0.272

    0.272

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

  • Real-user LCP: 3.0 s

    3.0 s

    Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Tap response (INP) got 22% slower for real visitors

    +22%

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

  • First Contentful Paint: 2.2 s

    2.2 s

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

  • Total Blocking Time: 220 ms

    220 ms

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

  • 1 image without width and height

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

4 checks passed
  • Real-user INP: 140 ms

    140 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.8 s

    1.8 s

    Real visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 660 ms

    660 ms

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

Images and page weight

5 to fix38
  • Page weight: 32.9 MB in 548 requests

    32.9 MB

    Your homepage downloads 32.9 MB in 548 requests on a phone: images 28.1 MB (132), scripts 2.8 MB (114) and other files 1.5 MB (285). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    black-friday-mega-sale.webp weighs 881 KiB. On a phone connection a single image that size takes seconds.

  • 32 images in older formats

    32 images (3.2 MB) 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.

  • 12 images below the first screen load straight away

    12 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • An image on the first screen is lazy-loaded

    ywigs-mystery-box.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).

  • About 9.3 g of CO₂ per visit

    9.32 g

    By the Sustainable Web Design model, a visit to your homepage emits about 9.32 g of CO₂e: 1118.3 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

6 to fixGoogle 9493
  • 70 text elements with low contrast

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

  • Hidden but focusable

    9 elements hidden from screen readers can still receive keyboard focus.

  • 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.

  • 63 form fields without a label

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

  • 10 links without text

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

  • Headings should not be empty (7 elements)

    Headings should not be empty: 7 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 158 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Ywigs® Crochet Human Hair & Braiding Bulk Hair in Los Angeles | Ywigs”.

  • Meta description is long (166 characters)

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 201 internal links, 16 external

    The homepage links to 201 pages on ywigs.com and 16 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Ywigs”.

  • Canonical URL set

    The canonical URL is https://www.ywigs.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Store and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.ywigs.com/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://www.ywigs.com/collections/burmese-hair, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages without a meta description

    https://www.ywigs.com/pages/ywigs-black-friday-sale and https://www.ywigs.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.ywigs.com/pages/ywigs-black-friday-sale has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 8 pages that loaded have a <title>.

Best practices

3 to fixGoogle 5088
  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

  • 2 third-party cookies

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    80 of 85 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix72
  • 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.

  • No phone number on the homepage

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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.

  • About 1,679 words of copy

    The homepage carries about 1,679 words of visible text.

5 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us”, “Sign up and save” and “icon-email Subscribe”.

  • 4 short forms

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

  • Analytics in place

    Analytics detected: Mixpanel.

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 11 trackers load before any consent

    11

    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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 36 cookies set on arrival

    36

    Opening the homepage sets 36 cookies, 1 of them by other companies (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.

  • 50 other companies contacted

    Loading the homepage contacts 50 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 ywigs.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on ywigs.com, including 24 speed issues, 3 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