toja.ca website review

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

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

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

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

8 third-party services load with your homepage (embedsocial.com, Klaviyo and Shopify and others), adding 1.2 MB and 388 ms of main-thread time.

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

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

embedsocial.com costs a phone 140 ms of main-thread work and 617 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 46 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

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

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

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

Your homepage downloads 4.2 MB in 237 requests on a phone: images 1.9 MB (32), scripts 1.3 MB (88) and other files 753 KiB (85). Under 2 MB keeps phones on slow connections fast.

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

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

There are 2 <h1> headlines (“” and “Build a Pergola in an afternoon”). One clear main headline is easier for people and search engines.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 84 pages on toja.ca and 6 external pages.

https://tojaliving.ca/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://tojaliving.ca/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://tojaliving.ca/customer_authentication/redirect, https://tojaliving.ca/collections/privacy-accessories and https://tojaliving.ca/collections/clearance have no meta description, so Google writes the search snippet from whatever text it finds.

https://tojaliving.ca/customer_authentication/redirect, https://tojaliving.ca/collections/pergola-kits, https://tojaliving.ca/collections/accessories and https://tojaliving.ca/collections/brackets have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 429 (Too Many Requests)”).

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

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.

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