Tools & Wizards About Us
necrologie.lapresse.ca screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

necrologie.lapresse.ca

LaPresse.ca | Actualités et Infos au Québec et dans le monde

Page Load Speed

723 ms in total

First Response

37 ms

Resources Loaded

614 ms

Page Rendered

72 ms

necrologie.lapresse.ca screenshot

About Website

Click here to check amazing Necrologie La Presse content for Canada. Otherwise, check out these important facts you probably never knew about necrologie.lapresse.ca

'Le site d\'information francophone le plus complet en Amérique du Nord: Actualités régionales, provinciales, nationales et internationales.

Visit necrologie.lapresse.ca

Key Findings

We analyzed Necrologie.lapresse.ca page load time and found that the first response time was 37 ms and then it took 686 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

necrologie.lapresse.ca performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value5,190 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.06

98/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

Network Requests Diagram

necrologie.lapresse.ca

37 ms

necrologie.lapresse.ca

91 ms

dataLayerEventSubscriber.js

62 ms

app.bundle.js

97 ms

styles.css

87 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 38% of them (13 requests) were addressed to the original Necrologie.lapresse.ca, 24% (8 requests) were made to Static.lapresse.ca and 18% (6 requests) were made to Static.lpcdn.ca. The less responsive or slowest element that took the longest time to load (302 ms) relates to the external source Js-sec.indexww.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 45.1 kB (13%)

Content Size

345.4 kB

After Optimization

300.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Necrologie.lapresse.ca main page is 345.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 259.2 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 19.9 kB

  • Original 27.7 kB
  • After minification 25.0 kB
  • After compression 7.8 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 19.9 kB or 72% of the original size.

JavaScript Optimization

-1%

Potential reduce by 3.0 kB

  • Original 259.2 kB
  • After minification 259.2 kB
  • After compression 256.2 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-38%

Potential reduce by 22.3 kB

  • Original 58.6 kB
  • After minification 58.6 kB
  • After compression 36.3 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Necrologie.lapresse.ca needs all CSS files to be minified and compressed as it can save up to 22.3 kB or 38% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (83%)

Requests Now

23

After Optimization

4

  • AJAX
  • JavaScript
  • CSS

The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Necrologie La Presse. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

necrologie.lapresse.ca

necrologie.lapresse.ca

37 ms

necrologie.lapresse.ca

necrologie.lapresse.ca

91 ms

dataLayerEventSubscriber.js

dataLayerEventSubscriber.js

62 ms

app.bundle.js

app.bundle.js

97 ms

styles.css

styles.css

87 ms

page_20231121.css

page_20231121.css

55 ms

overHeader_20231121.css

overHeader_20231121.css

96 ms

header_20231121.css

header_20231121.css

118 ms

cyberpresse-necrologie_20231121.css

cyberpresse-necrologie_20231121.css

133 ms

googletagmanager.js

googletagmanager.js

63 ms

183806-80690130798415.js

183806-80690130798415.js

302 ms

gpt.js

gpt.js

134 ms

necro.js

necro.js

119 ms

necroTexte.js

necroTexte.js

133 ms

calendar.js

calendar.js

119 ms

calendar-fr.js

calendar-fr.js

138 ms

calendar-setup.js

calendar-setup.js

149 ms

subBody_externe.js

subBody_externe.js

63 ms

footer_20231121.css

footer_20231121.css

286 ms

_chapitre_special.css

_chapitre_special.css

32 ms

rubrik.css

rubrik.css

24 ms

robotoserif.css

robotoserif.css

65 ms

calendar-blue2.css

calendar-blue2.css

55 ms

gtm.js

gtm.js

151 ms

pubads_impl.js

pubads_impl.js

60 ms

Rubrik-Regular.woff

Rubrik-Regular.woff

39 ms

Rubrik-Medium.woff

Rubrik-Medium.woff

40 ms

Rubrik-Light.woff

Rubrik-Light.woff

51 ms

Rubrik-ExtraLight.woff

Rubrik-ExtraLight.woff

52 ms

Rubrik-SemiBold.woff

Rubrik-SemiBold.woff

52 ms

Rubrik-Bold.woff

Rubrik-Bold.woff

52 ms

rid

rid

160 ms

any

any

163 ms

beacon.js

beacon.js

4 ms

Accessibility Review

necrologie.lapresse.ca accessibility score

82

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

necrologie.lapresse.ca best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

necrologie.lapresse.ca SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Necrologie.lapresse.ca can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Necrologie.lapresse.ca main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

necrologie.lapresse.ca

Open Graph description is not detected on the main page of Necrologie La Presse. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: