Website review, no card needed

107beauty.com logo

107beauty.com website review

Visit site (opens in a new tab)Reviewed 11 November 202633 issues · 86 checks

This review found 33 issues worth fixing on 107beauty.com, 11 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. 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
2.9 s2.2 sMay 23Nov 72.4 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.7 s
May 30, 20262.6 s
Jun 6, 20262.6 s
Jun 13, 20262.8 s
Jun 20, 20262.6 s
Jun 27, 20262.7 s
Jul 4, 20262.6 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.5 s
Aug 15, 20262.4 s
Aug 22, 20262.5 s
Aug 29, 20262.7 s
Sep 5, 20262.5 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.3 s
Nov 7, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
406 ms123 msMay 23Nov 7156 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026320 ms
May 30, 2026325 ms
Jun 6, 2026373 ms
Jun 13, 2026354 ms
Jun 20, 2026303 ms
Jun 27, 2026282 ms
Jul 4, 2026229 ms
Jul 11, 2026229 ms
Jul 18, 2026229 ms
Jul 25, 2026229 ms
Aug 1, 2026255 ms
Aug 8, 2026270 ms
Aug 15, 2026231 ms
Aug 22, 2026234 ms
Aug 29, 2026225 ms
Sep 5, 2026255 ms
Sep 12, 2026255 ms
Sep 19, 2026275 ms
Sep 26, 2026307 ms
Oct 3, 2026270 ms
Oct 10, 2026286 ms
Oct 17, 2026260 ms
Oct 24, 2026246 ms
Oct 31, 2026204 ms
Nov 7, 2026156 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 107beauty.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 107beauty.com at 0.5 s0.5 s
  2. 107beauty.com at 1.0 s1.0 s
  3. 107beauty.com at 1.5 s1.5 s
  4. 107beauty.com at 2.0 s2.0 s
  5. 107beauty.com at 2.5 s2.5 s
  6. 107beauty.com at 3.0 s3.0 s
  7. 107beauty.com at 3.5 s3.5 s
  8. 107beauty.com at 4.0 s4.0 s

Speed

7 to fix54
  • Use efficient cache lifetimes

    2.3 s · 339 KiB

    12 files are served with short cache lifetimes, so returning visitors download them again (339 KiB).

  • Reduce unused JavaScript

    1.6 s · 422 KiB

    About 422 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

  • Mobile performance score: 54

    54/100

    Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.

  • 4 long tasks on the main thread

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

  • Render-blocking requests

    750 ms

    9 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Google Tag Manager and Yotpo and others), adding 886 KiB and 527 ms of main-thread time.

  • Main-thread work: 3.4 s

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

  • Legacy JavaScript

    150 ms · 39 KiB

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

  • Improve image delivery

    116 KiB

    3 images could be 116 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    109 KiB

    About 109 KiB of CSS is downloaded but never applied on this page.

  • Font display

    50 ms

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

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

7 to fix50
  • 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: 10.0 s

    10.0 s

    Your largest element takes 10.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 11.2 s

    11.2 s

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

  • Speed Index: 7.1 s

    7.1 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Total Blocking Time: 517 ms

    517 ms

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

  • 16 images without width and height

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

6 checks passed
  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Tap response (INP) got 44% faster for real visitors

    -44%

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

  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

  • First Contentful Paint: 1.6 s

    1.6 s

    The first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.018

    0.018

    The layout barely moves while loading (CLS 0.018, good is under 0.1).

Images and page weight

1 to fix90
  • 1 image far larger than shown

    64 KiB

    1 image is downloaded at several times the size a phone draws it, for example US.png at 3,000 px wide, shown at 390 px. Resized copies would save about 64 KiB.

  • 4 images below the first screen load straight away

    4 images further down the page (153 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image in older formats

    1 image (34 KiB) is 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 0.5 g of CO₂ per visit

    0.46 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 54.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 checks passed
  • Page weight: 1.6 MB in 147 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 147 requests on a phone: scripts 953 KiB (56), images 410 KiB (36) and stylesheets 86 KiB (14). That is a lean page.

Accessibility

7 to fixGoogle 7890
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 2 text elements with low contrast

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

  • 3 images without alt text

    3 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

    Headings skip levels (h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 45 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: 45 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

3 to fixGoogle 8588
  • 7 H1 headlines

    There are 7 <h1> headlines (“”, “SCALP PURIFYING Microbiome Shampoo” and “BARRIER REPAIR Hydro Serum”). One clear main headline is easier for people and search engines.

  • Meta description is long (245 characters)

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

  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 63 internal links, 3 external

    The homepage links to 63 pages on 107beauty.com and 3 external pages.

6 checks passed
  • Title: 33 characters

    Your title is a healthy 33 characters: “107: Centuries-Old Beauty Secrets”.

  • Canonical URL set

    The canonical URL is https://107beauty.com/.

  • Structured data in place

    Structured data found: BreadcrumbList and LocalBusiness.

  • 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://107beauty.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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 9 pages without a meta description

    https://107beauty.com/collections/best-sellers, https://107beauty.com/collections/shop-all-essentials-skincare, https://107beauty.com/collections/hair-body, https://107beauty.com/collections/inner-wellness, https://107beauty.com/collections/sets-and-gifts and https://107beauty.com/pages/founder-story-1 and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://107beauty.com/pages/learn has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page slow to respond

    https://107beauty.com/collections/inner-wellness took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

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

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    17 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix69
  • 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 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.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • 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 309 words of copy

    The homepage carries about 309 words of visible text.

5 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Sign Up”, “Shop” and “Shop All”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

  • 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
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 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.

  • 29 other companies contacted

    Loading the homepage contacts 29 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 107beauty.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 8 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · hulkapps.com · goldendev.win · smile.io · privy.com · recovermycart.com · yotpo.com · stationmade.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

  • The footer still says © 2015.

Stack

Framework
jQuery
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 33 issues on 107beauty.com, including 14 speed issues, 3 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

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