Website review, no card needed

thecanadianpress.com logo

thecanadianpress.com website review

Visit site (opens in a new tab)Reviewed 28 October 202639 issues · 86 checks

This review found 39 issues worth fixing on thecanadianpress.com, 16 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. 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
1.7 s1.4 sMay 9Oct 241.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.4 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.6 s
Oct 24, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
135 ms108 msMay 9Oct 24129 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026113 ms
May 16, 2026112 ms
May 23, 2026112 ms
May 30, 2026111 ms
Jun 6, 2026113 ms
Jun 13, 2026113 ms
Jun 20, 2026113 ms
Jun 27, 2026119 ms
Jul 4, 2026121 ms
Jul 11, 2026120 ms
Jul 18, 2026119 ms
Jul 25, 2026120 ms
Aug 1, 2026120 ms
Aug 8, 2026121 ms
Aug 15, 2026124 ms
Aug 22, 2026120 ms
Aug 29, 2026121 ms
Sep 5, 2026124 ms
Sep 12, 2026128 ms
Sep 19, 2026130 ms
Sep 26, 2026131 ms
Oct 3, 2026129 ms
Oct 10, 2026132 ms
Oct 17, 2026129 ms
Oct 24, 2026129 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 thecanadianpress.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thecanadianpress.com at 0.4 s0.4 s
  2. thecanadianpress.com at 0.8 s0.8 s
  3. thecanadianpress.com at 1.1 s1.1 s
  4. thecanadianpress.com at 1.5 s1.5 s
  5. thecanadianpress.com at 1.9 s1.9 s
  6. thecanadianpress.com at 2.3 s2.3 s
  7. thecanadianpress.com at 2.6 s2.6 s
  8. thecanadianpress.com at 3.0 s3.0 s

Speed

11 to fix32
  • Use efficient cache lifetimes

    2.7 s · 624 KiB

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

  • Reduce unused JavaScript

    1.6 s · 894 KiB

    About 894 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: 32

    32/100

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

  • 8 third-party services on the page

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

  • Improve image delivery

    300 ms · 508 KiB

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

  • Minify JavaScript

    450 ms · 97 KiB

    97 KiB could be saved by minifying JavaScript.

  • Google CDN adds 383 ms

    383 ms

    Google CDN costs a phone 383 ms of main-thread work and 1.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.

  • Main-thread work: 3.7 s

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

  • Reduce unused CSS

    300 ms · 72 KiB

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

  • Render-blocking requests

    300 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

  • Google Tag Manager adds 231 ms

    231 ms

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

  • 18 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 12 KiB

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

  • Font display

    50 ms

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

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

    21 ms

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

Core Web Vitals

8 to fix67
  • 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.

  • Real-user CLS: 0.59

    0.59

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

  • Largest Contentful Paint: 14.9 s

    14.9 s

    Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CANADA'S TRUSTED NEWS LEADER Get alerted in real time to fu…”.

  • Time to Interactive: 22.4 s

    22.4 s

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

  • Cumulative Layout Shift: 0.5

    0.5

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Total Blocking Time: 658 ms

    658 ms

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

  • 21 images without width and height

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

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

    +15%

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

  • Largest content (LCP) got 13% slower for real visitors

    +13%

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

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 130 ms

    130 ms

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

  • Real-user FCP: 1.1 s

    1.1 s

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

  • Real-user TTFB: 616 ms

    616 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

Images and page weight

2 to fix60
  • Page weight: 4.5 MB in 251 requests

    4.5 MB

    Your homepage downloads 4.5 MB in 251 requests on a phone: scripts 2.3 MB (54), images 1.3 MB (113) and other files 400 KiB (56). Under 2 MB keeps phones on slow connections fast.

  • 5 images in older formats

    5 images (711 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 below the first screen load straight away

    1 image further down the page (58 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.27 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

9 to fixGoogle 7989
  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • 12 text elements with low contrast

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

  • ARIA input fields must have an accessible name (2 elements)

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

  • 4 images without alt text

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

  • All page content should be contained by landmarks (25 elements)

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

  • No main landmark

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

  • 3 links without text

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

  • 1 form field without a label

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

  • 1 tap target too small

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

  • <td> elements in a large <table> do not have table headers.

    <td> elements in a large <table> do not have table headers. (1 element).

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 9288
  • 2 H1 headlines

    There are 2 <h1> headlines (“CANADA'S TRUSTED NEWS LEADER” and “CANADA'S TRUSTED NEWS LEADER”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token 'C', ..." "@type": Corporatio"... is not va)”.

  • No social preview image

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

  • 139 internal links, 9 external

    The homepage links to 139 pages on thecanadianpress.com and 9 external pages.

5 checks passed
  • Meta description: 139 characters

    Your meta description is 139 characters: “The Canadian Press offers multimedia news; custom freelance writing, photography & videography; media monitoring; conte…”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “The Canadian Press | Canada's Trusted News Leader”.

  • Canonical URL set

    The canonical URL is https://www.thecanadianpress.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.thecanadianpress.com/sitemap.xml.

AI search readiness

1 to fix65
  • robots.txt blocks 5 AI answer engine crawlers

    5 of 6

    Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • No llms.txt

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

2 checks passed
  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,220 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://www.thecanadianpress.com/content-services/newsfeed-subscription/digital-signage-content-feeds and https://www.thecanadianpress.com/multimedia/cp-images-platform have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.thecanadianpress.com/multimedia/cp-images-platform has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 9 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

    The homepage carries about 939 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “GET FREE DEMO”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “GET FREE DEMO” and “Try our media monitoring”.

  • 2 short forms

    2 short forms (7 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 45 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (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.

  • 11 cookies set on arrival

    11

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

  • No consent tool detected

    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.

  • 37 other companies contacted

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

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
AWS

Hiring

Hiring
1 open role
Teams
Editorial (1)
Job board
workable

Company

Founded
1917
Headquarters
Toronto

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on thecanadianpress.com, including 19 speed issues and 3 SEO issues. 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