tallgrass.ca website review

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

2 images could be 467 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

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

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

14 long tasks block the main thread while loading, the longest for 1.2 s. During a long task the page ignores taps.

8 third-party services load with your homepage (Shopify, Hubspot and Google Tag Manager and others), adding 933 KiB and 858 ms of main-thread time.

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

Shopify costs a phone 604 ms of main-thread work and 609 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 70 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

Desktop scores 68 but mobile only 33. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

2 KiB could be saved by minifying JavaScript.

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

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

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

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

1 image 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.8 MB in 189 requests on a phone: scripts 1.1 MB (64), other files 853 KiB (102) and images 660 KiB (9). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example AdobeStock_526927990_2000x1334.jpg at 2,000 px wide, shown at 390 px. Resized copies would save about 75 KiB.

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

All page content should be contained by landmarks: 5 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.

8 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 24 characters: “TallGrass Natural Health”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

6 links have no real href, so search engines can't follow them.

Your <h1> is empty.

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

The homepage links to 34 pages on tallgrass.ca and 4 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

Your homepage links to https://tallgrass.ca/apps/advanced-wishlist, which answers with an error. Visitors hit a dead end and search engines drop it.

We fetched 8 pages linked from your homepage and read each the way a search engine does.

6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://tallgrass.ca/apps/wlm/css/wlmhideaddtocart.css?v=1.0.1' because its MIME type ('te…”.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and HubSpot (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 12 cookies (measured from a US location before any click).

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