petreleaf.io website review

9 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 16.4 s faster on a phone.

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

A phone's processor spends 4.3 s on main-thread work while loading, 1.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, Shopify and Klaviyo and others), adding 2.0 MB and 855 ms of main-thread time.

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

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

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

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

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

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

Klaviyo costs a phone 188 ms of main-thread work and 432 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,562 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

8 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.

3 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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 8.1 MB in 334 requests on a phone: images 4.9 MB (44), scripts 1.8 MB (109) and other files 893 KiB (157). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example hemp-300-SR-HO.png at 1,250 px wide, shown at 175 px. Resized copies would save about 104 KiB.

1 image further down the page (35 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

Your canonical URL points to petreleaf.com, not petreleaf.io, so Google may credit that host instead.

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

Structured data found (BreadcrumbList, CollectionPage, FAQPage and ImageObject) but with 1 problem, for example “Organization: url points at a different host (https://petreleaf.com)”.

The homepage links to 114 pages on petreleaf.io and 11 external pages.

https://petreleaf.io/collections/shop-all-1, https://petreleaf.io/collections/calming-hemp-products-for-cats-dogs, https://petreleaf.io/collections/general-wellness-1, https://petreleaf.io/collections/hemp-digestion, https://petreleaf.io/collections/hip-joint-hemp-for-cats-dogs and https://petreleaf.io/collections/hemp-for-senior-cats-dogs and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://petreleaf.io/collections/shop-all-1, https://petreleaf.io/collections/general-wellness-1, https://petreleaf.io/collections/hemp-digestion, https://petreleaf.io/collections/hemp-for-senior-cats-dogs, https://petreleaf.io/collections/hemp-topical-1 and https://petreleaf.io/collections/hemp-products-for-dogs and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

1 image failed to load on a phone, for example https://petreleaf.io/.

2 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of null (reading 'dataset')”.

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.

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

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

The homepage carries about 1,354 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, 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 15 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 44 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.