getmaple.ca website review

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

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

Your mobile performance score is 56 (desktop: 79). Pages that score under 90 lose visitors before the first paint.

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

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

1 file is served with short cache lifetimes, so returning visitors download them again (33 KiB).

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

3 third-party services load with your homepage (Cookiebot, Bing Ads and Google Tag Manager), adding 217 KiB and 127 ms of main-thread time.

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

Your largest element takes 12.0 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 15.0 s. Good is under 3.8 s.

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

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

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

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

Your homepage downloads 8.3 MB in 58 requests on a phone: media 5.3 MB (1), images 1.4 MB (18) and scripts 1.1 MB (34). Under 2 MB keeps phones on slow connections fast.

health-yeah-screengrab-1_5x-1.jpg weighs 524 KiB. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example health-yeah-screengrab-1_5x-1.jpg at 2,880 px wide, shown at 390 px. Resized copies would save about 449 KiB.

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

Some list items are not inside a list.

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

Your title is 84 characters, so Google will cut it off around 60: “Online Doctor Appointments, Consultations, and Prescriptions in Canada, 24/7 | Maple”.

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

The homepage links to 107 pages on getmaple.ca and 14 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), 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.

There is no /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.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=25139354&tm=gtm002&Ver=2&mid=9b5c85ac-370f-4772-a5c1-cd0b24bcbf27&bo=1&sid=61b8b5e0d25211f1a93417034e7c97cf&vid=61b8f690d25211f1815b6b9048847bd6&vids=1&msclkid=N&pi=91.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 180 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

Your security.txt expired on 2023-06-01, so researchers may not trust its contact details.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

getmaple.ca has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

getmaple.ca's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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 2,126 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Tag Manager and Microsoft Ads (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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