Website review, no card needed

nutricanine.ca logo

nutricanine.ca website review

Visit site (opens in a new tab)Reviewed 8 November 202638 issues · 86 checks

This review found 38 issues worth fixing on nutricanine.ca, 17 of them high impact, across 86 checks. The most urgent: improve image delivery. 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.9 s1.5 sMay 16Oct 311.6 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.7 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.7 s
Aug 15, 20261.7 s
Aug 22, 20261.7 s
Aug 29, 20261.7 s
Sep 5, 20261.7 s
Sep 12, 20261.8 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.6 s
Oct 31, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
161 ms125 msMay 16Oct 31154 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026129 ms
May 23, 2026136 ms
May 30, 2026137 ms
Jun 6, 2026137 ms
Jun 13, 2026137 ms
Jun 20, 2026137 ms
Jun 27, 2026138 ms
Jul 4, 2026144 ms
Jul 11, 2026145 ms
Jul 18, 2026145 ms
Jul 25, 2026145 ms
Aug 1, 2026138 ms
Aug 8, 2026138 ms
Aug 15, 2026142 ms
Aug 22, 2026146 ms
Aug 29, 2026151 ms
Sep 5, 2026153 ms
Sep 12, 2026154 ms
Sep 19, 2026156 ms
Sep 26, 2026157 ms
Oct 3, 2026154 ms
Oct 10, 2026154 ms
Oct 17, 2026154 ms
Oct 24, 2026155 ms
Oct 31, 2026154 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 nutricanine.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nutricanine.ca at 1.1 s1.1 s
  2. nutricanine.ca at 2.2 s2.2 s
  3. nutricanine.ca at 3.3 s3.3 s
  4. nutricanine.ca at 4.4 s4.4 s
  5. nutricanine.ca at 5.5 s5.5 s
  6. nutricanine.ca at 6.6 s6.6 s
  7. nutricanine.ca at 7.7 s7.7 s
  8. nutricanine.ca at 8.8 s8.8 s

Speed

13 to fix42
  • Improve image delivery

    3.5 s · 1.3 MB

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

  • Reduce unused JavaScript

    1.8 s · 401 KiB

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

  • Use efficient cache lifetimes

    1.4 s · 318 KiB

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

  • Mobile performance score: 42

    42/100

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

  • Main-thread work: 9.7 s

    A phone's processor spends 9.7 s on main-thread work while loading, 5.7 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 (Unpkg, Clarity and Klaviyo and others), adding 1.2 MB and 1.7 s of main-thread time.

  • Unpkg adds 794 ms

    794 ms

    Unpkg costs a phone 794 ms of main-thread work and 96 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.

  • 19 long tasks on the main thread

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

  • Clarity adds 351 ms

    351 ms

    Clarity costs a phone 351 ms of main-thread work and 28 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.

  • Render-blocking requests

    350 ms

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

  • Klaviyo adds 203 ms

    203 ms

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

  • 1,921 HTML elements

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

  • Shopify adds 36 ms

    36 ms

    Shopify costs a phone 36 ms of main-thread work and 457 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

    290 ms · 65 KiB

    About 65 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 290 ms faster on a phone.

  • Legacy JavaScript

    150 ms · 54 KiB

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

  • Font display

    150 ms

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

  • 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

6 to fix100
  • Largest Contentful Paint: 28.5 s

    28.5 s

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

  • Time to Interactive: 32.3 s

    32.3 s

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

  • Speed Index: 15.1 s

    15.1 s

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

  • Total Blocking Time: 969 ms

    969 ms

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

  • 46 images without width and height

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

  • First Contentful Paint: 1.9 s

    1.9 s

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

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

    +17%

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

  • Largest content (LCP) held steady for real visitors

    -6%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 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: 1.4 s

    1.4 s

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

  • Real-user INP: 111 ms

    111 ms

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

  • Real-user CLS: 0.10

    0.10

    For real visitors the layout shifts by 0.10 (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.

  • Real-user TTFB: 406 ms

    406 ms

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

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

5 to fix18
  • Page weight: 9.1 MB in 297 requests

    9.1 MB

    Your homepage downloads 9.1 MB in 297 requests on a phone: images 6.3 MB (60), other files 1.4 MB (132) and scripts 1.1 MB (81). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 3.3 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    2.0 MB

    6 images are downloaded at several times the size a phone draws them, for example NutriCanine-431_2.jpg at 4,246 px wide, shown at 390 px. Resized copies would save about 2.0 MB.

  • 24 images below the first screen load straight away

    24 images further down the page (4.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 4 images in older formats

    4 images (1.8 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.

  • About 2.6 g of CO₂ per visit

    2.58 g

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

Accessibility

6 to fixGoogle 8492
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 16 text elements with low contrast

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

  • 6 images without alt text

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

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

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

  • 3 links without text

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

  • 1 form field without a label

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

  • Headings skip levels

    Headings skip levels (h1 → h3 and h2 → h4), 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 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9295
  • Meta description is long (320 characters)

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

  • Open Graph partly set

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

  • No X (Twitter) card tag

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

  • 37 internal links, 8 external

    The homepage links to 37 pages on nutricanine.ca and 8 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Your dog deserves better than a bag.”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “Gently Cooked Dog Food | NutriCanine”.

  • Canonical URL set

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

  • 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://nutricanine.ca/sitemap.xml.

AI search readiness

100
4 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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,175 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://nutricanine.ca/blogs/dog-digest, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 6 pages without a meta description

    https://nutricanine.ca/pages/recipes, https://nutricanine.ca/pages/careers, https://nutricanine.ca/pages/affiliate-program, https://nutricanine.ca/pages/wholesale_inquiries, https://nutricanine.ca/policies/refund-policy and https://nutricanine.ca/policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://nutricanine.ca/pages/affiliate-program and https://nutricanine.ca/pages/wholesale_inquiries have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 internal pages checked

    We fetched 10 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • 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 9 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 2 broken images

    2 images failed to load on a phone, for example https://nutricanine.ca/.

  • 2 small tap targets

    2 of 7 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: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 2,708 words of copy

    The homepage carries about 2,708 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Get Started”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Get Started”, “Start the Quiz — Save 40%” and “Get started”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 49 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity and Mixpanel.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

  • 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
  • 11 trackers load before any consent

    11

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

  • 33 cookies set on arrival

    33

    Opening the homepage sets 33 cookies, 1 of them by other companies (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.

  • 58 other companies contacted

    Loading the homepage contacts 58 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 nutricanine.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on nutricanine.ca, including 19 speed issues and 1 SEO issue. 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