Tools & Wizards About Us
pourquoipas.ca screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

pourquoipas.ca

Alex Roof | creating de nouveaux pranks exclusifs chaque semaine! | Patreon

Page Load Speed

2.3 sec in total

First Response

35 ms

Resources Loaded

2.2 sec

Page Rendered

105 ms

pourquoipas.ca screenshot

About Website

Welcome to pourquoipas.ca homepage info - get ready to check Pourquoipas best content for Canada right away, or after learning these important things about pourquoipas.ca

creating de nouveaux pranks exclusifs chaque semaine!

Visit pourquoipas.ca

Key Findings

We analyzed Pourquoipas.ca page load time and found that the first response time was 35 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

pourquoipas.ca performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value15.3 s

0/100

25%

SI (Speed Index)

Value16.8 s

0/100

10%

TBT (Total Blocking Time)

Value9,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value37.4 s

0/100

10%

Network Requests Diagram

pourquoipas.ca

35 ms

pourquoipas.ca

359 ms

alexroof

662 ms

polyfills-c67a75d1b6f99dc8.js

102 ms

airgap.js

120 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Pourquoipas.ca, 76% (55 requests) were made to C13.patreon.com and 8% (6 requests) were made to C10.patreonusercontent.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source C10.patreonusercontent.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 279.8 kB (12%)

Content Size

2.3 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Pourquoipas.ca main page is 2.3 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. Javascripts take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 277.0 kB

  • Original 389.3 kB
  • After minification 389.1 kB
  • After compression 112.3 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 277.0 kB or 71% of the original size.

Image Optimization

-1%

Potential reduce by 731 B

  • Original 126.2 kB
  • After minification 125.5 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. Pourquoipas images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.1 kB

  • Original 1.8 MB
  • After minification 1.8 MB
  • After compression 1.8 MB

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.

Requests Breakdown

Number of requests can be reduced by 61 (88%)

Requests Now

69

After Optimization

8

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

pourquoipas.ca

pourquoipas.ca

35 ms

pourquoipas.ca

pourquoipas.ca

359 ms

alexroof

alexroof

662 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

102 ms

airgap.js

airgap.js

120 ms

api:client.js

api:client.js

98 ms

client

client

139 ms

appleid.auth.js

appleid.auth.js

91 ms

webpack-b314751d38562619.js

webpack-b314751d38562619.js

117 ms

framework-5b4b4bd7d64ffcfa.js

framework-5b4b4bd7d64ffcfa.js

129 ms

main-bba07c0d56e4f500.js

main-bba07c0d56e4f500.js

128 ms

_app-0f823414b6f74fb3.js

_app-0f823414b6f74fb3.js

218 ms

2852872c-657a224261f762b2.js

2852872c-657a224261f762b2.js

134 ms

37a763b4-eaaabd946be5e1fa.js

37a763b4-eaaabd946be5e1fa.js

205 ms

f9afc4fe-6059a26458ac411b.js

f9afc4fe-6059a26458ac411b.js

134 ms

8b11cd73-f09294707b04d014.js

8b11cd73-f09294707b04d014.js

195 ms

fc56bfa5-e49782f58abae3cb.js

fc56bfa5-e49782f58abae3cb.js

194 ms

30381-6e8e8def86fca9d9.js

30381-6e8e8def86fca9d9.js

196 ms

58588-e0e06435aa683efe.js

58588-e0e06435aa683efe.js

192 ms

91036-75f9a70fd050d3a3.js

91036-75f9a70fd050d3a3.js

198 ms

47903-998e8a1dd055161e.js

47903-998e8a1dd055161e.js

196 ms

12066-b08ba835f0c43116.js

12066-b08ba835f0c43116.js

199 ms

24785-5f45b994dbed1273.js

24785-5f45b994dbed1273.js

198 ms

28297-4ad3b12cb40c11ba.js

28297-4ad3b12cb40c11ba.js

201 ms

94232-fc737e543b5862b2.js

94232-fc737e543b5862b2.js

199 ms

58234-108becf07df07eea.js

58234-108becf07df07eea.js

204 ms

63614-47d14af560f6497d.js

63614-47d14af560f6497d.js

207 ms

35326-f79684b8d069bba4.js

35326-f79684b8d069bba4.js

205 ms

58839-5ad543485f9909fd.js

58839-5ad543485f9909fd.js

209 ms

39174-278290511207d4fc.js

39174-278290511207d4fc.js

265 ms

29249-6cee1127b74affb9.js

29249-6cee1127b74affb9.js

267 ms

77791-49e27ecb2466d0d0.js

77791-49e27ecb2466d0d0.js

264 ms

65943-a8e743c5b733315e.js

65943-a8e743c5b733315e.js

267 ms

21616-944d3462154f6ec2.js

21616-944d3462154f6ec2.js

272 ms

85351-600ae835f6c3e7d9.js

85351-600ae835f6c3e7d9.js

271 ms

90129-d6ded7babf1ec476.js

90129-d6ded7babf1ec476.js

269 ms

89019-317f617b741a312c.js

89019-317f617b741a312c.js

276 ms

22793-80f0aec7237a9b7e.js

22793-80f0aec7237a9b7e.js

273 ms

54988-7a9dda2f72390cd2.js

54988-7a9dda2f72390cd2.js

274 ms

79977-fa5dd539f1d0a265.js

79977-fa5dd539f1d0a265.js

275 ms

53756-864f9ff783e2504a.js

53756-864f9ff783e2504a.js

280 ms

98284-3925ed787b8f7993.js

98284-3925ed787b8f7993.js

281 ms

91424-2bdd47103bd336a1.js

91424-2bdd47103bd336a1.js

281 ms

18.jpeg

18.jpeg

274 ms

shim.js

shim.js

77 ms

11.jpg

11.jpg

576 ms

2.png

2.png

523 ms

4.png

4.png

516 ms

3.png

3.png

1026 ms

11.jpg

11.jpg

398 ms

assignments

assignments

164 ms

5672-9715090c61af2fdb.js

5672-9715090c61af2fdb.js

179 ms

95717-53cb12a546fd4392.js

95717-53cb12a546fd4392.js

182 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

13 ms

82090-885f0afc127fc2e1.js

82090-885f0afc127fc2e1.js

173 ms

22316-5662b7fdb200b139.js

22316-5662b7fdb200b139.js

170 ms

60216-92397ab631d909b9.js

60216-92397ab631d909b9.js

174 ms

43389-896e282750a53630.js

43389-896e282750a53630.js

161 ms

2218-a5bd8af49784b817.js

2218-a5bd8af49784b817.js

119 ms

18704-b95984bdff7b5ad5.js

18704-b95984bdff7b5ad5.js

139 ms

95799-2bc7ca28893d4219.js

95799-2bc7ca28893d4219.js

135 ms

42719-0232f868b5e6eabc.js

42719-0232f868b5e6eabc.js

130 ms

32395-5df89d6bd6636d5c.js

32395-5df89d6bd6636d5c.js

126 ms

56262-7c9171dd00353de9.js

56262-7c9171dd00353de9.js

132 ms

17-88bf0942185f0617.js

17-88bf0942185f0617.js

144 ms

48948-87e5411ba5b598a6.js

48948-87e5411ba5b598a6.js

145 ms

82311-19838be888345c11.js

82311-19838be888345c11.js

142 ms

43340-6e4548fa4e723587.js

43340-6e4548fa4e723587.js

154 ms

%5B%5B...tab%5D%5D-a33dc81c4acc450c.js

%5B%5B...tab%5D%5D-a33dc81c4acc450c.js

189 ms

_buildManifest.js

_buildManifest.js

145 ms

_ssgManifest.js

_ssgManifest.js

170 ms

s.js

s.js

84 ms

Accessibility Review

pourquoipas.ca accessibility score

70

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

pourquoipas.ca 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

High

Missing source maps for large first-party JavaScript

SEO Factors

pourquoipas.ca SEO score

85

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pourquoipas.ca can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pourquoipas.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

pourquoipas.ca

Open Graph data is detected on the main page of Pourquoipas. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: