Report Summary

  • 65

    Performance

    Renders faster than
    79% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 95

    SEO

    Google-friendlier than
    91% of websites

davidlesieur.com

David Lesieur // Analyste-programmeur et chargé de projets // Montréal, Québec

Page Load Speed

1.2 sec in total

First Response

197 ms

Resources Loaded

573 ms

Page Rendered

471 ms

davidlesieur.com screenshot

About Website

Visit davidlesieur.com now to see the best up-to-date David Lesieur content and also check out these interesting facts you probably never knew about davidlesieur.com

Ceci est le blogue de David Lesieur, analyste-programmeur et chargé de projets chez Whisky Echo Bravo et basé à Montréal. S’il n’est pas en ce moment en train de façonner un système d’information avec...

Visit davidlesieur.com

Key Findings

We analyzed Davidlesieur.com page load time and found that the first response time was 197 ms and then it took 1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

davidlesieur.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

62/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value7.9 s

43/100

10%

Network Requests Diagram

davidlesieur.com

197 ms

pure.grids-min.css

78 ms

pure.grids-responsive-min.css

79 ms

main.css

85 ms

mousetrap.min.js

104 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that 82% of them (14 requests) were addressed to the original Davidlesieur.com, 12% (2 requests) were made to Google-analytics.com and 6% (1 request) were made to Davidlesieur.disqus.com. The less responsive or slowest element that took the longest time to load (265 ms) relates to the external source Davidlesieur.disqus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 53.9 kB (38%)

Content Size

143.7 kB

After Optimization

89.7 kB

In fact, the total size of Davidlesieur.com main page is 143.7 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. 20% of websites need less resources to load. Images take 60.1 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 21.6 kB

  • Original 30.7 kB
  • After minification 28.3 kB
  • After compression 9.1 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 21.6 kB or 70% of the original size.

Image Optimization

-1%

Potential reduce by 335 B

  • Original 60.1 kB
  • After minification 59.7 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. David Lesieur images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.9 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 32.0 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (30%)

Requests Now

10

After Optimization

7

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

Accessibility Review

davidlesieur.com accessibility score

96

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.

Best Practices

davidlesieur.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

davidlesieur.com SEO score

95

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Davidlesieur.com 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 Davidlesieur.com 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

Open Graph description is not detected on the main page of David Lesieur. 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: