Tools & Wizards About Us
uqat.ca screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 0

    Best Practices

  • 85

    SEO

    Google-friendlier than
    56% of websites

uqat.ca

Université du Québec en Abitibi-Témiscamingue | UQAT

Page Load Speed

1.8 sec in total

First Response

318 ms

Resources Loaded

1.2 sec

Page Rendered

255 ms

uqat.ca screenshot

About Website

Visit uqat.ca now to see the best up-to-date UQAT content for Canada and also check out these interesting facts you probably never knew about uqat.ca

Humaine, créative, audacieuse : trois qualités qui décrivent bien l’Université du Québec en Abitibi-Témiscamingue (Québec, Canada). L'UQAT, VOTRE monde!

Visit uqat.ca

Key Findings

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

Performance Metrics

uqat.ca performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value24.7 s

0/100

10%

Network Requests Diagram

uqat.ca

318 ms

global-2013-10-10.css

149 ms

jquery-1.4.2.min.js

249 ms

jquery.cycle.all.min.js

154 ms

jquery.vticker.js

122 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 65% of them (47 requests) were addressed to the original Uqat.ca, 11% (8 requests) were made to Google.com and 6% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (595 ms) belongs to the original domain Uqat.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 235.8 kB (23%)

Content Size

1.0 MB

After Optimization

775.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Uqat.ca main page is 1.0 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. 50% of websites need less resources to load. Images take 725.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 36.2 kB

  • Original 46.3 kB
  • After minification 38.2 kB
  • After compression 10.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. This page needs HTML code to be minified as it can gain 8.1 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 36.2 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 47.7 kB

  • Original 725.9 kB
  • After minification 678.2 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. UQAT images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 105.1 kB

  • Original 183.6 kB
  • After minification 182.7 kB
  • After compression 78.5 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 105.1 kB or 57% of the original size.

CSS Optimization

-84%

Potential reduce by 46.8 kB

  • Original 55.9 kB
  • After minification 46.9 kB
  • After compression 9.1 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. Uqat.ca needs all CSS files to be minified and compressed as it can save up to 46.8 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (51%)

Requests Now

67

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

uqat.ca

uqat.ca

318 ms

global-2013-10-10.css

global-2013-10-10.css

149 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

249 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

154 ms

jquery.vticker.js

jquery.vticker.js

122 ms

jsapi

jsapi

24 ms

t13n

t13n

37 ms

t13n

t13n

107 ms

scripts_pa.min.js

scripts_pa.min.js

49 ms

sousmenu.min.js

sousmenu.min.js

62 ms

analytics.js

analytics.js

24 ms

fbevents.js

fbevents.js

169 ms

uqat_tete_top_new3.png

uqat_tete_top_new3.png

80 ms

bt_facebook.png

bt_facebook.png

79 ms

bt_twitter.png

bt_twitter.png

78 ms

bt_youtube.png

bt_youtube.png

76 ms

bt_vimeo.png

bt_vimeo.png

79 ms

bt_rss.png

bt_rss.png

81 ms

uqat_tete_new_2.png

uqat_tete_new_2.png

125 ms

rech_avancee.png

rech_avancee.png

221 ms

slide_27.jpg

slide_27.jpg

321 ms

slide_28.jpg

slide_28.jpg

243 ms

slide_29.jpg

slide_29.jpg

243 ms

slide_30.jpg

slide_30.jpg

425 ms

slide_33.jpg

slide_33.jpg

219 ms

slide_31.jpg

slide_31.jpg

524 ms

slide_32.jpg

slide_32.jpg

524 ms

FutursEtudiants.png

FutursEtudiants.png

342 ms

AdmissionInscription.png

AdmissionInscription.png

343 ms

1217_derniere.jpg

1217_derniere.jpg

413 ms

actualite_mini.png

actualite_mini.png

453 ms

1213_derniere.jpg

1213_derniere.jpg

413 ms

suite_actus.png

suite_actus.png

465 ms

collation_2015.jpg

collation_2015.jpg

483 ms

filariane_logo.png

filariane_logo.png

470 ms

gtm.js

gtm.js

76 ms

barre_nav_new2.png

barre_nav_new2.png

496 ms

cadre_page.png

cadre_page.png

508 ms

cadre_haut_page_new2.png

cadre_haut_page_new2.png

513 ms

accesrapide.png

accesrapide.png

525 ms

accesrapide_fond_trans.png

accesrapide_fond_trans.png

539 ms

cadre_page_pad_bas_nav.png

cadre_page_pad_bas_nav.png

555 ms

menupa_fond_trans.png

menupa_fond_trans.png

558 ms

15 ms

collect

collect

12 ms

transliteration.css

transliteration.css

4 ms

transliteration.I.js

transliteration.I.js

12 ms

collect

collect

86 ms

32 ms

black-50.png

black-50.png

517 ms

flip-nav.png

flip-nav.png

583 ms

contenu_4.png

contenu_4.png

579 ms

BG_box_header.png

BG_box_header.png

587 ms

widgets.js

widgets.js

15 ms

logo_calendrier.png

logo_calendrier.png

565 ms

filariane_separateur.png

filariane_separateur.png

523 ms

ligne_pied_fond.png

ligne_pied_fond.png

545 ms

pied_fond.png

pied_fond.png

571 ms

chercher_input.png

chercher_input.png

595 ms

inputtools.js

inputtools.js

18 ms

timeline.1b43d11859b7663a2225b885f87704a5.js

timeline.1b43d11859b7663a2225b885f87704a5.js

46 ms

ga-audiences

ga-audiences

95 ms

125 ms

syndication

syndication

109 ms

349978431980703745

349978431980703745

144 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

5 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

11 ms

5f83d9cfb18c851f895ba4acca2d9582_normal.jpeg

5f83d9cfb18c851f895ba4acca2d9582_normal.jpeg

129 ms

3vhNI62i_normal.jpg

3vhNI62i_normal.jpg

155 ms

jot

jot

26 ms

impression.min.css

impression.min.css

52 ms

roundtrip.js

roundtrip.js

9 ms

Accessibility Review

uqat.ca accessibility score

85

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

[role] values are not valid

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

SEO Factors

uqat.ca SEO score

85

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

uqat.ca

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