Website review, no card needed
beautysociety.com website review
Visit site (opens in a new tab)Reviewed 24 October 202649 issues · 89 checks
This review found 49 issues worth fixing on beautysociety.com, 21 of them high impact, across 89 checks. The most urgent: improve image delivery. 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.0 s |
| May 9, 2026 | 2.0 s |
| May 16, 2026 | 1.9 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 137 ms |
| May 9, 2026 | 130 ms |
| May 16, 2026 | 120 ms |
| May 23, 2026 | 113 ms |
| May 30, 2026 | 105 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 104 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 105 ms |
| Aug 1, 2026 | 105 ms |
| Aug 8, 2026 | 105 ms |
| Aug 15, 2026 | 104 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 104 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 105 ms |
| Sep 19, 2026 | 105 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 104 ms |
| Oct 10, 2026 | 103 ms |
| Oct 17, 2026 | 103 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.3 s
2.6 s
3.9 s
5.2 s
6.5 s
7.8 s
9.1 s
10.4 s
Speed
Improve image delivery
9.5 s · 11.2 MB17 images could be 11.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.5 s faster on a phone.
Render-blocking requests
5.2 s72 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.2 s.
Reduce unused JavaScript
2.3 s · 975 KiBAbout 975 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Main-thread work: 11.6 s
A phone's processor spends 11.6 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 10
10/100Your mobile performance score is 10 (desktop: 33). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,189 HTML elements
The page has 3,189 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 20.2 MB39 files are served with short cache lifetimes, so returning visitors download them again (20.2 MB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 2.3 s. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (JSDelivr CDN, Google CDN and Cookiebot and others), adding 1.6 MB and 1.6 s of main-thread time.
JSDelivr CDN adds 833 ms
833 msJSDelivr CDN costs a phone 833 ms of main-thread work and 45 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.
Minify JavaScript
600 ms · 51 KiB51 KiB could be saved by minifying JavaScript.
Google CDN adds 362 ms
362 msGoogle CDN costs a phone 362 ms of main-thread work and 474 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.
Reduce unused CSS
300 ms · 104 KiBAbout 104 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.
Legacy JavaScript
300 ms · 17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Other Google APIs/SDKs adds 42 ms
42 msOther Google APIs/SDKs costs a phone 42 ms of main-thread work and 503 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 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: 9 ms
9 msYour server sent the HTML in 9 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.
First Contentful Paint: 9.9 s
9.9 sThe first text or image appears after 9.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 40.1 s
40.1 sYour largest element takes 40.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 17.0 s
17.0 sVisually, the page fills in at 17.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 41.4 s
41.4 sThe page becomes fully interactive after 41.4 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.922
0.922The layout shifts by 0.922 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 879 ms
879 msScripts block taps and scrolling for 879 ms in total while the page loads. Good is under 200 ms.
Real-user TTFB: 801 ms
801 msReal visitors wait 801 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 123 ms
123 msReal visitors wait 123 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 137 ms to 103 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 27.1 MB in 245 requests
27.1 MBYour homepage downloads 27.1 MB in 245 requests on a phone: images 23.9 MB (45), scripts 1.9 MB (114) and other files 579 KiB (40). Under 2 MB keeps phones on slow connections fast.
7 images far larger than shown
4.2 MB7 images are downloaded at several times the size a phone draws them, for example beauty-society-retro-lip-oil(2).jpg at 12,500 px wide, shown at 60 px. Resized copies would save about 4.2 MB.
1 image over 500 KB
beauty-society-retro-lip-oil(2).jpg weighs 3.4 MB. On a phone connection a single image that size takes seconds.
8 images below the first screen load straight away
8 images further down the page (4.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
5 images in older formats
5 images (4.0 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.
About 7.7 g of CO₂ per visit
7.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.67 g of CO₂e: 920.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
31 text elements with low contrast
31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (33 elements)
All page content should be contained by landmarks: 33 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.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
15 H1 headlines
There are 15 <h1> headlines (“Time Lapse”, “Time Lapse” and “Iconic”). One clear main headline is easier for people and search engines.
18 links crawlers can't follow
18 links have no real href, so search engines can't follow them.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
118 internal links, 10 external
The homepage links to 118 pages on beautysociety.com and 10 external pages.
7 checks passed
Meta description: 114 characters
Your meta description is 114 characters: “Discover the Highest Performing Anti-Aging Ingredients in Skincare and Cosmetics from a company with a conscience.”.
Title: 55 characters
Your title is a healthy 55 characters: “Discover your best Skincare Routine with Beauty Society”.
Canonical URL set
The canonical URL is https://beautysociety.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://beautysociety.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://beautysociety.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.
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.
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 (644 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://beautysociety.com/viewcart is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages share a title
https://beautysociety.com/order, https://beautysociety.com/order/All-products and https://beautysociety.com/order/All-Products all use the title “Shop - Beauty Society”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://beautysociety.com/viewcart, https://beautysociety.com/skin-quiz, https://beautysociety.com/skincare-regimens, https://beautysociety.com/color-matching, https://beautysociety.com/product-of-the-month and https://beautysociety.com/subscription-savings-program and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages share a meta description
https://beautysociety.com/order, https://beautysociety.com/order/All-products and https://beautysociety.com/order/All-Products use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://beautysociety.com/order/All-products, whose canonical is https://beautysociety.com/order. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
7 pages without an H1
https://beautysociety.com/viewcart, https://beautysociety.com/order, https://beautysociety.com/order/All-products, https://beautysociety.com/skin-quiz, https://beautysociety.com/skincare-regimens and https://beautysociety.com/color-matching and 1 other have 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 53 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
25 small tap targets
25 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
About 638 words of copy
The homepage carries about 638 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LEARN MORE”.
17 calls to action
The homepage has 17 calls to action, for example “Shop”, “Join Now” and “Why Join”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Hotjar and PostHog.
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
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
4 cookies set on arrival
4Opening the homepage sets 4 cookies (measured from a US location before any click).
14 other companies contacted
Loading the homepage contacts 14 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 beautysociety.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager | Hotjar | PostHog
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 beautysociety.com, including 23 speed issues, 3 SEO issues 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.