honest2goodness.com website review

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 1.1 MB and 513 ms of main-thread time.

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

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

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

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

7 images could be 215 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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 13.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 13.2 s. Good is under 3.8 s.

Visually, the page fills in at 6.1 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.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.7 MB in 221 requests on a phone: scripts 1,003 KiB (84), other files 924 KiB (98) and images 645 KiB (14). Under 2 MB keeps phones on slow connections fast.

H2G_HomePage_SplitLayout_Header_Wide-_1.jpg 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).

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

Your title is only 29 characters: “Honest to Goodness Pet Treats”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

Your <h1> is empty.

The homepage links to 32 pages on honest2goodness.com and 7 external pages.

https://www.honest2goodness.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.honest2goodness.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.honest2goodness.com/collections/dogs, https://www.honest2goodness.com/collections/upcycled-treats, https://www.honest2goodness.com/blogs/articles, https://www.honest2goodness.com/customer_authentication/redirect, https://www.honest2goodness.com/collections/all-products-1 and https://www.honest2goodness.com/collections/protein-bites and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.honest2goodness.com/collections/dogs, https://www.honest2goodness.com/collections/upcycled-treats, https://www.honest2goodness.com/pages/about-honest-to-goodness, https://www.honest2goodness.com/customer_authentication/redirect, https://www.honest2goodness.com/collections/all-products-1 and https://www.honest2goodness.com/collections/protein-bites and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 747 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel (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 23 cookies, 7 of them by other companies (measured from a US location before any click).

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