Website review, no card needed

thefacehaus.com logo

thefacehaus.com website review

Visit site (opens in a new tab)Reviewed 21 October 202639 issues · 85 checks

This review found 39 issues worth fixing on thefacehaus.com, 18 of them high impact, across 85 checks. The most urgent: render-blocking requests. 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.5 s1.3 sMay 2Oct 172.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.4 s
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.5 s
Jul 4, 20261.7 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20262.1 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Oct 10, 20262.1 s
Oct 17, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
74 ms63 msMay 9Oct 1769 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202671 ms
May 23, 202670 ms
May 30, 202669 ms
Jun 6, 202664 ms
Jun 13, 202670 ms
Jun 20, 202670 ms
Jun 27, 202671 ms
Jul 18, 202670 ms
Jul 25, 202668 ms
Aug 1, 202669 ms
Aug 8, 202665 ms
Aug 15, 202666 ms
Aug 22, 202665 ms
Aug 29, 202665 ms
Sep 5, 202673 ms
Sep 12, 202670 ms
Sep 19, 202671 ms
Sep 26, 202666 ms
Oct 3, 202666 ms
Oct 10, 202666 ms
Oct 17, 202669 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 thefacehaus.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thefacehaus.com at 0.4 s0.4 s
  2. thefacehaus.com at 0.8 s0.8 s
  3. thefacehaus.com at 1.1 s1.1 s
  4. thefacehaus.com at 1.5 s1.5 s
  5. thefacehaus.com at 1.9 s1.9 s
  6. thefacehaus.com at 2.3 s2.3 s
  7. thefacehaus.com at 2.6 s2.6 s
  8. thefacehaus.com at 3.0 s3.0 s

Speed

11 to fix35
  • Render-blocking requests

    2.1 s

    11 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.

  • Reduce unused JavaScript

    1.6 s · 200 KiB

    About 200 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: 35

    35/100

    Your mobile performance score is 35 (desktop: 65). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 3,885 HTML elements

    The page has 3,885 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    638 KiB

    20 images could be 638 KiB 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 (Cookiebot, userway.org and Google CDN and others), adding 1.3 MB and 375 ms of main-thread time.

  • Minify JavaScript

    300 ms · 39 KiB

    39 KiB could be saved by minifying JavaScript.

  • Reduce unused CSS

    300 ms · 33 KiB

    About 33 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.

  • Cookiebot adds 268 ms

    268 ms

    Cookiebot costs a phone 268 ms of main-thread work and 255 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.

  • Main-thread work: 2.5 s

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

  • Shopify adds 24 ms

    24 ms

    Shopify costs a phone 24 ms of main-thread work and 876 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.

  • Use efficient cache lifetimes

    250 ms · 43 KiB

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

  • 5 long tasks on the main thread

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

  • Legacy JavaScript

    50 ms · 11 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Phones get a much slower page than desktops

    Desktop scores 65 but mobile only 35. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 28 ms

    28 ms

    Your server sent the HTML in 28 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix0
  • 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: 1.49

    1.49

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

  • Largest Contentful Paint: 13.9 s

    13.9 s

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

  • Time to Interactive: 15.1 s

    15.1 s

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

  • Cumulative Layout Shift: 0.576

    0.576

    The layout shifts by 0.576 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 4.6 s

    4.6 s

    The first text or image appears after 4.6 s on a phone. Good is under 1.8 s.

  • Speed Index: 8.3 s

    8.3 s

    Visually, the page fills in at 8.3 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.

  • Largest content (LCP) got 55% slower for real visitors

    +55%

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

  • 13 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -4%

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

3 checks passed
  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 420 ms

    420 ms

    Real visitors wait 420 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 111 ms

    111 ms

    Scripts block the page for only 111 ms while loading. Good is under 200 ms.

Images and page weight

1 to fix85
  • Page weight: 3.5 MB in 290 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 290 requests on a phone: images 1.6 MB (101), scripts 929 KiB (73) and other files 805 KiB (101). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.99 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 119.0 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

7 to fixGoogle 8088
  • Required ARIA attributes must be provided (2 elements)

    Required ARIA attributes must be provided: 2 elements on the page fail this check, rated critical by axe-core.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 57 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • Links must have discernible text (20 elements)

    Links must have discernible text: 20 elements on the page fail this check, rated serious by axe-core.

  • All page content should be contained by landmarks (41 elements)

    All page content should be contained by landmarks: 41 elements on the page fail this check, rated moderate by axe-core.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 125 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10085
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (302 characters)

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

  • 132 internal links, 15 external

    The homepage links to 132 pages on thefacehaus.com and 15 external pages.

6 checks passed
  • Title: 38 characters

    Your title is a healthy 38 characters: “The Face Haus | Facials for the People”.

  • Canonical URL set

    The canonical URL is https://thefacehaus.com/.

  • Structured data in place

    Structured data found: Organization 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://thefacehaus.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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 (3,348 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://thefacehaus.com/collections/shop-body, https://thefacehaus.com/collections/shop-bundles, https://thefacehaus.com/collections/shop-cleansers, https://thefacehaus.com/collections/shop-creams, https://thefacehaus.com/collections/shop-exfoliators and https://thefacehaus.com/collections/shop-eye-lip-care and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://thefacehaus.com/collections/shop-body, https://thefacehaus.com/collections/shop-bundles, https://thefacehaus.com/collections/shop-cleansers, https://thefacehaus.com/collections/shop-creams, https://thefacehaus.com/collections/shop-exfoliators and https://thefacehaus.com/collections/shop-eye-lip-care and 5 others 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 60 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

3 to fixGoogle 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://thefacehaus.com/.

  • 77 distorted images

    77 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 30 small tap targets

    30 of 63 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 789 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BOOK NOW”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “SHOP ACCOUNT”, “SHOP” and “SUBSCRIBE”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 cookies (measured from a US location before any click).

  • 13 other companies contacted

    Loading the homepage contacts 13 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 thefacehaus.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2020.

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on thefacehaus.com, including 21 speed issues, 2 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

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