Website review, no card needed

chrismcmillan.com logo

chrismcmillan.com website review

Visit site (opens in a new tab)Reviewed 6 November 202643 issues · 82 checks

This review found 43 issues worth fixing on chrismcmillan.com, 15 of them high impact, across 82 checks. The most urgent: page weight: 28.2 MB in 325 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
1.4 s1.2 sMay 16Oct 311.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.3 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.4 s
Oct 10, 20261.3 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Oct 31, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
213 ms145 msMay 16Oct 31192 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026176 ms
May 23, 2026188 ms
May 30, 2026196 ms
Jun 6, 2026205 ms
Jun 13, 2026203 ms
Jun 20, 2026177 ms
Jun 27, 2026172 ms
Jul 4, 2026169 ms
Jul 11, 2026163 ms
Jul 18, 2026155 ms
Jul 25, 2026153 ms
Aug 1, 2026153 ms
Aug 8, 2026153 ms
Aug 15, 2026170 ms
Aug 22, 2026182 ms
Aug 29, 2026191 ms
Sep 5, 2026194 ms
Sep 12, 2026189 ms
Sep 19, 2026194 ms
Sep 26, 2026195 ms
Oct 3, 2026195 ms
Oct 10, 2026196 ms
Oct 17, 2026184 ms
Oct 24, 2026180 ms
Oct 31, 2026192 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 chrismcmillan.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. chrismcmillan.com at 1.0 s1.0 s
  2. chrismcmillan.com at 1.9 s1.9 s
  3. chrismcmillan.com at 2.9 s2.9 s
  4. chrismcmillan.com at 3.9 s3.9 s
  5. chrismcmillan.com at 4.8 s4.8 s
  6. chrismcmillan.com at 5.8 s5.8 s
  7. chrismcmillan.com at 6.8 s6.8 s
  8. chrismcmillan.com at 7.8 s7.8 s

Speed

12 to fix48
  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 48

    48/100

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

  • Main-thread work: 6.7 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, TikTok and Klaviyo and others), adding 2.0 MB and 1.9 s of main-thread time.

  • Improve image delivery

    912 KiB

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

  • Reduce unused JavaScript

    891 KiB

    About 891 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 570 ms

    570 ms

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

    50 ms · 385 KiB

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

  • Klaviyo adds 293 ms

    293 ms

    Klaviyo costs a phone 293 ms of main-thread work and 391 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.

  • TikTok adds 313 ms

    313 ms

    TikTok costs a phone 313 ms of main-thread work and 169 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.

  • Facebook adds 292 ms

    292 ms

    Facebook costs a phone 292 ms of main-thread work and 287 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.

  • rebuyengine.com adds 243 ms

    243 ms

    rebuyengine.com costs a phone 243 ms of main-thread work and 468 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.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    80 KiB

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

  • Reduce unused CSS

    16 KiB

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

  • Duplicated JavaScript

    6 KiB

    6 KiB JavaScript is shipped twice across bundles.

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

    5 ms

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

Core Web Vitals

9 to fix33
  • 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: 23.5 s

    23.5 s

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

  • Speed Index: 10.7 s

    10.7 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

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

  • Real-user INP: 203 ms

    203 ms

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

  • Real-user CLS: 0.12

    0.12

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

  • Cumulative Layout Shift: 0.129

    0.129

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

  • 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

    +2%

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

5 checks passed
  • Real-user LCP: 1.2 s

    1.2 s

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 514 ms

    514 ms

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

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

    -11%

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

4 to fix25
  • Page weight: 28.2 MB in 325 requests

    28.2 MB

    Your homepage downloads 28.2 MB in 325 requests on a phone: media 23.0 MB (2), scripts 2.1 MB (112) and images 2.0 MB (47). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    bed3e3e9-1bf6-489d-8445-f4cc5312fd66.jpeg weighs 761 KiB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    769 KiB

    2 images are downloaded at several times the size a phone draws them, for example bed3e3e9-1bf6-489d-8445-f4cc5312fd66.jpeg at 4,341 px wide, shown at 338 px. Resized copies would save about 769 KiB.

  • 2 images in older formats

    2 images (831 KiB) 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 8.0 g of CO₂ per visit

    7.99 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

4 to fixGoogle 8494
  • 14 tap targets too small

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

  • 10 text elements with low contrast

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

  • 11 links without text

    11 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

1 checks passed
  • 53 automated accessibility rules passed

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

SEO

5 to fixGoogle 9276
  • Title is short (19 characters)

    Your title is only 19 characters: “Chris McMillan Hair”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (182 characters)

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

  • Structured data has 4 problems

    Structured data found (Organization and WebSite) but with 4 problems, for example “Organization: sameAs is not an absolute URL ("#")”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 78 internal links, 4 external

    The homepage links to 78 pages on chrismcmillan.com and 4 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.chrismcmillan.com/.

  • 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.chrismcmillan.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.chrismcmillan.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 (914 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix68
  • 1 page without a title

    https://www.chrismcmillan.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.chrismcmillan.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://www.chrismcmillan.com/collections/all, https://www.chrismcmillan.com/customer_authentication/redirect and https://www.chrismcmillan.com/collections/the-routine-sets have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.chrismcmillan.com/collections/all, https://www.chrismcmillan.com/customer_authentication/redirect and https://www.chrismcmillan.com/collections/the-routine-sets 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 33 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    7 pages of 15 loaded without an error (the rest turned automated requests away).

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

Best practices

2 to fixGoogle 9687
  • 14 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 8 testimonial or review blocks. 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 793 words of copy

    The homepage carries about 793 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: “SHOP NOW” and “JOIN THE COMMUNITY”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “SHOP NOW”, “JOIN THE COMMUNITY” and “SHOP THE SETS”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 39 cookies set on arrival

    39

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

  • 52 other companies contacted

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

Apps your storefront loads

Microsoft Clarity · Rebuy Personalization Engine · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Countdown Timer · rebuyengine.com · superfiliate-cdn.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

Stack

E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Hiring

Hiring
3 open roles
Job board
careers page

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on chrismcmillan.com, including 21 speed issues, 5 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