purpleleafshop.ca website review

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

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

8 images could be 8.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Hotjar and Shopify and others), adding 29.4 MB and 2.4 s of main-thread time.

Shopify costs a phone 383 ms of main-thread work and 28.4 MB 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 674 KiB 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 695 ms of main-thread work and 546 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.

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

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

Hotjar costs a phone 458 ms of main-thread work and 65 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.

Other Google APIs/SDKs costs a phone 365 ms of main-thread work and 22 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 65 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 CDN costs a phone 242 ms of main-thread work and 330 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,906 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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.

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

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

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

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

Your homepage downloads 31.3 MB in 346 requests on a phone: media 19.1 MB (3), images 9.0 MB (61) and scripts 1.8 MB (139). Under 2 MB keeps phones on slow connections fast.

42e6756e4b73e7a7107f98ef99a66485.gif weighs 19.8 MB. On a phone connection a single image that size takes seconds.

2 images (20.2 MB) are 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.

5 images are downloaded at several times the size a phone draws them, for example Louvered-Pergola-PE.webp at 1,250 px wide, shown at 390 px. Resized copies would save about 140 KiB.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “Organization: sameAs is an empty list”.

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

Your <h1> is empty.

The homepage links to 295 pages on purpleleafshop.ca and 30 external pages.

Your Organization JSON-LD is missing logo, 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.

There is no https://purpleleafshop.ca/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

3 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=97013273&Ver=2&mid=4bd8b9fb-7c3d-4b63-98de-5bfc491178db&bo=1&sid=b5691610dcfd11f1bd6cb1bb95b648b9&vid=b56937e0dcfd11f199864b165c2bce30&vids=1&msclkid=N&pid=em%3Dd8d82a.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

5 images are served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Content security policy”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

The homepage has only about 174 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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Microsoft Ads and 1 more (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 19 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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.