Website review, no card needed

wildrose.ca logo

wildrose.ca website review

Visit site (opens in a new tab)Reviewed 5 November 202628 issues · 74 checks

This review found 28 issues worth fixing on wildrose.ca, 10 of them high impact, across 74 checks. The most urgent: reduce unused JavaScript. 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
1000 ms715 msMay 16Oct 31836 ms
Show as table
DateReal-visitor load time (LCP)
May 16, 2026748 ms
May 23, 2026778 ms
May 30, 2026808 ms
Jun 6, 2026785 ms
Jun 13, 2026785 ms
Jun 20, 2026792 ms
Jun 27, 2026764 ms
Jul 4, 2026794 ms
Jul 11, 2026821 ms
Jul 18, 2026820 ms
Jul 25, 2026857 ms
Aug 1, 2026903 ms
Aug 8, 2026905 ms
Aug 15, 2026830 ms
Aug 22, 2026822 ms
Aug 29, 2026816 ms
Sep 5, 2026840 ms
Sep 12, 2026935 ms
Sep 19, 2026956 ms
Sep 26, 2026938 ms
Oct 3, 2026967 ms
Oct 10, 2026915 ms
Oct 17, 2026926 ms
Oct 24, 2026892 ms
Oct 31, 2026836 ms
Real-visitor tap response (INP)75th percentile, phones
100 ms76 msMay 16Oct 3189 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202679 ms
May 23, 202681 ms
May 30, 202687 ms
Jun 13, 202686 ms
Jun 20, 202688 ms
Jun 27, 202687 ms
Jul 4, 202695 ms
Jul 11, 202696 ms
Jul 18, 202694 ms
Jul 25, 202687 ms
Aug 1, 202687 ms
Aug 8, 202685 ms
Aug 15, 202679 ms
Aug 22, 202679 ms
Aug 29, 202679 ms
Sep 12, 202694 ms
Sep 19, 202697 ms
Sep 26, 202696 ms
Oct 3, 202696 ms
Oct 10, 202696 ms
Oct 17, 202696 ms
Oct 24, 202695 ms
Oct 31, 202689 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 wildrose.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wildrose.ca at 0.4 s0.4 s
  2. wildrose.ca at 0.8 s0.8 s
  3. wildrose.ca at 1.2 s1.2 s
  4. wildrose.ca at 1.6 s1.6 s
  5. wildrose.ca at 2.0 s2.0 s
  6. wildrose.ca at 2.4 s2.4 s
  7. wildrose.ca at 2.8 s2.8 s
  8. wildrose.ca at 3.2 s3.2 s

Speed

4 to fix62
  • Reduce unused JavaScript

    1.7 s · 318 KiB

    About 318 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.

  • Mobile performance score: 62

    62/100

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

  • Google Tag Manager adds 235 ms

    235 ms

    Google Tag Manager costs a phone 235 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.

  • Klaviyo adds 101 ms

    101 ms

    Klaviyo costs a phone 101 ms of main-thread work and 319 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, Klaviyo and Shopify and others), adding 893 KiB and 398 ms of main-thread time.

  • 3 long tasks on the main thread

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

  • Use efficient cache lifetimes

    150 ms · 24 KiB

    6 files are served with short cache lifetimes, so returning visitors download them again (24 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.

  • Render-blocking requests

    150 ms

    8 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

  • Improve image delivery

    7 KiB

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

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

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 10.2 s

    10.2 s

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

  • Time to Interactive: 10.4 s

    10.4 s

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

  • Speed Index: 6.6 s

    6.6 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

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

    +15%

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

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

    +13%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 0.8 s

    0.8 s

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

  • Real-user INP: 87 ms

    87 ms

    Real visitors wait 87 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: 0.6 s

    0.6 s

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

  • Total Blocking Time: 200 ms

    200 ms

    Scripts block the page for only 200 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

2 to fix81
  • Page weight: 2.0 MB in 200 requests

    2.0 MB

    Your homepage downloads 2.0 MB in 200 requests on a phone: scripts 1,003 KiB (79), other files 673 KiB (72) and images 167 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    WR_25.04_Website_Homepage_Banner_1280x720_e0d82f00-96e6-42c5 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).

  • About 0.6 g of CO₂ per visit

    0.57 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

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

  • Documents must have <title> element to aid in navigation (1 element)

    Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

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

2 checks passed
  • Every image has alt text

    All 29 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

6 to fixGoogle 7762
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 47 internal links, 6 external

    The homepage links to 47 pages on wildrose.ca and 6 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://wildrose.ca/.

  • 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://wildrose.ca/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 (567 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix62
  • 15 pages without a title

    https://wildrose.ca/collections/all-products, https://wildrose.ca/products/herbal-d-tox-kit, https://wildrose.ca/products/gentle-herbal-d-tox-kit, https://wildrose.ca/products/liver-support-kit, https://wildrose.ca/pages/about-us and https://wildrose.ca/blogs/recipes and 9 others have no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

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

  • 15 pages without a meta description

    https://wildrose.ca/collections/all-products, https://wildrose.ca/products/herbal-d-tox-kit, https://wildrose.ca/products/gentle-herbal-d-tox-kit, https://wildrose.ca/products/liver-support-kit, https://wildrose.ca/pages/about-us and https://wildrose.ca/blogs/recipes and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://wildrose.ca/collections/all-products, https://wildrose.ca/pages/about-us, https://wildrose.ca/pages/herbs, https://wildrose.ca/pages/faqs, https://wildrose.ca/pages/downloadable-resources and https://wildrose.ca/customer_authentication/redirect and 1 other 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 16 found) and read each the way a search engine does.

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

Best practices

1 to fixGoogle 9693
  • 4 small tap targets

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

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 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 537 words of copy

    The homepage carries about 537 words of visible text.

4 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Shop”, “Learn More” and “Contact”.

  • 5 short forms

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

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, 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.

  • 6 cookies set on arrival

    6

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

  • 16 other companies contacted

    Loading the homepage contacts 16 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 wildrose.ca, 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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Judge Me Reviews · 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

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on wildrose.ca, including 8 speed issues, 6 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