ticats.ca website review

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.4 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and cfl.ca and others), adding 2.6 MB and 1.5 s of main-thread time.

Google Tag Manager costs a phone 681 ms of main-thread work and 998 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 461 ms. During a long task the page ignores taps.

Google/Doubleclick Ads costs a phone 392 ms of main-thread work and 591 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.

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

cfl.ca costs a phone 238 ms of main-thread work and 567 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 34 KiB of CSS is downloaded but never applied on this page.

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

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.

3 KiB could be saved by minifying JavaScript.

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

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

Visually, the page fills in at 14.8 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.

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

For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.

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

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

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

Your homepage downloads 5.8 MB in 391 requests on a phone: scripts 3.0 MB (148), images 1.1 MB (61) and fonts 813 KiB (10). Under 2 MB keeps phones on slow connections fast.

4 images further down the page (156 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

Elements with visible text labels do not have matching accessible names. (3 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 23 pages on ticats.ca and 39 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.

There is no /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.

/schedule has no <title>, so Google invents the link text in results.

/schedule, /article/tiger-cats-and-friends-remember-june-jones, /article/remembering-june-jones-a-brilliant-football-mind-a-loyal-friend-and-a-one-of-a-kind-coach, /article/hamilton-tiger-cats-mourn-the-passing-of-former-head-coach-june-jones, /article/revenberg-and-ossai-earn-east-division-all-cfl-honours and /article/as-lockers-empty-in-october-the-ticats-turn-the-page-to-2027 and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

/schedule, /roster and /listen have no <h1> headline, so visitors and search engines get no clear main topic.

/schedule and /roster have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

/schedule, /article/tiger-cats-and-friends-remember-june-jones, /article/remembering-june-jones-a-brilliant-football-mind-a-loyal-friend-and-a-one-of-a-kind-coach, /article/hamilton-tiger-cats-mourn-the-passing-of-former-head-coach-june-jones, /article/as-lockers-empty-in-october-the-ticats-turn-the-page-to-2027 and /article/tiger-cats-force-four-turnovers-down-redblacks-in-regular-season-finale and 2 others took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://content.cfl.ca/logos/ham-dark.svg.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “This version of the RudderStack JavaScript SDK is deprecated and no longer maintained. While your events are still bein…”.

Large scripts ship without source maps.

Chrome logged issues while loading the page (“Cookie”).

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

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

Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Analytics, Google Tag Manager and The Trade Desk 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 11 cookies, 3 of them by other companies (measured from a US location before any click).

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