kanine.com website review

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

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

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

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

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

Shopify costs a phone 76 ms of main-thread work and 488 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 load with your homepage (loox.io, Hotjar and Shopify and others), adding 788 KiB and 436 ms of main-thread time.

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

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

4 KiB could be saved by minifying JavaScript.

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

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

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.

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

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

The layout shifts by 0.813 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

Your homepage downloads 9.6 MB in 453 requests on a phone: images 7.8 MB (214), scripts 710 KiB (120) and other files 672 KiB (81). Under 2 MB keeps phones on slow connections fast.

9 images are downloaded at several times the size a phone draws them, for example MBB_289d591d-8ff4-4048-8133-6d6a470ef74e.jpg at 5,000 px wide, shown at 360 px. Resized copies would save about 4.0 MB.

2 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.

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

3 images (1.2 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.

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

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

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 31 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 on the page fails this check, rated moderate by axe-core.

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

Headings should not be empty: 20 elements on the page fail this check, rated minor by axe-core.

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

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

Your title is 122 characters, so Google will cut it off around 60: “Kanine | Premium Dog Apparel | Tommy Hilfiger, Ralph Lauren, Arsenal – Kanine | Premium D…”.

There are 2 <h1> headlines (“Helping You Redefine Pet Fashion and Accessories” and “The Greatest Pet Beds Are Now Available”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 310 pages on kanine.com and 17 external pages.

Your robots.txt lets ChatGPT (ChatGPT-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.kanine.com/collections/sports/Tottenham-Hotspurs+Arsenal+Manchester-United, whose canonical is https://www.kanine.com/collections/sports. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.kanine.com/collections/bowls-water-feeders and https://www.kanine.com/collections/mats-beds took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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 576 words of visible text.

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

Opening the homepage sets 17 cookies (measured from a US location before any click).

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.

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