Website review, no card needed
dooreshair.com website review
Visit site (opens in a new tab)Reviewed 8 November 202642 issues · 91 checks
This review found 42 issues worth fixing on dooreshair.com, 15 of them high impact, across 91 checks. The most urgent: main-thread work: 6.7 s. 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
79C- #55,689 of 124,903 reviewed websitesbeats 50%
- #36,546 of 70,062 online storesbeats 42%
- #35,002 of 63,677 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.2 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.3 s |
| Aug 8, 2026 | 1.3 s |
| Aug 15, 2026 | 1.3 s |
| Aug 22, 2026 | 1.3 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 121 ms |
| May 23, 2026 | 120 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 112 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 119 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 125 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 125 ms |
| Aug 29, 2026 | 128 ms |
| Sep 5, 2026 | 127 ms |
| Sep 12, 2026 | 128 ms |
| Sep 19, 2026 | 129 ms |
| Sep 26, 2026 | 129 ms |
| Oct 3, 2026 | 137 ms |
| Oct 10, 2026 | 142 ms |
| Oct 17, 2026 | 137 ms |
| Oct 24, 2026 | 127 ms |
| Oct 31, 2026 | 117 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
Main-thread work: 6.7 s
A phone's processor spends 6.7 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,732 HTML elements
The page has 3,732 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, quickcep.com and Yotpo and others), adding 2.3 MB and 1.4 s of main-thread time.
Reduce unused JavaScript
300 ms · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Improve image delivery
300 ms · 1.1 MB21 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
1.1 MB23 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Mobile performance score: 60
60/100Your mobile performance score is 60. Pages that score under 90 lose visitors before the first paint.
Shopify adds 547 ms
547 msShopify costs a phone 547 ms of main-thread work and 743 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.
Render-blocking requests
600 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Reduce unused CSS
300 ms · 95 KiBAbout 95 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
quickcep.com adds 185 ms
185 msquickcep.com costs a phone 185 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.
xcottons.com adds 152 ms
152 msxcottons.com costs a phone 152 ms of main-thread work and 343 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 233 ms. During a long task the page ignores taps.
Minify CSS
150 ms · 4 KiB4 KiB could be saved by minifying CSS.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
45 KiBPolyfills for old browsers add 45 KiB JavaScript that modern phones do not need.
Minify JavaScript
36 KiB36 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
8 KiB8 KiB JavaScript is shipped twice across bundles.
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: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 24.4 s
24.4 sThe page becomes fully interactive after 24.4 s. Good is under 3.8 s.
Largest Contentful Paint: 5.6 s
5.6 sYour largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 490 ms
490 msScripts block taps and scrolling for 490 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 121 ms to 117 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 103 ms
103 msReal visitors wait 103 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 739 ms
739 msReal visitors wait 739 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.3 s to 1.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.
Cumulative Layout Shift: 0.053
0.053The layout barely moves while loading (CLS 0.053, good is under 0.1).
Images and page weight
Page weight: 6.5 MB in 417 requests
6.5 MBYour homepage downloads 6.5 MB in 417 requests on a phone: scripts 2.6 MB (90), images 2.2 MB (32) and other files 1.3 MB (274). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
5_2758d2a4-9b35-4175-b12b-007c2d32572a.jpg 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 1.8 g of CO₂ per visit
1.84 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.84 g of CO₂e: 221.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
36 text elements with low contrast
36 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
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.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
44 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: 44 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (16 characters)
Your title is only 16 characters: “American Express”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
173 internal links, 6 external
The homepage links to 173 pages on dooreshair.com and 6 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.dooreshair.com/.
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.dooreshair.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.
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 (1,014 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.dooreshair.com/llms.txt (3 KiB, 28 links), a plain-text guide to the site for AI tools.
Other pages
12 pages without a title
https://www.dooreshair.com/collections/shop-all, https://www.dooreshair.com/collections/new-arrival, https://www.dooreshair.com/collections/best-seller, https://www.dooreshair.com/collections/clip-ins, https://www.dooreshair.com/collections/7-pcs-clip-ins and https://www.dooreshair.com/collections/scalp-hair-fill-ins and 6 others have no <title>, so Google invents the link text in results.
4 pages share a title
/, https://www.dooreshair.com/pages/color-match, https://www.dooreshair.com/collections/150g-clip-ins and https://www.dooreshair.com/collections/ultra-seamless-clip-ins all use the title “American Express”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://www.dooreshair.com/collections/shop-all, https://www.dooreshair.com/collections/new-arrival, https://www.dooreshair.com/collections/best-seller, https://www.dooreshair.com/pages/color-match, https://www.dooreshair.com/collections/clip-ins and https://www.dooreshair.com/collections/7-pcs-clip-ins and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://www.dooreshair.com/collections/shop-all, https://www.dooreshair.com/collections/best-seller, https://www.dooreshair.com/pages/color-match, https://www.dooreshair.com/collections/clip-ins, https://www.dooreshair.com/collections/150g-clip-ins and https://www.dooreshair.com/collections/all-tape-ins and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages with very little text
https://www.dooreshair.com/collections/shop-all, https://www.dooreshair.com/collections/best-seller, https://www.dooreshair.com/collections/clip-ins, https://www.dooreshair.com/collections/all-tape-ins, https://www.dooreshair.com/collections/tape-ins and https://www.dooreshair.com/collections/weft-hair-extensions-1 and 1 other 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 84 found) and read each the way a search engine does.
3 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
40 of 43 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.
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 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 718 words of copy
The homepage carries about 718 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
36 calls to action
The homepage has 36 calls to action, for example “SHOP BY TYPE”, “Order Tracking” and “Contact Us”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Klaviyo (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
30 other companies contacted
Loading the homepage contacts 30 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 dooreshair.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 23 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Nospy · Avada Seo Suite · Frequently Bought · Xcotton Guard · Starapps Variant Image · Judge Me Reviews · Zoorix Cross Sell · Tolstoy · Klaviyo Email Marketing Sms · Swatch King · Variant Title King · Selleasy · Ecomsend · Rivyo Product Review · yotpo.com · jsdelivr.net · routeapp.io · cloudfront.net · revy.io · mambasms.com · hextom.com · luckyorange.com · quickcep.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
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on dooreshair.com, including 16 speed issues, 4 SEO issues and 3 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.