Website review, no card needed

thehumble.co logo

thehumble.co website review

Visit site (opens in a new tab)Reviewed 8 November 202633 issues · 81 checks

This review found 33 issues worth fixing on thehumble.co, 8 of them high impact, across 81 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.1 s1.6 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.1 s
May 23, 20262.0 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.8 s
Sep 5, 20261.9 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.8 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
152 ms108 msMay 16Oct 31147 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026121 ms
May 23, 2026119 ms
May 30, 2026119 ms
Jun 6, 2026113 ms
Jun 13, 2026113 ms
Jun 20, 2026113 ms
Jun 27, 2026114 ms
Jul 4, 2026120 ms
Jul 11, 2026123 ms
Jul 18, 2026123 ms
Jul 25, 2026123 ms
Aug 1, 2026124 ms
Aug 8, 2026127 ms
Aug 15, 2026129 ms
Aug 22, 2026129 ms
Aug 29, 2026129 ms
Sep 5, 2026129 ms
Sep 12, 2026129 ms
Sep 19, 2026130 ms
Sep 26, 2026136 ms
Oct 3, 2026136 ms
Oct 10, 2026138 ms
Oct 17, 2026142 ms
Oct 24, 2026143 ms
Oct 31, 2026147 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 thehumble.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thehumble.co at 0.7 s0.7 s
  2. thehumble.co at 1.4 s1.4 s
  3. thehumble.co at 2.0 s2.0 s
  4. thehumble.co at 2.7 s2.7 s
  5. thehumble.co at 3.4 s3.4 s
  6. thehumble.co at 4.1 s4.1 s
  7. thehumble.co at 4.8 s4.8 s
  8. thehumble.co at 5.5 s5.5 s

Speed

9 to fix73
  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 73

    73/100

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

  • Reduce unused JavaScript

    300 ms · 625 KiB

    About 625 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, selma.se and Shopify and others), adding 1.3 MB and 555 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 101 KiB

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

  • Main-thread work: 2.9 s

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

  • Klaviyo adds 211 ms

    211 ms

    Klaviyo costs a phone 211 ms of main-thread work and 524 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

    255 KiB

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

  • Shopify adds 83 ms

    83 ms

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

  • Improve image delivery

    222 KiB

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

  • 5 long tasks on the main thread

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

  • Duplicated JavaScript

    150 ms · 11 KiB

    11 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    30 KiB

    Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need.

  • Minify JavaScript

    21 KiB

    21 KiB could be saved by minifying JavaScript.

  • Minify CSS

    6 KiB

    6 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: 10 ms

    10 ms

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

Core Web Vitals

6 to fix100
  • 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.

  • Time to Interactive: 14.6 s

    14.6 s

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

  • Largest Contentful Paint: 5.9 s

    5.9 s

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

  • Tap response (INP) got 21% slower for real visitors

    +21%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Speed Index: 4.9 s

    4.9 s

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

8 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 165 ms

    165 ms

    Real visitors wait 165 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

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

  • Real-user TTFB: 715 ms

    715 ms

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

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

    -13%

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

  • Total Blocking Time: 162 ms

    162 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 3.3 MB in 266 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 266 requests on a phone: scripts 1.5 MB (95), other files 976 KiB (142) and images 501 KiB (16). Under 2 MB keeps phones on slow connections fast.

  • About 0.9 g of CO₂ per visit

    0.94 g

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

5 to fixGoogle 8392
  • 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.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • 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 (h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

2 to fixGoogle 8585
  • No H1 headline

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

  • Meta description is long (187 characters)

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

  • 39 internal links, 7 external

    The homepage links to 39 pages on thehumble.co and 7 external pages.

6 checks passed
  • Title: 45 characters

    Your title is a healthy 45 characters: “The Humble Co. | Gentle & Effective Oral Care”.

  • Canonical URL set

    The canonical URL is https://www.thehumble.co/.

  • 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://www.thehumble.co/sitemap.xml.

AI search readiness

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

  • llms.txt published

    The site publishes https://www.thehumble.co/llms.txt (4 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix71
  • 7 pages point its canonical at the homepage

    https://www.thehumble.co/products/bad-breath-kit, https://www.thehumble.co/products/whitneing-pen, https://www.thehumble.co/products/whitening-strips-aloe-vera, https://www.thehumble.co/products/the-whitening-kit, https://www.thehumble.co/products/stainless-steel-tounge-scraper and https://www.thehumble.co/products/humble-toothpaste-whitening-mint-75ml-cosmos-natural and 1 other declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 10 pages share 2 titles

    /, https://www.thehumble.co/products/bad-breath-kit, https://www.thehumble.co/products/whitneing-pen, https://www.thehumble.co/products/whitening-strips-aloe-vera, https://www.thehumble.co/products/the-whitening-kit and https://www.thehumble.co/products/stainless-steel-tounge-scraper and 2 others all use the title “The Humble Co. | Gentle & Effective Oral Care”, and 1 other title repeat too. 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://www.thehumble.co/collections/all-products, https://www.thehumble.co/collections/new-arrivals, https://www.thehumble.co/collections/best-sellers-v2, https://www.thehumble.co/collections/toothpaste, https://www.thehumble.co/collections/toothbrushes and https://www.thehumble.co/collections/kits-gift-sets and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages share a meta description

    https://www.thehumble.co/products/bad-breath-kit, https://www.thehumble.co/products/whitneing-pen, https://www.thehumble.co/products/whitening-strips-aloe-vera, https://www.thehumble.co/products/the-whitening-kit, https://www.thehumble.co/products/stainless-steel-tounge-scraper and https://www.thehumble.co/products/humble-toothpaste-whitening-mint-75ml-cosmos-natural and 1 other use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.thehumble.co/collections/all-products, https://www.thehumble.co/collections/new-arrivals, https://www.thehumble.co/collections/best-sellers-v2, https://www.thehumble.co/collections/toothpaste, https://www.thehumble.co/collections/toothbrushes and https://www.thehumble.co/collections/kits-gift-sets and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://www.thehumble.co/products/bad-breath-kit, https://www.thehumble.co/products/whitneing-pen, https://www.thehumble.co/products/whitening-strips-aloe-vera, https://www.thehumble.co/products/the-whitening-kit, https://www.thehumble.co/products/stainless-steel-tounge-scraper and https://www.thehumble.co/products/humble-toothpaste-whitening-mint-75ml-cosmos-natural 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 28 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.

  • 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

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    9 of 10 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix71
  • Thin social proof

    Social proof on the homepage: 40 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • Only about 31 words

    The homepage has only about 31 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop All”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “SHOP THE BETTER BREATH ROUTINE”, “Join” and “Contact us”.

  • 5 short forms

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (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.

  • 12 cookies set on arrival

    12

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 thehumble.co, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Shopify

Company

Headquarters
Stockholm

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 thehumble.co, including 15 speed issues, 2 SEO issues and 4 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