cheo5050.ca website review

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

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

About 416 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 480 ms faster on a phone.

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

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

Google CDN costs a phone 113 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 load with your homepage (Google CDN, weglot.com and Clarity and others), adding 716 KiB and 361 ms of main-thread time.

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

About 19 KiB of CSS is downloaded but never applied on this page.

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 KiB could be saved by minifying JavaScript.

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

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 2.4 MB in 122 requests on a phone: scripts 806 KiB (24), images 724 KiB (9) and other files 724 KiB (83). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (24 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 0.67 g of CO₂e: 80.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

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

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 23 characters: “CHEO 50/50 – CHEO 50-50”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 60 characters: “Buy your 50/50 raffle tickets in support of CHEO Foundation.”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 11 pages on cheo5050.ca and 4 external pages.

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.

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

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

1 error was logged to the browser console while the page loaded, for example “Unexpected token '}'”.

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

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

There is no form on the homepage, so every lead has to click through to another page first.

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

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

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

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.

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