3 sec in total
727 ms
1.8 sec
504 ms
Welcome to imtl.org homepage info - get ready to check IMTL best content for Canada right away, or after learning these important things about imtl.org
Images Montreal : photos de gratte-ciel et architecture historiques, IMTL, Quebec
Visit imtl.orgWe analyzed Imtl.org page load time and found that the first response time was 727 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 40% of websites can load faster.
imtl.org performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value19.7 s
0/100
25%
Value7.1 s
31/100
10%
Value830 ms
35/100
30%
Value0.062
97/100
15%
Value14.2 s
9/100
10%
727 ms
64 ms
144 ms
10 ms
181 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 77% of them (53 requests) were addressed to the original Imtl.org, 7% (5 requests) were made to Pagead2.googlesyndication.com and 6% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (740 ms) belongs to the original domain Imtl.org.
Page size can be reduced by 195.6 kB (18%)
1.1 MB
863.8 kB
In fact, the total size of Imtl.org main page is 1.1 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. 45% of websites need less resources to load. Images take 889.9 kB which makes up the majority of the site volume.
Potential reduce by 36.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 36.1 kB or 79% of the original size.
Potential reduce by 130.4 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. Obviously, IMTL needs image optimization as it can save up to 130.4 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 9.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. This website has mostly compressed JavaScripts.
Potential reduce by 19.2 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. Imtl.org needs all CSS files to be minified and compressed as it can save up to 19.2 kB or 81% of the original size.
Number of requests can be reduced by 12 (18%)
67
55
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IMTL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
imtl.org
727 ms
search.css
64 ms
responsive.css
144 ms
adsbygoogle.js
10 ms
twitter_street.png
181 ms
facebook.png
126 ms
icon_home.gif
125 ms
b_newPoint.jpg
447 ms
20141124_131255.jpg
420 ms
4_2_MG_0025.jpg
382 ms
pavillon_des_sciences_923.jpg
239 ms
1_MG_6006.jpg
275 ms
quartier_ico_sm.jpg
278 ms
IMG_4602.jpg
305 ms
small_futur_.jpg
477 ms
montreal_image5.jpg
345 ms
montreal_image4.jpg
378 ms
montreal_image1.jpg
411 ms
montreal_image3.jpg
452 ms
montreal_image2.jpg
461 ms
explorateur_mroyal.jpg
489 ms
panoramique_360_sma.jpg
490 ms
174399_017.jpg
540 ms
20160215_171124.jpg
543 ms
2015_IMG_3190.jpg
552 ms
2015_IMG_3156.jpg
545 ms
2015_IMG_3125.jpg
625 ms
2015_IMG_3291.jpg
583 ms
2015_IMG_3351.jpg
633 ms
ca-pub-0866178478906864.js
51 ms
zrt_lookup.html
44 ms
show_ads_impl.js
86 ms
analytics.js
30 ms
bg_line2.jpg
462 ms
montreal_t2.jpg
499 ms
topLarge.jpg
499 ms
redevellopement_alcan.jpg
525 ms
grayTopmini.jpg
490 ms
bgquestion.jpg
576 ms
bonnaventure.jpg
550 ms
2015_IMG_3144.jpg
585 ms
tour2canadiens.jpg
582 ms
tour_quartier_spectacle_avant.jpg
694 ms
redevellopement_alcan.jpg
607 ms
20131030_124920.jpg
740 ms
Western_Hospital_avenue_Atwater_Montreal_1902_notman.jpg
667 ms
eglise_rue_recolet_love_james_w_1862.JPG
672 ms
collect
40 ms
ads
289 ms
1_MG_8905.jpg
600 ms
osd.js
5 ms
20151120_121029.jpg
624 ms
20150926_151925.jpg
653 ms
champs_de_mars.jpg
635 ms
20160211_134258(0).jpg
601 ms
sbghistoire.jpg
581 ms
sbgreference.jpg
610 ms
sbgmusee.jpg
571 ms
bgmenu08.jpg
597 ms
recherche_go.gif
587 ms
bg_belle.jpg
571 ms
m_js_controller.js
29 ms
abg.js
41 ms
favicon
62 ms
googlelogo_color_112x36dp.png
52 ms
nessie_icon_thin_arrow_big_white.png
30 ms
s
21 ms
x_button_blue2.png
9 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
3 ms
imtl.org accessibility score
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
[aria-*] attributes do not match their roles
ARIA input fields 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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
imtl.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
imtl.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
FR
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imtl.org 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 Imtl.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
imtl.org
Open Graph description is not detected on the main page of IMTL. 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: