northmedicalspa.com website review

11 images could be 4.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

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

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

website-files.com costs a phone 118 ms of main-thread work and 6.1 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.

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

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

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

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

Google CDN costs a phone 184 ms of main-thread work and 354 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 20 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 13 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.

5 KiB could be saved by minifying CSS.

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

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

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

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

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

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

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

Your homepage downloads 7.6 MB in 54 requests on a phone: images 5.6 MB (16), scripts 1.5 MB (16) and fonts 493 KiB (8). Under 2 MB keeps phones on slow connections fast.

61b11f19c13de22bdaf67a56_Untitled design (31)-p-500.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

5 images (938 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.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 14 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.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

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.

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

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

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

The homepage links to 102 pages on northmedicalspa.com and 27 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 https://www.northmedicalspa.com/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.northmedicalspa.com/treatments/skin-rescue-facial, https://www.northmedicalspa.com/treatments/teen-facial, https://www.northmedicalspa.com/treatments/express-hydrafacial, https://www.northmedicalspa.com/treatments/express-bbl and https://www.northmedicalspa.com/treatments/express-chemical-peel have no <title>, so Google invents the link text in results.

https://www.northmedicalspa.com/location/toronto and https://www.northmedicalspa.com/location/collingwood all use the title “North Medical Spa”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.northmedicalspa.com/book-a-consultation, https://www.northmedicalspa.com/location/toronto, https://www.northmedicalspa.com/location/collingwood, https://www.northmedicalspa.com/treatments/skin-rescue-facial, https://www.northmedicalspa.com/treatments/teen-facial and https://www.northmedicalspa.com/treatments/express-hydrafacial and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

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

Large scripts ship without source maps.

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.

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

The homepage has only about 214 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

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