Website review, no card needed

thunderbaycatchtheace.ca logo

thunderbaycatchtheace.ca website review

Visit site (opens in a new tab)Reviewed 7 November 202622 issues · 81 checks

This review found 22 issues worth fixing on thunderbaycatchtheace.ca, 6 of them high impact, across 81 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.2 s926 msMay 16Oct 311.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 2026957 ms
May 23, 20261.0 s
May 30, 20261.0 s
Jun 6, 2026994 ms
Jun 13, 20261.0 s
Jun 20, 20261.0 s
Jun 27, 20261.0 s
Jul 4, 20261.0 s
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.1 s
Aug 15, 20261.2 s
Aug 22, 20261.2 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.0 s
Oct 31, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
115 ms88 msMay 16Oct 31111 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202694 ms
May 23, 202695 ms
May 30, 202691 ms
Jun 6, 202695 ms
Jun 13, 202696 ms
Jun 20, 2026102 ms
Jun 27, 2026103 ms
Jul 4, 2026104 ms
Jul 11, 2026104 ms
Jul 18, 2026104 ms
Jul 25, 2026105 ms
Aug 1, 2026106 ms
Aug 8, 2026106 ms
Aug 15, 2026106 ms
Aug 22, 2026108 ms
Aug 29, 2026107 ms
Sep 5, 2026106 ms
Sep 12, 2026109 ms
Sep 19, 2026107 ms
Sep 26, 2026107 ms
Oct 3, 2026109 ms
Oct 10, 2026106 ms
Oct 17, 2026110 ms
Oct 24, 2026112 ms
Oct 31, 2026111 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of thunderbaycatchtheace.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thunderbaycatchtheace.ca at 0.4 s0.4 s
  2. thunderbaycatchtheace.ca at 0.8 s0.8 s
  3. thunderbaycatchtheace.ca at 1.1 s1.1 s
  4. thunderbaycatchtheace.ca at 1.5 s1.5 s
  5. thunderbaycatchtheace.ca at 1.9 s1.9 s
  6. thunderbaycatchtheace.ca at 2.3 s2.3 s
  7. thunderbaycatchtheace.ca at 2.6 s2.6 s
  8. thunderbaycatchtheace.ca at 3.0 s3.0 s

Speed

7 to fix74
  • Reduce unused JavaScript

    1.6 s · 357 KiB

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

  • Mobile performance score: 74

    74/100

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

  • Use efficient cache lifetimes

    600 ms · 250 KiB

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

  • Render-blocking requests

    550 ms

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

  • Facebook adds 302 ms

    302 ms

    Facebook costs a phone 302 ms of main-thread work and 280 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.

  • 4 long tasks on the main thread

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

  • Google CDN adds 136 ms

    136 ms

    Google CDN costs a phone 136 ms of main-thread work and 349 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.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Facebook, Google CDN and Cloudflare CDN and others), adding 698 KiB and 467 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 19 KiB

    About 19 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.

  • Legacy JavaScript

    150 ms · 13 KiB

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

  • Improve image delivery

    88 KiB

    6 images could be 88 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 checks passed
  • Main-thread work: 1.3 s

    A phone's processor spends 1.3 s on main-thread work while loading, 556 ms of it running JavaScript. That is comfortably low.

  • Server response: 4 ms

    4 ms

    Your server sent the HTML in 4 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 6.0 s

    6.0 s

    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.

  • Time to Interactive: 7.8 s

    7.8 s

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

  • Total Blocking Time: 224 ms

    224 ms

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

  • 4 images without width and height

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

  • Tap response (INP) got 18% slower for real visitors

    +18%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.2 s

    1.2 s

    Real visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 77 ms

    77 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 525 ms

    525 ms

    Real visitors wait 525 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 1.3 s

    1.3 s

    The first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.

  • Speed Index: 2.4 s

    2.4 s

    Visually, the page fills in at 2.4 s (Speed Index), inside the 3.4 s “good” threshold.

  • Cumulative Layout Shift: 0.025

    0.025

    The layout barely moves while loading (CLS 0.025, good is under 0.1).

Images and page weight

100
  • 1 image below the first screen load straight away

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

  • About 0.5 g of CO₂ per visit

    0.54 g

    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.

3 checks passed
  • Page weight: 1.9 MB in 109 requests

    1.9 MB

    Your homepage downloads 1.9 MB in 109 requests on a phone: scripts 790 KiB (15), other files 721 KiB (76) and images 304 KiB (12). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 8994
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Headings should not be empty (3 elements)

    Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 43 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9288
  • Title is long (83 characters)

    Your title is 83 characters, so Google will cut it off around 60: “Thunder Bay Catch the Ace Lottery – Thunder Bay Regional Health Sciences Foundation”.

  • Meta description is long (166 characters)

    Your meta description is 166 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 23 internal links, 5 external

    The homepage links to 23 pages on thunderbaycatchtheace.ca and 5 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “<img src="//thunderbaycatchtheace.ca/cdn/shop/files/Header_Logo_6fdd2ebd-1a17-4c52-ad0b-6af7719231b3_155x.png?v=1738186…”.

  • Canonical URL set

    The canonical URL is https://thunderbaycatchtheace.ca/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://thunderbaycatchtheace.ca/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (445 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://thunderbaycatchtheace.ca/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without a meta description

    https://thunderbaycatchtheace.ca/pages/winners has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://thunderbaycatchtheace.ca/pages/winners has 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.

  • 6 internal pages checked

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

6 checks passed
  • Linked pages load

    5 pages of 6 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 5 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    11 of 12 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

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

  • Local business without LocalBusiness data

    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.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 402 words of copy

    The homepage carries about 402 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “BUY TICKETS”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Buy Tickets”.

  • 4 short forms

    4 short forms (0 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Meta Pixel.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Meta Pixel (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.

  • 7 cookies set on arrival

    7

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

  • No consent tool detected

    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.

  • 8 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at thunderbaycatchtheace.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

No apps were seen in the code your storefront loads.

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 22 issues on thunderbaycatchtheace.ca, including 11 speed issues, 2 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25