Website review, no card needed

Way of Wade logo

wayofwade.com website review

Visit site (opens in a new tab)Reviewed 4 November 202622 issues · 79 checks

This review found 22 issues worth fixing on wayofwade.com, 5 of them high impact, across 79 checks. The most urgent: fails Core Web Vitals for real visitors. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Way of Wade

  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 s944 msAug 8Oct 31992 ms
Show as table
DateReal-visitor load time (LCP)
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.2 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.0 s
Oct 24, 20261.0 s
Oct 31, 2026992 ms
Real-visitor tap response (INP)75th percentile, phones
201 ms165 msAug 8Oct 31197 ms
Show as table
DateReal-visitor tap response (INP)
Aug 8, 2026169 ms
Aug 15, 2026187 ms
Aug 22, 2026188 ms
Aug 29, 2026192 ms
Sep 5, 2026196 ms
Sep 12, 2026195 ms
Sep 19, 2026195 ms
Sep 26, 2026194 ms
Oct 3, 2026194 ms
Oct 10, 2026194 ms
Oct 17, 2026195 ms
Oct 24, 2026196 ms
Oct 31, 2026197 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 wayofwade.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

1 to fix100
  • 1,736 HTML elements

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, cdnfonts.com and Yahoo! JAPAN Ads and others), adding 243 KiB and 3 ms of main-thread time.

  • Use efficient cache lifetimes

    18 KiB

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

  • Reduce unused CSS

    15 KiB

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

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

3 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.6 s

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

  • Server response: 33 ms

    33 ms

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

Core Web Vitals

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

  • Real-user TTFB: 944 ms

    944 ms

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

  • 11 images without width and height

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

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

    +10%

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

11 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 INP: 167 ms

    167 ms

    Real visitors wait 167 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 FCP: 1.2 s

    1.2 s

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

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

    -19%

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

  • First Contentful Paint: 1.5 s

    1.5 s

    The first text or image appears after 1.5 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).

  • Largest Contentful Paint: 1.5 s

    1.5 s

    Your largest element renders in 1.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Γ”.

  • Speed Index: 1.8 s

    1.8 s

    Visually, the page fills in at 1.8 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 1.5 s

    1.5 s

    The page is fully interactive after 1.5 s.

Images and page weight

2 to fix86
  • An image on the first screen is lazy-loaded

    mobile_e3947bde-2d9b-47a4-9014-36447318a158.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image far larger than shown

    58 KiB

    1 image is downloaded at several times the size a phone draws it, for example flag-mx.svg at 980 px wide, shown at 22 px. Resized copies would save about 58 KiB.

  • About 0.3 g of CO₂ per visit

    0.28 g

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

2 checks passed
  • Page weight: 997 KiB in 131 requests

    997 KiB

    Your homepage downloads 997 KiB in 131 requests on a phone: images 385 KiB (70), scripts 348 KiB (22) and HTML 149 KiB (1). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 9293
  • 8 text elements with low contrast

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 form fields without a label

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

  • 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 (h1 → h3), 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).

2 checks passed
  • Every image has alt text

    All 109 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

3 to fixGoogle 10084
  • Title is short (28 characters)

    Your title is only 28 characters: “Way of Wade Official Website”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (167 characters)

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

  • 174 internal links, 17 external

    The homepage links to 174 pages on wayofwade.com and 17 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Way of Wade”.

  • Canonical URL set

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

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

  • llms.txt published

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

Other pages

4 to fix57
  • 1 linked page is broken

    Your homepage links to https://www.wayofwade.com/t4s_pr_url, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 11 pages point its canonical at the homepage

    https://www.wayofwade.com/en-ca, https://www.wayofwade.com/en-mx, https://www.wayofwade.com/en-eu, https://www.wayofwade.com/en-gb, https://www.wayofwade.com/en-id and https://www.wayofwade.com/en-kr and 5 others 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.

  • 12 pages share a title

    /, https://www.wayofwade.com/en-ca, https://www.wayofwade.com/en-mx, https://www.wayofwade.com/en-eu, https://www.wayofwade.com/en-gb and https://www.wayofwade.com/en-id and 6 others all use the title “Way of Wade Official Website”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages share a meta description

    https://www.wayofwade.com/en-ca, https://www.wayofwade.com/en-mx, https://www.wayofwade.com/en-eu, https://www.wayofwade.com/en-gb, https://www.wayofwade.com/en-id and https://www.wayofwade.com/en-kr and 5 others use the same meta description. A description written for each page earns more clicks.

  • 5 pages slow to respond

    https://www.wayofwade.com/en-kr, https://www.wayofwade.com/en-ph, https://www.wayofwade.com/en-sg, https://www.wayofwade.com/en-ae and https://www.wayofwade.com/en-au took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 73 found) and read each the way a search engine does.

4 checks passed
  • Every page has a meta description

    All 13 pages that loaded have a meta description.

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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix85
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 313 words of copy

    The homepage carries about 313 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP 808 6 ULTRA” and “SHOP DLO 2”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “SHOP 808 6 ULTRA”, “SHOP DLO 2” and “SHOP NOW”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics and Microsoft Clarity.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 1 email link.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 5 cookies set on arrival

    5

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

  • 5 other companies contacted

    Loading the homepage contacts 5 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 wayofwade.com, 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
Analytics
Google Analytics | Microsoft Clarity
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on wayofwade.com, including 4 speed issues, 3 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