thatskool.ca website review

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

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

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

The page has 2,389 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

6 images could be 249 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

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

About 42 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 80 ms faster on a phone.

2 third-party services load with your homepage (Shopify and shop.app), adding 254 KiB and 55 ms of main-thread time.

79 KiB JavaScript is shipped twice across bundles.

Polyfills for old browsers add 7 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.

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

That_s_Kool_Logo_header2.png 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).

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h2 → h4 and h2 → h4), 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 22 characters: “Welcome to That's Kool”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your <h1> is empty.

The homepage links to 19 pages on thatskool.ca and 5 external pages.

https://www.thatskool.ca/collections/cardboard-builder-kit, https://www.thatskool.ca/policies/refund-policy, https://www.thatskool.ca/policies/privacy-policy and https://www.thatskool.ca/policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.thatskool.ca/products/free-printable-echo-colouring-page-echo-in-space-copy, https://www.thatskool.ca/products/free-printable-echo-colouring-page-echo-with-guitar and https://www.thatskool.ca/products/free-printable-echo-colouring-page-oliver-and-pip-and-the-cardboard-rocketship use the same meta description. A description written for each page earns more clicks.

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

1 error was logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

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.

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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.

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

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