3.1 sec in total
182 ms
2.3 sec
647 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 182 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
imtl.org performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value4.6 s
35/100
25%
Value5.6 s
52/100
10%
Value970 ms
28/100
30%
Value0.01
100/100
15%
Value11.4 s
19/100
10%
182 ms
515 ms
133 ms
226 ms
228 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 58% of them (50 requests) were addressed to the original Imtl.org, 13% (11 requests) were made to Fonts.gstatic.com and 8% (7 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (868 ms) belongs to the original domain Imtl.org.
Page size can be reduced by 378.1 kB (5%)
7.5 MB
7.1 MB
In fact, the total size of Imtl.org main page is 7.5 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. 70% of websites need less resources to load. Images take 7.0 MB which makes up the majority of the site volume.
Potential reduce by 53.5 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 14.0 kB, which is 22% 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 53.5 kB or 84% of the original size.
Potential reduce by 217.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. IMTL images are well optimized though.
Potential reduce by 48.2 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 48.2 kB or 13% of the original size.
Potential reduce by 58.6 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 58.6 kB or 55% of the original size.
Number of requests can be reduced by 30 (42%)
72
42
The browser has sent 72 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 22 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
imtl.org
182 ms
imtl.org
515 ms
bootstrap.min.css
133 ms
font-awesome.min.css
226 ms
jquery-ui.min.css
228 ms
slick.css
225 ms
nouislider.min.css
185 ms
style.css
249 ms
responsive.css
193 ms
local.css
247 ms
css
30 ms
logo.jpg
342 ms
20240326_125402.jpg
532 ms
20240409_165956.jpg
628 ms
300_young_1.png
742 ms
20240322_142450.jpg
578 ms
20240408_183215.jpg
430 ms
20240322_142818.jpg
531 ms
20240326_123056.jpg
704 ms
20240409_124754.jpg
606 ms
20240330_143530.jpg
657 ms
20240330_131545.jpg
630 ms
20230916_131615.jpg
638 ms
20240326_124329.jpg
673 ms
projet_mansfield.jpg
693 ms
20240314_165439.jpg
704 ms
tours_halles_anjou_2.jpg
807 ms
adsbygoogle.js
376 ms
js
64 ms
jquery-3.1.1.min.js
728 ms
jquery-ui.min.js
783 ms
bootstrap.min.js
797 ms
slick.min.js
801 ms
isotope.min.js
802 ms
wNumb.js
825 ms
nouislider.min.js
827 ms
global.js
826 ms
20240204_141858.jpg
834 ms
20231228_155416.jpg
865 ms
sbghistoire.jpg
867 ms
sbgreference.jpg
868 ms
divider-half-white.png
799 ms
montreal_image4.jpg
756 ms
montreal_image5.jpg
748 ms
montreal_image3.jpg
733 ms
montreal_image1.jpg
736 ms
174399_017.jpg
750 ms
laSalle_secondaire_2024.jpg
738 ms
patinoire_place_tranquille.jpg
830 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
89 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
159 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf
190 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf
204 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
205 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf
205 ms
fontawesome-webfont.woff
667 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
203 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
203 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
203 ms
20211221_140500.jpg
708 ms
show_ads_impl.js
302 ms
20200502_175941.jpg
552 ms
divider-half.png
505 ms
zrt_lookup.html
60 ms
ads
376 ms
ads
154 ms
3b0c1a1c8750041eb27603629860e89a.js
26 ms
load_preloaded_resource.js
54 ms
f11bfab4e3c942216447974439595ef6.js
36 ms
abg_lite.js
55 ms
window_focus.js
59 ms
qs_click_protection.js
61 ms
ufs_web_display.js
18 ms
bbae3fd3506d8d9338f85d10ea9db8af.js
54 ms
icon.png
26 ms
s
9 ms
css
18 ms
sodar
107 ms
activeview
85 ms
GhmJCpBREX7wgGMT0ZiWZLwlRNdtIOd5PV2NPLMoOVM.js
19 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf
13 ms
4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf
12 ms
sodar2.js
4 ms
runner.html
5 ms
aframe
33 ms
q3_ozqIbHCwHEmDedgzG-D6UnUyzi2L496FFdqoLokA.js
5 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 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
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
Browser errors were logged to the console
Page has valid source maps
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
UTF-8
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 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.
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: