Website review, no card needed
sunberhair.com website review
Visit site (opens in a new tab)Reviewed 4 November 202645 issues · 89 checks
This review found 45 issues worth fixing on sunberhair.com, 21 of them high impact, across 89 checks. The most urgent: page weight: 39.1 MB in 230 requests. 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
67D- #105,649 of 117,615 reviewed websitesbeats 9%
- #63,312 of 66,923 online storesbeats 4%
- #58,262 of 61,018 Shopify storesbeats 4%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 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.5 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 241 ms |
| May 23, 2026 | 251 ms |
| May 30, 2026 | 259 ms |
| Jun 6, 2026 | 270 ms |
| Jun 13, 2026 | 272 ms |
| Jun 20, 2026 | 280 ms |
| Jun 27, 2026 | 288 ms |
| Jul 4, 2026 | 293 ms |
| Jul 11, 2026 | 281 ms |
| Jul 18, 2026 | 280 ms |
| Jul 25, 2026 | 274 ms |
| Aug 1, 2026 | 271 ms |
| Aug 8, 2026 | 273 ms |
| Aug 15, 2026 | 270 ms |
| Aug 22, 2026 | 274 ms |
| Aug 29, 2026 | 278 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
1.2 s
2.4 s
3.6 s
4.8 s
6.0 s
7.2 s
8.5 s
9.7 s
Speed
Reduce unused JavaScript
1.3 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 817 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.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.4 s
A phone's processor spends 6.4 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
31.9 MB39 images could be 31.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Stripe and Facebook and others), adding 1.7 MB and 2.2 s of main-thread time.
Use efficient cache lifetimes
300 ms · 642 KiB24 files are served with short cache lifetimes, so returning visitors download them again (642 KiB).
Avoid multiple page redirects
780 msThe page goes through 1 redirect before it starts loading, costing about 780 ms. Link and advertise the final URL directly.
Stripe adds 478 ms
478 msStripe costs a phone 478 ms of main-thread work and 319 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.
Document request latency
300 msThe HTML itself could arrive about 300 ms sooner: redirects, a slow server response or missing compression delay everything after it.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 270 ms. During a long task the page ignores taps.
2,638 HTML elements
The page has 2,638 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 57 KiBPolyfills for old browsers add 57 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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: 3 ms
3 msYour server sent the HTML in 3 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.
Real-user CLS: 0.83
0.83For real visitors the layout shifts by 0.83 (75th percentile). Good is under 0.1.
Time to Interactive: 21.9 s
21.9 sThe page becomes fully interactive after 21.9 s. Good is under 3.8 s.
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “20261104-BF-Ready-To-Shop-friday-allwig69off_m1”.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.2 s
7.2 sVisually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 s.
Real-user INP: 320 ms
320 msReal visitors wait 320 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 241 ms to 278 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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 2.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 39.1 MB in 230 requests
39.1 MBYour homepage downloads 39.1 MB in 230 requests on a phone: images 36.8 MB (94), scripts 2.1 MB (48) and other files 111 KiB (79). Under 2 MB keeps phones on slow connections fast.
15 images over 500 KB
15 images weigh 33.8 MB together. On a phone connection a single image that size takes seconds.
29 images far larger than shown
17.5 MB29 images are downloaded at several times the size a phone draws them, for example a7aff04848ce7be776fc120ac75eb73d.gif at 780 px wide, shown at 177 px. Resized copies would save about 17.5 MB.
22 images in older formats
22 images (34.5 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.
24 images below the first screen load straight away
24 images further down the page (26.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 11.1 g of CO₂ per visit
11.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 11.08 g of CO₂e: 1330.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
32 buttons without a name
32 buttons have no accessible name, so screen readers announce just “button”.
51 text elements with low contrast
51 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (166 elements)
All page content should be contained by landmarks: 166 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.
1 checks passed
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Canonical points to another host
Your canonical URL points to m.sunberhair.com, not sunberhair.com, so Google may credit that host instead.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
23 internal links, 4 external
The homepage links to 23 pages on sunberhair.com and 4 external pages.
7 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Shop glueless and HD lace wigs, bundles, and more at SunberHair. Enjoy up to $300 off in first-order + free gifts, plus…”.
One H1 headline
Your main headline reads: “sunber”.
Title: 61 characters
Your title is a healthy 61 characters: “Human Hair Glueless Wigs and Weave Hair Bundles | Sunber Hair”.
Structured data in place
Structured data found: OnlineStore.
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.sunberhair.com/sitemap/sitemap.xml.
AI search readiness
Most text only appears after JavaScript runs
7%A phone browser shows 1,088 words, but the HTML your server sends has only 78. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
No llms.txt
There is no https://www.sunberhair.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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.
Other pages
7 pages share a title
https://www.sunberhair.com/about-us, https://www.sunberhair.com/accessibility, https://www.sunberhair.com/order-tracking, https://www.sunberhair.com/return-policy, https://www.sunberhair.com/privacy-policy and https://www.sunberhair.com/terms-conditions and 1 other all use the title “Sunberhair”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.sunberhair.com/activity/ig-70-off-flash-sale.html has no meta description, so Google writes the search snippet from whatever text it finds.
7 pages share a meta description
https://www.sunberhair.com/about-us, https://www.sunberhair.com/accessibility, https://www.sunberhair.com/order-tracking, https://www.sunberhair.com/return-policy, https://www.sunberhair.com/privacy-policy and https://www.sunberhair.com/terms-conditions and 1 other use the same meta description. A description written for each page earns more clicks.
7 pages without an H1
https://www.sunberhair.com/customer, https://www.sunberhair.com/activity/ig-70-off-flash-sale.html, https://www.sunberhair.com/about-us, https://www.sunberhair.com/activity/coupon-code.html, https://www.sunberhair.com/activity/wholesale and https://www.sunberhair.com/order-tracking and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.sunberhair.com/customer, https://www.sunberhair.com/accessibility and https://www.sunberhair.com/order-tracking 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.
4 pages slow to respond
https://www.sunberhair.com/return-policy, https://www.sunberhair.com/privacy-policy, https://www.sunberhair.com/terms-conditions and https://www.sunberhair.com/shipping-payment took over 3 s to send their HTML from our server.
14 internal pages checked
We fetched 14 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 14 pages we checked loaded without an error.
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.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
9 broken images
9 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=16001201&Ver=2&mid=b12bf7cd-679e-4ff3-8610-ffa7da0c6b7b&bo=1&sid=81e30a10d89f11f18ec25d1f8fcc171e&vid=81e31e30d89f11f1b5fd9ba2e23f0184&vids=1&msclkid=N&pi=918639831&lg.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'v')”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
32 of 38 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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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,088 words of copy
The homepage carries about 1,088 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Track Order”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads 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.
30 cookies set on arrival
30Opening the homepage sets 30 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.
32 other companies contacted
Loading the homepage contacts 32 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 sunberhair.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- E-commerce
- 1ClickPopup;Shopify;Shopify Plus
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on sunberhair.com, including 20 speed issues, 1 SEO issue and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.