lapresse.ca website review

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

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

Your mobile performance score is 44. 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, lpcdn.ca and Google/Doubleclick Ads and others), adding 3.1 MB and 1.3 s of main-thread time.

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

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

lpcdn.ca costs a phone 281 ms of main-thread work and 2.0 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 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.

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

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

Google/Doubleclick Ads costs a phone 268 ms of main-thread work and 308 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.

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

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

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

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.

Your largest element takes 19.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Quatre scénarios pour les midterms”.

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

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

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

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

5 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 80 ms to 87 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 1.1 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.4 MB in 221 requests on a phone: scripts 1.7 MB (33), other files 566 KiB (96) and fonts 524 KiB (24). Under 2 MB keeps phones on slow connections fast.

1 image (44 KiB) is 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 further down the page (22 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

Input buttons must have discernible text: 1 element on the page fails this check, rated critical by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“La Presse” and “La Presse”). One clear main headline is easier for people and search engines.

Structured data found (NewsMediaOrganization and WebSite) but with 1 problem, for example “WebSite: missing name”.

The homepage links to 443 pages on lapresse.ca and 41 external pages.

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

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

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.

https://www.lapresse.ca/renseignements/2023-08-02/fin-de-l-acces-aux-nouvelles-sur-facebook-instagram-et-google/comment-continuer-de-vous-informer-efficacement-et-gratuitement.php, https://www.lapresse.ca/actualites, https://www.lapresse.ca/international, https://www.lapresse.ca/dialogue, https://www.lapresse.ca/affaires and https://www.lapresse.ca/sports and 7 others have no <title>, so Google invents the link text in results.

https://www.lapresse.ca/mon-compte/profil is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.lapresse.ca/renseignements/2023-08-02/fin-de-l-acces-aux-nouvelles-sur-facebook-instagram-et-google/comment-continuer-de-vous-informer-efficacement-et-gratuitement.php, https://www.lapresse.ca/actualites, https://www.lapresse.ca/international, https://www.lapresse.ca/dialogue, https://www.lapresse.ca/affaires and https://www.lapresse.ca/sports and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lapresse.ca/renseignements/2023-08-02/fin-de-l-acces-aux-nouvelles-sur-facebook-instagram-et-google/comment-continuer-de-vous-informer-efficacement-et-gratuitement.php, https://www.lapresse.ca/contribution, https://www.lapresse.ca/actualites, https://www.lapresse.ca/international, https://www.lapresse.ca/dialogue and https://www.lapresse.ca/affaires and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.lapresse.ca/contribution, https://www.lapresse.ca/auto, https://www.lapresse.ca/arts and https://www.lapresse.ca/cinema took over 3 s to send their HTML from our server.

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

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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 1,602 words of visible text.

Before a visitor clicks anything, the page loads Comscore, Google Ads, Google Analytics, Google Tag Manager and Reddit 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 14 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 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.