troyleedesigns.ca website review

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

Signyfyd costs a phone 1.2 s of main-thread work and 279 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (Signyfyd, Yotpo and Google Tag Manager and others), adding 2.2 MB and 2.8 s of main-thread time.

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

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

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

Yotpo costs a phone 428 ms of main-thread work and 601 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.

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

Google Tag Manager costs a phone 288 ms of main-thread work and 357 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.

Klaviyo costs a phone 220 ms of main-thread work and 318 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 84 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 110 ms faster on a phone.

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

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

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 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bike”.

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

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

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

The layout shifts by 0.336 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 238 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 63.5 MB in 530 requests on a phone: media 56.6 MB (8), scripts 2.6 MB (124) and images 2.3 MB (66). Under 2 MB keeps phones on slow connections fast.

BIKE_f5f105b0-11ee-456f-a7e5-9d999d809001.jpg 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).

1 image further down the page (45 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

ARIA tooltip nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

Your <h1> is empty.

The homepage links to 440 pages on troyleedesigns.ca and 15 external pages.

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

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

https://troyleedesigns.com/customer_authentication/redirect and https://troyleedesigns.com/policies/shipping-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://troyleedesigns.com/customer_authentication/redirect and https://troyleedesigns.com/collections/stage-2-helmets have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

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.

Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 23 cookies (measured from a US location before any click).

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