kanu.pet website review

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

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

49 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Shopify and Facebook and others), adding 2.1 MB and 1.3 s of main-thread time.

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

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

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

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

Shopify costs a phone 440 ms of main-thread work and 1.0 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.

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

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

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

4 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

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

Your homepage downloads 6.2 MB in 319 requests on a phone: images 3.1 MB (99), scripts 1.9 MB (80) and other files 743 KiB (96). Under 2 MB keeps phones on slow connections fast.

32 images are downloaded at several times the size a phone draws them, for example 1_5c846415-34a8-44a5-91d9-f565d510a7bc.webp at 600 px wide, shown at 181 px. Resized copies would save about 1.3 MB.

27 images (4.3 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.

4ed76e7d-28b7-4672-a035-9b89282c0c73.png 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).

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

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

52 elements hidden from screen readers can still receive keyboard focus.

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

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

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (3 elements).

<td> elements in a large <table> do not have table headers. (1 element).

There are 5 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.

The homepage links to 495 pages on kanu.pet and 13 external pages.

https://kanu.pet/collections/alimento-seco-natural-para-perros and https://kanu.pet/collections/alimento-seco-tradicional-para-perros have no meta description, so Google writes the search snippet from whatever text it finds.

https://kanu.pet/collections/alimento-seco-natural-para-perros, https://kanu.pet/collections/alimento-seco-tradicional-para-perros, https://kanu.pet/collections/alimento-medicado-para-perro, https://kanu.pet/collections/alimento-humedo-para-perro, https://kanu.pet/collections/alimento-natural-y-congelado-para-perro and https://kanu.pet/collections/toppers-para-perros and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 27 cookies, 6 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.