Tools & Wizards About Us
tva.ca screenshot

Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

tva.ca

Tout ce que vous aimez de TVA… et encore plus! | TVA+

Page Load Speed

2.3 sec in total

First Response

89 ms

Resources Loaded

2.1 sec

Page Rendered

67 ms

tva.ca screenshot

About Website

Click here to check amazing TVA content for Canada. Otherwise, check out these important facts you probably never knew about tva.ca

TVA+ vous donne accès à TVA en direct et aussi à des milliers d’heures de divertissement sur demande, avec des nouveautés ajoutées régulièrement.

Visit tva.ca

Key Findings

We analyzed Tva.ca page load time and found that the first response time was 89 ms and then it took 2.2 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

tva.ca performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value26.4 s

0/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

tva.ca

89 ms

tva.ca

104 ms

silent-auth

176 ms

connect

127 ms

redirect

38 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Tva.ca, 58% (34 requests) were made to Qub.ca and 37% (22 requests) were made to M1.quebecormedia.com. The less responsive or slowest element that took the longest time to load (810 ms) relates to the external source M1.quebecormedia.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 498.9 kB (73%)

Content Size

682.8 kB

After Optimization

183.8 kB

  • HTML
  • Images

In fact, the total size of Tva.ca main page is 682.8 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. 55% of websites need less resources to load. HTML takes 579.8 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 498.9 kB

  • Original 579.8 kB
  • After minification 579.8 kB
  • After compression 80.9 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 498.9 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 102.9 kB
  • After minification 102.9 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. TVA images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 36 (69%)

Requests Now

52

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tva.ca

tva.ca

89 ms

tva.ca

tva.ca

104 ms

silent-auth

silent-auth

176 ms

connect

connect

127 ms

redirect

redirect

38 ms

callback

callback

107 ms

tvaplus

tvaplus

362 ms

analytics-snippet-1592406242.min.js

analytics-snippet-1592406242.min.js

26 ms

3098167023770dbe.css

3098167023770dbe.css

63 ms

cc44fb319276a6a6.css

cc44fb319276a6a6.css

24 ms

ae62bf48ada05cfb.css

ae62bf48ada05cfb.css

23 ms

35fd30100d5e0c38.css

35fd30100d5e0c38.css

24 ms

a0cf06a58a8ed322.css

a0cf06a58a8ed322.css

42 ms

5f4288a5e1508e55.css

5f4288a5e1508e55.css

44 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

45 ms

webpack-cd11bfcf3f48fc8f.js

webpack-cd11bfcf3f48fc8f.js

83 ms

framework-f725be5aa0c8fb1b.js

framework-f725be5aa0c8fb1b.js

45 ms

main-309b2b7418e4ee7a.js

main-309b2b7418e4ee7a.js

90 ms

_app-b7b6d8325b1cfafe.js

_app-b7b6d8325b1cfafe.js

133 ms

6127-c68924ddf9b2e24d.js

6127-c68924ddf9b2e24d.js

89 ms

9533-2f15365ecb14215f.js

9533-2f15365ecb14215f.js

119 ms

8778-d8578089dba98a19.js

8778-d8578089dba98a19.js

89 ms

6924-e9de54b92ff861a6.js

6924-e9de54b92ff861a6.js

125 ms

1631-9fe538a8706a2895.js

1631-9fe538a8706a2895.js

148 ms

4414-71e83d06b3ed91df.js

4414-71e83d06b3ed91df.js

149 ms

619-4330b52330c94b2d.js

619-4330b52330c94b2d.js

162 ms

2945-b63127f8afd4b375.js

2945-b63127f8afd4b375.js

148 ms

2575-3424506849509413.js

2575-3424506849509413.js

150 ms

4961-0c1f18bdad086bc3.js

4961-0c1f18bdad086bc3.js

149 ms

2733-99c682e074c4f167.js

2733-99c682e074c4f167.js

151 ms

9374-76a6567aa9245ac8.js

9374-76a6567aa9245ac8.js

150 ms

4067-0ecb036f4eddc366.js

4067-0ecb036f4eddc366.js

153 ms

2159-727c884d0458865d.js

2159-727c884d0458865d.js

178 ms

%5B%5B...list-slug%5D%5D-532217de5c775ace.js

%5B%5B...list-slug%5D%5D-532217de5c775ace.js

154 ms

_buildManifest.js

_buildManifest.js

170 ms

_ssgManifest.js

_ssgManifest.js

160 ms

circle.svg

circle.svg

93 ms

inverse.svg

inverse.svg

123 ms

99407fdd-641b-4bec-85ae-c5a075a8e49f.png

99407fdd-641b-4bec-85ae-c5a075a8e49f.png

245 ms

266de12d-df3a-4fe1-9675-05976e5f5194.jpg

266de12d-df3a-4fe1-9675-05976e5f5194.jpg

454 ms

850b10f7-0051-4bf1-aafb-3cd32c62100f.png

850b10f7-0051-4bf1-aafb-3cd32c62100f.png

366 ms

b3a6d880-1f83-4886-98b5-3467e4fb4045.jpg

b3a6d880-1f83-4886-98b5-3467e4fb4045.jpg

312 ms

circle.svg

circle.svg

109 ms

71943566-5118-407c-9fb0-c89ff5ae268f.png

71943566-5118-407c-9fb0-c89ff5ae268f.png

133 ms

f131168b-e3a5-4cc0-8e43-4e5b2d2555bd.jpg

f131168b-e3a5-4cc0-8e43-4e5b2d2555bd.jpg

282 ms

b247670c-4e3b-42b1-96e1-4cdb14e8009e.jpg

b247670c-4e3b-42b1-96e1-4cdb14e8009e.jpg

433 ms

fe95cacd-3e10-4701-808c-c879e72fa2b5.png

fe95cacd-3e10-4701-808c-c879e72fa2b5.png

281 ms

f8acca8e-d693-4ef4-b191-f4885354bdc4.jpg

f8acca8e-d693-4ef4-b191-f4885354bdc4.jpg

322 ms

830c0061-adde-48a7-bd90-5515aa29d3a8.png

830c0061-adde-48a7-bd90-5515aa29d3a8.png

375 ms

cc45f068-c8d8-4273-b63f-bf6ccaba4813.png

cc45f068-c8d8-4273-b63f-bf6ccaba4813.png

364 ms

93323a0f-ab0e-467e-9434-0002d10403a0.png

93323a0f-ab0e-467e-9434-0002d10403a0.png

576 ms

3af1bef3-36cb-4b9a-aad9-268c1c634b54.png

3af1bef3-36cb-4b9a-aad9-268c1c634b54.png

541 ms

1d0eca3b-3963-4ca0-811d-9b11da6b1d11.png

1d0eca3b-3963-4ca0-811d-9b11da6b1d11.png

504 ms

6c4b865f-3af6-4256-8e99-541e77a1996a.jpg

6c4b865f-3af6-4256-8e99-541e77a1996a.jpg

493 ms

50f87df2-68d0-4d04-af3a-5fc771abce06.png

50f87df2-68d0-4d04-af3a-5fc771abce06.png

553 ms

4dd2f550-108f-4aed-83c8-d6c1216f2c5f.png

4dd2f550-108f-4aed-83c8-d6c1216f2c5f.png

612 ms

a75f9c2e-25ce-485f-a792-1ac51b2e8704.png

a75f9c2e-25ce-485f-a792-1ac51b2e8704.png

639 ms

0d2e81e4-748e-4f90-a8c1-c4a477c224a7.png

0d2e81e4-748e-4f90-a8c1-c4a477c224a7.png

810 ms

Logo_QUB_Horizontal-bc4bd949a9618e8013b23448ac904b57.svg

Logo_QUB_Horizontal-bc4bd949a9618e8013b23448ac904b57.svg

183 ms

Accessibility Review

tva.ca accessibility score

80

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

High

button, link, and menuitem elements do not have accessible names.

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

Links do not have a discernible name

Best Practices

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

tva.ca SEO score

100

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

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

tva.ca

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