kavu.com website review

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

13 images could be 750 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

8 third-party services load with your homepage (loox.io, Shopify and Klaviyo and others), adding 1.0 MB and 330 ms of main-thread time.

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

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

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

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

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

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

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

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.

Your largest element takes 16.0 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 16.2 s. Good is under 3.8 s.

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

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

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

Your homepage downloads 3.7 MB in 359 requests on a phone: scripts 1.3 MB (171), images 1.2 MB (16) and other files 884 KiB (149). Under 2 MB keeps phones on slow connections fast.

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

1 image (51 KiB) is 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 1.05 g of CO₂e: 125.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

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

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

There are 6 <h1> headlines (“KAVU.com”, “Grab Bag” and “Cedar Cove”). One clear main headline is easier for people and search engines.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 200 pages on kavu.com and 13 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://kavu.com/pages/shop-local is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://kavu.com/collections/mens-shirts, https://kavu.com/collections/mens-tees, https://kavu.com/collections/mens-knits-fleece, https://kavu.com/collections/mens-sweatshirts-throwshirts, https://kavu.com/collections/mens-jackets-vests and https://kavu.com/collections/mens-shorts and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://kavu.com/collections/new-arrivals/MENS, whose canonical is https://kavu.com/collections/new-arrivals/mens. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://kavu.com/pages/shop-local, https://kavu.com/collections/mens-shirts, https://kavu.com/collections/mens-tees, https://kavu.com/collections/mens-knits-fleece, https://kavu.com/collections/mens-sweatshirts-throwshirts and https://kavu.com/collections/mens-jackets-vests and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

The homepage has only about 248 words of visible text; thin pages give Google and first-time buyers little to go on.

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

The page uses urgency cues (a countdown or limited-time wording).

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

Opening the homepage sets 7 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 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.