mhlab.ca website review

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

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

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

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

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 2.7 MB and 828 ms of main-thread time.

About 121 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

51 KiB could be saved by minifying JavaScript.

YouTube costs a phone 339 ms of main-thread work and 1.7 MB 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.

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

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

13 KiB could be saved by minifying CSS.

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

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

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

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 17.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Medical Diagnostic Laboratory”.

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

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

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

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

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

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

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

11 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-17, real Chrome visitors' tap response (inp) went from 87 ms to 90 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.9 MB in 104 requests on a phone: scripts 2.5 MB (36), images 2.4 MB (25) and fonts 631 KiB (10). Under 2 MB keeps phones on slow connections fast.

Thing-you-can-do-online.jpg weighs 658 KiB. On a phone connection a single image that size takes seconds.

7 images (961 KiB) 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.

1 image is downloaded at several times the size a phone draws it, for example Thing-you-can-do-online.jpg at 1,123 px wide, shown at 300 px. Resized copies would save about 235 KiB.

5 images further down the page (182 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.67 g of CO₂e: 199.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

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

The homepage links to 35 pages on mhlab.ca and 1 external page.

There is no https://www.mhlab.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.

https://www.mhlab.ca/locations/toronto and https://www.mhlab.ca/locations/vaughan use the same meta description. A description written for each page earns more clicks.

https://www.mhlab.ca/appointment, https://www.mhlab.ca/services/patient and https://www.mhlab.ca/health-care-provider have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.mhlab.ca/appointment, https://www.mhlab.ca/make-payment, https://www.mhlab.ca/services, https://www.mhlab.ca/services/patient, https://www.mhlab.ca/health-care-provider and https://www.mhlab.ca/services/patient-results-portal and 9 others took over 3 s to send their HTML from our server.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

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

1 error was logged to the browser console while the page loaded, for example “SecurityError: Failed to read the 'cssRules' property from 'CSSStyleSheet': Cannot access rules https://www.mhlab.ca/wp…”.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 2 testimonial or review blocks. 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.

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

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

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

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.

Opening the homepage sets 8 cookies, 1 of them by other companies (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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.