leavesoftrees.com website review

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

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

8 third-party services load with your homepage (Lucky Orange, Shopify and Klaviyo and others), adding 1.7 MB and 2.2 s of main-thread time.

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

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

Lucky Orange costs a phone 880 ms of main-thread work and 108 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 676 ms of main-thread work and 737 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.

About 397 KiB of JavaScript is downloaded but never used on this page.

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

okendo.io costs a phone 183 ms of main-thread work and 421 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 2,159 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

6 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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 4.0 MB in 503 requests on a phone: scripts 1.7 MB (222), other files 1.1 MB (203) and images 490 KiB (28). Under 2 MB keeps phones on slow connections fast.

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

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

5 tap targets are too small or too close together to hit reliably with a finger.

Scrollable region must have keyboard access: 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: 4 elements on the page fail this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Elements with visible text labels do not have matching accessible names. (5 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 74 characters, so Google will cut it off around 60: “Leaves of Trees Natural Luxury Skincare Toronto – Leaves of Trees - Canada”.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 54 pages on leavesoftrees.com and 4 external pages.

https://leavesoftrees.com/collections/deodorants, https://leavesoftrees.com/collections/argan-oils, https://leavesoftrees.com/collections/face-masks-1, https://leavesoftrees.com/collections/cleansers and https://leavesoftrees.com/collections/balms have no meta description, so Google writes the search snippet from whatever text it finds.

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

6 errors were logged to the browser console while the page loaded, for example “Framing 'https://www.facebook.com/' violates the following report-only Content Security Policy directive: "default-src …”.

1 image is served at too low a resolution for sharp phone screens.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 341 words of visible text.

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