Website review, no card needed

guelphstorm.com logo

guelphstorm.com website review

Visit site (opens in a new tab)Reviewed 21 November 202650 issues · 91 checks

This review found 50 issues worth fixing on guelphstorm.com, 23 of them high impact, across 91 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
2.6 s1.4 sMay 30Nov 141.7 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.5 s
Jun 27, 20261.6 s
Jul 4, 20261.9 s
Jul 11, 20262.2 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.2 s
Sep 5, 20262.0 s
Sep 12, 20261.9 s
Sep 19, 20261.8 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.8 s
Nov 7, 20261.7 s
Nov 14, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
139 ms120 msMay 30Nov 14128 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026125 ms
Jun 6, 2026123 ms
Jun 13, 2026122 ms
Jun 20, 2026123 ms
Jun 27, 2026123 ms
Jul 4, 2026127 ms
Jul 11, 2026130 ms
Jul 18, 2026134 ms
Jul 25, 2026137 ms
Aug 1, 2026137 ms
Aug 8, 2026135 ms
Aug 15, 2026135 ms
Aug 22, 2026136 ms
Aug 29, 2026136 ms
Sep 5, 2026134 ms
Sep 12, 2026134 ms
Sep 19, 2026135 ms
Sep 26, 2026136 ms
Oct 3, 2026136 ms
Oct 10, 2026135 ms
Oct 17, 2026133 ms
Oct 24, 2026131 ms
Oct 31, 2026130 ms
Nov 7, 2026129 ms
Nov 14, 2026128 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 guelphstorm.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. guelphstorm.com at 0.6 s0.6 s
  2. guelphstorm.com at 1.1 s1.1 s
  3. guelphstorm.com at 1.7 s1.7 s
  4. guelphstorm.com at 2.2 s2.2 s
  5. guelphstorm.com at 2.8 s2.8 s
  6. guelphstorm.com at 3.4 s3.4 s
  7. guelphstorm.com at 3.9 s3.9 s
  8. guelphstorm.com at 4.5 s4.5 s

Speed

11 to fix15
  • Reduce unused JavaScript

    7.0 s · 1.7 MB

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

  • Render-blocking requests

    2.8 s

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

  • Reduce unused CSS

    1.1 s · 188 KiB

    About 188 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 15

    15/100

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

  • Main-thread work: 5.0 s

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

  • 4,457 HTML elements

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

  • Improve image delivery

    36.1 MB

    63 images could be 36.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    450 ms · 4.9 MB

    84 files are served with short cache lifetimes, so returning visitors download them again (4.9 MB).

  • 16 long tasks on the main thread

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

  • Google Tag Manager adds 232 ms

    232 ms

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

  • Google CDN adds 81 ms

    81 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 916 KiB and 410 ms of main-thread time.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    11 KiB

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

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 10 ms

    10 ms

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

Core Web Vitals

10 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user CLS: 1.39

    1.39

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

  • Cumulative Layout Shift: 1.349

    1.349

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

  • Largest Contentful Paint: 41.2 s

    41.2 s

    Your largest element takes 41.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Speed Index: 22.6 s

    22.6 s

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

  • Time to Interactive: 43.3 s

    43.3 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Total Blocking Time: 745 ms

    745 ms

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) got 13% slower for real visitors

    +13%

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

3 checks passed
  • Real-user INP: 159 ms

    159 ms

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 406 ms

    406 ms

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

Images and page weight

4 to fix38
  • Page weight: 45.2 MB in 243 requests

    45.2 MB

    Your homepage downloads 45.2 MB in 243 requests on a phone: images 41.8 MB (130), scripts 2.9 MB (79) and stylesheets 264 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • 19 images over 500 KB

    19 images weigh 18.7 MB together. On a phone connection a single image that size takes seconds.

  • 40 images in older formats

    40 images (22.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 15 images below the first screen load straight away

    15 images further down the page (13.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 12.8 g of CO₂ per visit

    12.80 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

13 to fixGoogle 7684
  • 111 text elements with low contrast

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

  • Hidden but focusable

    7 elements hidden from screen readers can still receive keyboard focus.

  • Orphan list items

    Some list items are not inside a list.

  • 3 tap targets too small

    3 tap targets are too small or too close together to hit reliably with a finger.

  • 34 images without alt text

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

  • All page content should be contained by landmarks (106 elements)

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

  • 120 links without text

    120 visible links have no text or label, so screen readers cannot say where they go.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

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

  • Main landmark should not be contained in another landmark (1 element)

    Main 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 main landmark (1 element)

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

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

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

4 to fixGoogle 7771
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • Title is short (14 characters)

    Your title is only 14 characters: “Guelph Storm -”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 8 links with vague text

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 496 internal links, 39 external

    The homepage links to 496 pages on guelphstorm.com and 39 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://chl.ca/ohl-storm/.

  • Structured data in place

    Structured data found: BreadcrumbList, CollectionPage and WebSite.

  • 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://chl.ca/sitemap_index.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://chl.ca/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.

2 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 (1,969 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 11 pages without a meta description

    https://chl.ca/whl-wheatkings, https://chl.ca/whl-hitmen, https://chl.ca/whl-oilkings, https://chl.ca/whl-silvertips, https://chl.ca/whl-blazers and https://chl.ca/whl-hurricanes and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://chl.ca/whl, https://chl.ca/whl-hitmen, https://chl.ca/whl-oilkings, https://chl.ca/whl-silvertips, https://chl.ca/whl-blazers and https://chl.ca/whl-rockets and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 85 small tap targets

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

  • 2 JavaScript errors while loading

    2 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 ()”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

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

  • No direct contact details

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

  • 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 1,925 words of copy

    The homepage carries about 1,925 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “FULL SCHEDULE” and “Schedule”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Schedule”, “2026/2027 Printable Schedule” and “2026/2027 Promotional Schedule”.

  • 3 short forms

    3 short forms (5 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and 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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 cookies, 1 of them by other companies (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.

  • 14 other companies contacted

    Loading the homepage contacts 14 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 guelphstorm.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
React
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

Company

Headquarters
Guelph

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on guelphstorm.com, including 21 speed issues, 4 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