Website review, no card needed

mchel.co logo

mchel.co website review

Visit site (opens in a new tab)Reviewed 17 November 202623 issues · 67 checks

This review found 23 issues worth fixing on mchel.co, 8 of them high impact, across 67 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
3.3 s2.0 sMay 30Oct 32.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jul 18, 20262.6 s
Jul 25, 20262.3 s
Aug 1, 20262.2 s
Aug 8, 20262.2 s
Aug 15, 20262.2 s
Aug 22, 20262.2 s
Sep 26, 20262.2 s
Oct 3, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
175 ms124 msMay 30Aug 15149 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026130 ms
Jun 6, 2026145 ms
Jun 13, 2026162 ms
Jun 20, 2026169 ms
Jul 11, 2026137 ms
Jul 18, 2026137 ms
Jul 25, 2026148 ms
Aug 1, 2026146 ms
Aug 8, 2026146 ms
Aug 15, 2026149 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 mchel.co (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mchel.co at 0.5 s0.5 s
  2. mchel.co at 1.0 s1.0 s
  3. mchel.co at 1.5 s1.5 s
  4. mchel.co at 2.0 s2.0 s
  5. mchel.co at 2.5 s2.5 s
  6. mchel.co at 3.0 s3.0 s
  7. mchel.co at 3.4 s3.4 s
  8. mchel.co at 3.9 s3.9 s

Speed

6 to fix70
  • Render-blocking requests

    1.6 s

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

  • Use efficient cache lifetimes

    1.1 s · 232 KiB

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

  • Reduce unused JavaScript

    930 ms · 244 KiB

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

  • Mobile performance score: 70

    70/100

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

  • Reduce unused CSS

    300 ms · 40 KiB

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

  • Google Tag Manager adds 269 ms

    269 ms

    Google Tag Manager costs a phone 269 ms of main-thread work and 353 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and bayengage.com and others), adding 677 KiB and 426 ms of main-thread time.

  • Legacy JavaScript

    150 ms · 25 KiB

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

  • 7 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Improve image delivery

    15 KiB

    1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    6 KiB

    6 KiB could be saved by minifying JavaScript.

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

    2 KiB

    2 KiB could be saved by minifying CSS.

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 559 ms of it running JavaScript. That is comfortably low.

  • Server response: 31 ms

    31 ms

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

Core Web Vitals

4 to fix69
  • Largest Contentful Paint: 6.5 s

    6.5 s

    Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Double Day After™ Brush Bundle”.

  • Time to Interactive: 7.8 s

    7.8 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • Tap response (INP) held steady for real visitors

    +7%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

3 checks passed
  • Largest content (LCP) got 24% faster for real visitors

    -24%

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

  • Total Blocking Time: 98 ms

    98 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

100
  • About 0.3 g of CO₂ per visit

    0.33 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.33 g of CO₂e: 40.0 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.2 MB in 69 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 69 requests on a phone: scripts 824 KiB (37), images 110 KiB (9) and fonts 90 KiB (3). That is a lean page.

Accessibility

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 9 automated accessibility rules passed

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

SEO

3 to fixGoogle 10078
  • No H1 headline

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

  • Title is short (15 characters)

    Your title is only 15 characters: “m'Chel Haircare”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (300 characters)

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 49 internal links, 2 external

    The homepage links to 49 pages on mchel.co and 2 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://mchel.co/.

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

AI search readiness

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

    Your Organization JSON-LD is missing sameAs (social profiles), 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.

  • No llms.txt

    There is no https://mchel.co/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.

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

Other pages

2 to fix93
  • 1 page without a meta description

    https://mchel.co/shop has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://mchel.co/products/double-day-after-brush-bundle and https://mchel.co/products/day-after-brush-refill-bundle use the same meta description. A description written for each page earns more clicks.

  • 1 page with very little text

    https://mchel.co/contact has 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 20 found) and read each the way a search engine does.

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

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

Best practices

1 to fixGoogle 10092
  • 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 429 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 33 words

    The homepage has only about 33 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.

4 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Shop All”, “Contact” and “Shop the Day After™ Brush”.

  • 3 short forms

    3 short forms (4 fields 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 2 email links.

Privacy and tracking

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

1 checks passed
  • 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 mchel.co, 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
E-commerce
WooCommerce
Analytics
Google Analytics
Hosting
WordPress.com

Company

Headquarters
San Francisco

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on mchel.co, including 10 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