Website review, no card needed

graydonskincare.com logo

graydonskincare.com website review

Visit site (opens in a new tab)Reviewed 10 November 202642 issues · 85 checks

This review found 42 issues worth fixing on graydonskincare.com, 14 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.6 s1.7 sMay 23Aug 222.5 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.8 s
May 30, 20262.0 s
Jul 25, 20262.1 s
Aug 1, 20262.4 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s

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 graydonskincare.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. graydonskincare.com at 1.1 s1.1 s
  2. graydonskincare.com at 2.2 s2.2 s
  3. graydonskincare.com at 3.3 s3.3 s
  4. graydonskincare.com at 4.3 s4.3 s
  5. graydonskincare.com at 5.4 s5.4 s
  6. graydonskincare.com at 6.5 s6.5 s
  7. graydonskincare.com at 7.6 s7.6 s
  8. graydonskincare.com at 8.7 s8.7 s

Speed

11 to fix37
  • Render-blocking requests

    1.8 s

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

  • Main-thread work: 11.0 s

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

  • Mobile performance score: 37

    37/100

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

  • 5,160 HTML elements

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

  • Improve image delivery

    150 ms · 3.2 MB

    26 images could be 3.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, Shopify and bestfreecdn.com and others), adding 4.9 MB and 746 ms of main-thread time.

  • Reduce unused JavaScript

    600 ms · 527 KiB

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

  • 15 long tasks on the main thread

    15 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.

  • Shopify adds 286 ms

    286 ms

    Shopify costs a phone 286 ms of main-thread work and 3.7 MB 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.

  • Klaviyo adds 358 ms

    358 ms

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

  • Reduce unused CSS

    300 ms · 94 KiB

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

  • Use efficient cache lifetimes

    177 KiB

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

  • Legacy JavaScript

    150 ms · 19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 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).

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

  • Minify CSS

    9 KiB

    9 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: 19 ms

    19 ms

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

Core Web Vitals

7 to fix38
  • Largest Contentful Paint: 13.5 s

    13.5 s

    Your largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our customers' faves Bestsellers See more”.

  • Time to Interactive: 17.5 s

    17.5 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Speed Index: 7.7 s

    7.7 s

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

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

    +29%

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

  • 1 image without width and height

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

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix35
  • Page weight: 10.7 MB in 405 requests

    10.7 MB

    Your homepage downloads 10.7 MB in 405 requests on a phone: images 4.0 MB (52), media 3.5 MB (1) and scripts 1.5 MB (191). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Graydon-hero_1000px.webp weighs 1.7 MB. On a phone connection a single image that size takes seconds.

  • 3 images in older formats

    3 images (2.1 MB) 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.

  • 1 image far larger than shown

    346 KiB

    1 image is downloaded at several times the size a phone draws it, for example graydonmoffat_2026_457x447.webp at 456 px wide, shown at 1 px. Resized copies would save about 346 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (36 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 3.0 g of CO₂ per visit

    3.03 g

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

Accessibility

9 to fixGoogle 8190
  • 49 text elements with low contrast

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

  • ARIA commands must have an accessible name (13 elements)

    ARIA commands must have an accessible name: 13 elements on the page fail this check, rated serious by axe-core.

  • 4 images without alt text

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

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

  • 2 tap targets too small

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

  • 1 form field without a label

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4), 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. (1 element).

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

2 to fixGoogle 8590
  • Title is long (89 characters)

    Your title is 89 characters, so Google will cut it off around 60: “Clinically proven natural skincare for sensitive skin | Made in Canada — Graydon Skincare”.

  • 2 links with vague text

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

  • 174 internal links, 10 external

    The homepage links to 174 pages on graydonskincare.com and 10 external pages.

7 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “GRAYDON | Clinically proven skincare rooted in nature and backed by science. Made to support sensitive skin as you age …”.

  • One H1 headline

    Your main headline reads: “Welcome to Graydon Skincare”.

  • Canonical URL set

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

  • Structured data in place

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

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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

  • llms.txt published

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

Other pages

3 to fix88
  • 6 pages without a meta description

    https://graydonskincare.com/pages/routine-builder, https://graydonskincare.com/collections/sensitive-skin, https://graydonskincare.com/collections/pro-aging, https://graydonskincare.com/collections/sallow-skin, https://graydonskincare.com/collections/oily-and-combination-skin and https://graydonskincare.com/pages/magazine-homepage have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://graydonskincare.com/blogs/mindfulbeauty/tagged/skincarembm and https://graydonskincare.com/blogs/mindfulbeauty/tagged/agingmbm use the same meta description. A description written for each page earns more clicks.

  • 1 page without an H1

    https://graydonskincare.com/pages/routine-builder has no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://graydonskincare.com/collections/sallow-skin, https://graydonskincare.com/collections/oily-and-combination-skin, https://graydonskincare.com/pages/magazine-homepage, https://graydonskincare.com/blogs/mindfulbeauty/tagged/skincarembm and https://graydonskincare.com/blogs/mindfulbeauty/tagged/agingmbm took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 93 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

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “TypeError: Cannot destructure property 'Section' of 'window.PxuThemeSections' as it is undefined.”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 1,611 words of copy

    The homepage carries about 1,611 words of visible text.

3 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Shop Bundles”, “Shop Graydon” and “Quick shop”.

  • 8 short forms

    8 short forms (3 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 34 testimonial or review blocks and 11 trust badges.

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.

  • 17 cookies set on arrival

    17

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

  • 25 other companies contacted

    Loading the homepage contacts 25 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 graydonskincare.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

Klaviyo Email Marketing Sms · Gsc Instagram Feed · Countdown Timer · amazonaws.com · bestfreecdn.com · backinstock.org · cloudfront.net

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
Hosting
Shopify

Company

Headquarters
Toronto

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on graydonskincare.com, including 18 speed issues, 2 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