thehonestkitchen.com website review

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

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

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

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

81 files are served with short cache lifetimes, so returning visitors download them again (1.6 MB).

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

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

18 images could be 578 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

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

Yotpo costs a phone 194 ms of main-thread work and 406 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.

Google CDN costs a phone 133 ms of main-thread work and 613 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.

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

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

109 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 85 KiB JavaScript that modern phones do not need.

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

6 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 14.9 MB in 562 requests on a phone: fonts 5.7 MB (17), scripts 4.4 MB (210) and other files 2.8 MB (217). Under 2 MB keeps phones on slow connections fast.

THK.com_DogEssentialClusters_Homepagembl-healthy-high-qualit 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).

4 images are downloaded at several times the size a phone draws them, for example xe7miuulpml1bynrzq38_750x750.png at 750 px wide, shown at 114 px. Resized copies would save about 204 KiB.

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

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

ARIA attributes must conform to valid values: 11 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.

1 element has a tabindex above 0, which scrambles the keyboard order.

Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is 69 characters, so Google will cut it off around 60: “The Honest Kitchen – Healthy, High Quality, Human Grade Food for Dogs”.

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

Your <h1> is empty.

The homepage links to 49 pages on thehonestkitchen.com and 7 external pages.

https://www.thehonestkitchen.com/pages/overstock-sale and https://www.thehonestkitchen.com/pages/store-locator have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.thehonestkitchen.com/pages/overstock-sale, https://www.thehonestkitchen.com/pages/store-locator, https://www.thehonestkitchen.com/collections/shop-dog-food-treats-toppers, https://www.thehonestkitchen.com/collections/shop-cat-food-treats, https://www.thehonestkitchen.com/pages/healthy-dog-treats and https://www.thehonestkitchen.com/collections/shop-puppy-food-treats-toppers and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.thehonestkitchen.com/pages/overstock-sale, https://www.thehonestkitchen.com/pages/healthy-dog-treats, https://www.thehonestkitchen.com/collections/shop-healthy-dog-treats and https://www.thehonestkitchen.com/collections/shop-healthy-dog-food-toppers have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97157146&tm=gtm002&Ver=2&mid=489da0de-1808-415c-a8dd-6030c88f048d&bo=1&sid=bb095bd0d8d311f1b2d6599f87e6f485&vid=bb09a5d0d8d311f1a87155210c8888e6&vids=1&msclkid=N&pi=91.

7 of 28 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 (“Unload event listeners are deprecated and will be removed.”).

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

Large scripts ship without source maps.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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

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

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