Website review, no card needed

canadapost.ca logo

canadapost.ca website review

Visit site (opens in a new tab)Reviewed 7 November 202644 issues · 89 checks

This review found 44 issues worth fixing on canadapost.ca, 10 of them high impact, across 89 checks. The most urgent: render-blocking requests. 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.8 s2.5 sMay 16Oct 312.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.6 s
May 23, 20262.7 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.7 s
Jun 20, 20262.7 s
Jun 27, 20262.7 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.8 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.7 s
Oct 24, 20262.7 s
Oct 31, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
159 ms118 msMay 16Oct 31152 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026123 ms
May 23, 2026124 ms
May 30, 2026125 ms
Jun 6, 2026126 ms
Jun 13, 2026127 ms
Jun 20, 2026128 ms
Jun 27, 2026129 ms
Jul 4, 2026133 ms
Jul 11, 2026137 ms
Jul 18, 2026142 ms
Jul 25, 2026145 ms
Aug 1, 2026147 ms
Aug 8, 2026149 ms
Aug 15, 2026151 ms
Aug 22, 2026153 ms
Aug 29, 2026154 ms
Sep 5, 2026154 ms
Sep 12, 2026154 ms
Sep 19, 2026154 ms
Sep 26, 2026154 ms
Oct 3, 2026154 ms
Oct 10, 2026154 ms
Oct 17, 2026154 ms
Oct 24, 2026153 ms
Oct 31, 2026152 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 canadapost.ca (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. canadapost.ca at 0.4 s0.4 s
  2. canadapost.ca at 0.8 s0.8 s
  3. canadapost.ca at 1.1 s1.1 s
  4. canadapost.ca at 1.5 s1.5 s
  5. canadapost.ca at 1.9 s1.9 s
  6. canadapost.ca at 2.3 s2.3 s
  7. canadapost.ca at 2.7 s2.7 s
  8. canadapost.ca at 3.1 s3.1 s

Speed

12 to fix37
  • Render-blocking requests

    3.9 s

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

  • Reduce unused JavaScript

    1.6 s · 610 KiB

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

  • Mobile performance score: 37

    37/100

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

  • Improve image delivery

    150 ms · 2.2 MB

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

  • Use efficient cache lifetimes

    950 ms · 586 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (reddit, Facebook and Adobe Tag Manager and others), adding 1.2 MB and 1.3 s of main-thread time.

  • Reduce unused CSS

    300 ms · 268 KiB

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

  • Main-thread work: 3.8 s

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

  • reddit adds 356 ms

    356 ms

    reddit costs a phone 356 ms of main-thread work and 28 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.

  • Legacy JavaScript

    300 ms · 39 KiB

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

  • Facebook adds 264 ms

    264 ms

    Facebook costs a phone 264 ms of main-thread work and 284 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.

  • 2,015 HTML elements

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

  • 12 long tasks on the main thread

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

  • Document request latency

    151 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify JavaScript

    79 KiB

    79 KiB could be saved by minifying JavaScript.

  • 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: 303 ms

    303 ms

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

Core Web Vitals

11 to fix100
  • 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.

  • Largest Contentful Paint: 17.8 s

    17.8 s

    Your largest element takes 17.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “ll phone screen displays the MyMail page of the Canada Post…”.

  • Time to Interactive: 31.7 s

    31.7 s

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

  • First Contentful Paint: 6.6 s

    6.6 s

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

  • Speed Index: 11.0 s

    11.0 s

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

  • Tap response (INP) got 23% slower for real visitors

    +23%

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 861 ms

    861 ms

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

  • Total Blocking Time: 550 ms

    550 ms

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

  • Cumulative Layout Shift: 0.133

    0.133

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

  • 6 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

3 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 131 ms

    131 ms

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

  • Real-user CLS: 0.01

    0.01

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

Images and page weight

5 to fix28
  • Page weight: 6.8 MB in 137 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 137 requests on a phone: images 4.5 MB (58), scripts 1.6 MB (33) and stylesheets 264 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 2.6 MB together. On a phone connection a single image that size takes seconds.

  • 12 images in older formats

    12 images (3.2 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.

  • 10 images below the first screen load straight away

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

  • 2 images far larger than shown

    196 KiB

    2 images are downloaded at several times the size a phone draws them, for example CCMOPC-38790-image-2-desktop.png at 1,200 px wide, shown at 358 px. Resized copies would save about 196 KiB.

  • About 1.9 g of CO₂ per visit

    1.92 g

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

Accessibility

2 to fixGoogle 9597
  • 128 links without text

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

  • Zoom is disabled

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 34 images in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

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

SEO

5 to fixGoogle 8585
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Make life easier with our mobile app” and “Make tracking your packages easier with our mobil…”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 1 link with vague text

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

  • No X (Twitter) card tag

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

  • 24 internal links, 7 external

    The homepage links to 24 pages on canadapost.ca and 7 external pages.

5 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Mail letters, ship parcels, market your business and sell online with Canada Post. We offer services for individuals an…”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Mailing and shipping for Personal and Business | Canada Post”.

  • Canonical URL set

    The canonical URL is https://www.canadapost-postescanada.ca/cpc/en/home.page.

  • 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://www.canadapost-postescanada.ca/cpc/doc/en/sitemap/sitemap.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://www.canadapost-postescanada.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 (512 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.canadapost-postescanada.ca/cpc/en/our-company/news-and-media/corporate-news/closures-and-service-interruptions-list.page is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://www.canadapost-postescanada.ca/track-reperage/en, https://www.canadapost-postescanada.ca/cpc/en/tools/find-a-rate.page and https://www.canadapost-postescanada.ca/cpc/en/tools/find-a-post-office.page have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.canadapost-postescanada.ca/track-reperage/en, https://www.canadapost-postescanada.ca/cpc/en/tools/find-a-rate.page and https://www.canadapost-postescanada.ca/cpc/en/tools/find-a-post-office.page have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://www.canadapost-postescanada.ca/cpc/en/personal/manage-mail/automatic-tracking.page, https://www.canadapost-postescanada.ca/cpc/en/support/kb/tracking/delivery-notifications.page, https://www.canadapost-postescanada.ca/cpc/en/personal/money-transfers.page, https://www.canadapost-postescanada.ca/cpc/en/personal/mymail.page, https://www.canadapost-postescanada.ca/cpc/en/our-company/news-and-media/service-alerts.page and https://www.canadapost-postescanada.ca/cpc/en/our-company/news-and-media/corporate-news/closures-and-service-interruptions-list.page took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 5894
  • 3 third-party cookies

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

  • Deprecated browser APIs

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

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    183 of 192 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 2 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 680 words of copy

    The homepage carries about 680 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Buy stamps and packaging” and “Schedule a home pickup”.

  • 7 calls to action

    The homepage has 7 calls to action, for example “Sign up for free”, “Learn more” and “Shop now”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

  • 5 trackers load before any consent

    5

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

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 cookies, 3 of them by other companies (measured from a US location before any click).

  • 21 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 canadapost.ca, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Hosting
CloudFront

Company

Employees
72,000
Founded
1867
Headquarters
Ottawa

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on canadapost.ca, including 23 speed issues, 5 SEO issues and 3 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