Website review, no card needed
incommonbeauty.com website review
Visit site (opens in a new tab)Reviewed 9 November 202642 issues · 89 checks
This review found 42 issues worth fixing on incommonbeauty.com, 16 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
72C- #96,977 of 125,402 reviewed websitesbeats 19%
- #59,539 of 70,179 online storesbeats 12%
- #55,411 of 63,759 Shopify storesbeats 11%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.3 s |
| Nov 7, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 113 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 119 ms |
| Jun 20, 2026 | 122 ms |
| Jun 27, 2026 | 133 ms |
| Jul 4, 2026 | 136 ms |
| Jul 11, 2026 | 130 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 128 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 121 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 137 ms |
| Aug 29, 2026 | 138 ms |
| Sep 5, 2026 | 144 ms |
| Sep 12, 2026 | 148 ms |
| Sep 19, 2026 | 150 ms |
| Sep 26, 2026 | 140 ms |
| Oct 3, 2026 | 137 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 128 ms |
| Oct 24, 2026 | 129 ms |
| Oct 31, 2026 | 138 ms |
| Nov 7, 2026 | 140 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.5 s
0.9 s
1.3 s
1.8 s
2.2 s
2.7 s
3.1 s
3.6 s
Speed
Reduce unused JavaScript
2.1 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Use efficient cache lifetimes
1.0 s · 1.3 MB41 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).
Mobile performance score: 45
45/100Your 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.8 s
A phone's processor spends 6.8 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Yotpo, Google Tag Manager and Hotjar and others), adding 3.6 MB and 1.8 s of main-thread time.
Reduce unused CSS
750 ms · 157 KiBAbout 157 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Render-blocking requests
700 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Improve image delivery
675 KiB3 images could be 675 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Yotpo adds 372 ms
372 msYotpo costs a phone 372 ms of main-thread work and 627 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.
Google Tag Manager adds 273 ms
273 msGoogle Tag Manager costs a phone 273 ms of main-thread work and 486 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.
rebuyengine.com adds 239 ms
239 msrebuyengine.com costs a phone 239 ms of main-thread work and 670 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.
Klaviyo adds 232 ms
232 msKlaviyo costs a phone 232 ms of main-thread work and 540 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.
Hotjar adds 258 ms
258 msHotjar costs a phone 258 ms of main-thread work and 65 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 231 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 16 KiB16 KiB could be saved by minifying JavaScript.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
89 KiBPolyfills for old browsers add 89 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
50 ms · 6 KiB6 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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: 8 ms
8 msYour server sent the HTML in 8 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.27
0.27For real visitors the layout shifts by 0.27 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 13.7 s
13.7 sYour largest element takes 13.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 34.5 s
34.5 sThe page becomes fully interactive after 34.5 s. Good is under 3.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 861 ms
861 msScripts block taps and scrolling for 861 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 113 ms to 140 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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: 140 ms
140 msReal visitors wait 140 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 763 ms
763 msReal visitors wait 763 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.055
0.055The layout barely moves while loading (CLS 0.055, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 6.4 MB in 361 requests
6.4 MBYour homepage downloads 6.4 MB in 361 requests on a phone: scripts 3.3 MB (140), images 1.6 MB (38) and other files 748 KiB (134). Under 2 MB keeps phones on slow connections fast.
About 1.8 g of CO₂ per visit
1.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.81 g of CO₂e: 216.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
[role="img"] and [role="image"] elements must have alternative text (5 elements)
[role="img"] and [role="image"] elements must have alternative text: 5 elements on the page fail this check, rated serious 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.
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.
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.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 7 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 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “IN COMMON Beauty | Luxury Haircare Inspired by Riawna Capri& Nikki Lee”.
4 H1 headlines
There are 4 <h1> headlines (“MEET MAGIC TREATMENT”, “WORKS LIKE MAGIC IN 1 USE*” and “LEVEL-UP YOUR CONDITIONER”). One clear main headline is easier for people and search engines.
Meta description is long (218 characters)
Your meta description is 218 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.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
61 internal links, 15 external
The homepage links to 61 pages on incommonbeauty.com and 15 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.incommonbeauty.com/.
Structured data in place
Structured data found: Organization and WebSite.
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.incommonbeauty.com/sitemap.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (798 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.incommonbeauty.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://www.incommonbeauty.com/pages/howitworksleavein and https://www.incommonbeauty.com/pages/hair-quiz, which answer with an error. Visitors hit a dead end and search engines drop them.
1 page without a meta description
https://www.incommonbeauty.com/pages/rewards-yotpo has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://www.incommonbeauty.com/collections/shop-all, https://www.incommonbeauty.com/collections/treatment and https://www.incommonbeauty.com/collections/boosters use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
5 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.
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 13 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=46fb8f5a-a15e-400e-97ee-27c2ccac3709&referrer=&landingpage=https%3A%2F%2Fwww.incommonbeauty.com%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%2.
5 small tap targets
5 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 23 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
A 11-field form
Your longest form asks for 11 fields (0 required). Every extra field lowers completion.
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 581 words of copy
The homepage carries about 581 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
17 calls to action
The homepage has 17 calls to action, for example “SHOP”, “SHOP ALL” and “JOIN THE PRO FAMILY”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and Hotjar.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 4 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.
37 cookies set on arrival
37Opening the homepage sets 37 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.
56 other companies contacted
Loading the homepage contacts 56 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 incommonbeauty.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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Attentive · Yotpo Product Reviews · Klaviyo Email Marketing Sms · Yotpo Loyalty Rewards · Freegifts · rakuten.com · shareasale.com · b-cdn.net · rechargecdn.com · dailykarma.io · bogos.io · socialsnowball.io · attn.tv · 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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar
- Hosting
- Cloudflare
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 incommonbeauty.com, including 21 speed issues, 5 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.