819 ms in total
76 ms
626 ms
117 ms
Visit stm.info now to see the best up-to-date STM content for Canada and also check out these interesting facts you probably never knew about stm.info
Entreprise publique, la Société de transport de Montréal assure les besoins de mobilité de la population en offrant un réseau de transport collectif de bus et métro.
Visit stm.infoWe analyzed Stm.info page load time and found that the first response time was 76 ms and then it took 743 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
stm.info performance score
name
value
score
weighting
Value12.2 s
0/100
10%
Value24.0 s
0/100
25%
Value18.5 s
0/100
10%
Value23,490 ms
0/100
30%
Value0.005
100/100
15%
Value41.2 s
0/100
10%
76 ms
50 ms
41 ms
55 ms
109 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 84% of them (66 requests) were addressed to the original Stm.info, 6% (5 requests) were made to Google-analytics.com and 1% (1 request) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (248 ms) belongs to the original domain Stm.info.
Page size can be reduced by 1.5 MB (56%)
2.7 MB
1.2 MB
In fact, the total size of Stm.info main page is 2.7 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. 40% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 148.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 148.1 kB or 85% of the original size.
Potential reduce by 207.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. Obviously, STM needs image optimization as it can save up to 207.9 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 898.6 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 898.6 kB or 72% of the original size.
Potential reduce by 283.4 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. Stm.info needs all CSS files to be minified and compressed as it can save up to 283.4 kB or 86% of the original size.
Number of requests can be reduced by 36 (47%)
77
41
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of STM. 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 as a result speed up the page load time.
fr
76 ms
modernizr-2.6.1.min.js
50 ms
css_sRBrTC0bKAoPtoym9Xeap5EcShghHx9_0q52zikCr6Q.css
41 ms
css_cxm7Xg5EOkgdfk2RDpNcC8-daV4JzZrcfX9ag0fB9A4.css
55 ms
css_xajl29VBIw4Hynup5GqiZtxBvAZIw9PkePzE4EattBU.css
109 ms
conversion.js
15 ms
js_-z-2lAhufzBeVjYseT6cTzSICUy9vnoLBpu1sF_zZrs.js
74 ms
js_AIjtX5u1VhkGD6LKLTaFQDeO5Y73MAz-8TlPGj0_DSs.js
49 ms
api.js
192 ms
js_7syw3Je1nnDaZwJH_pf5oAs9PYRoyHY2xKihSU7qFTY.js
153 ms
js_xGKefWkiwRex2XcmOd5dAIRSFFZ-_0hcISCHakozUgs.js
47 ms
js_RYKevzdJ1XNS8qtFcagSxICIkivAXCN260mraf61dEQ.js
48 ms
js_PpZUBDHNSAACOQ7hXcCNOwBF3eb1Ea096jmRFFOGFX8.js
75 ms
js_zSfhz4sKZFtxo8GnzbvDPRvYjl6Y8Hq0rbc3BfZj42Y.js
151 ms
js_VSmF_ekzQMhyRl0-FN1DFIqfEA2bqef2EylKROXvyVU.js
150 ms
js_q2f53be15SFKTV1QFOUzlQ8WprP_XOMj9U8mbuVNCgU.js
153 ms
fbevents.js
40 ms
110 ms
DFPAudiencePixel;ord=1170618941541.7612;dc_seg=141630250
57 ms
gtm.js
57 ms
gradient-body.png
71 ms
header-logo.png
72 ms
20000_reseaux.png
72 ms
20000_etat_du_service.png
72 ms
20000_titres_et_tarifs.png
46 ms
service_a_la_clientele_0.png
72 ms
20000_conseils_aux_passagers.png
81 ms
20000_reglements_et_securite.png
82 ms
25000_accessibilite_reseau-33_0_2.png
81 ms
41000_a-propos-du-transport-adapte.png
83 ms
42000_admission.png
82 ms
20000_titres_et_tarifs_2.png
82 ms
44000_utiliser-le-transport-adapte.png
178 ms
45000_consignes-et-conseils.png
176 ms
47000_formulaires_0.png
176 ms
app_merci.png
174 ms
sorties.png
176 ms
15500_13-infolettre_icone.png
174 ms
decouvrez-la-stm-et-son-histoire.png
199 ms
52000_grands-projets.png
199 ms
gouvernance_picto.png
198 ms
53000_informations-corporatives-et-financieres.png
198 ms
54000_sondages.png
198 ms
55000_accessibilite-universelle_1.png
199 ms
56000_fournisseurs-et-partenaires_2.png
212 ms
57000_communaute-developpeurs.png
212 ms
icons-small.png
221 ms
logo-mystm-small.png
210 ms
icon-accessibilite.png
210 ms
map-application-tabs-sprite.png
210 ms
general-plan.png
218 ms
carte_opus_1.jpg
216 ms
cartetrans_1.jpg
219 ms
opus_date.gif
220 ms
map-application-open-close.png
220 ms
75 ms
icons-normal.png
248 ms
map-service-state.png
173 ms
advertising-sprite.png
174 ms
sef-relache_pub.png
196 ms
16506_03-340x210_fr.png
196 ms
azur_pub_1.png
198 ms
ga.js
97 ms
analytics.js
96 ms
stmmontreal_bold-webfont.woff
231 ms
122 ms
stmmontreal_regular-webfont.woff
208 ms
15453_11-carrousel_fr.png
227 ms
opusenregistrer_pub.png
233 ms
16803_11-340x210_fr.png
208 ms
15599_canadiens_carrousel_v2_fran.png
225 ms
15533_01-achristi_carrousel_f.png
247 ms
etats-du-service
172 ms
footer-services-sprite.png
169 ms
icons-social-small.png
143 ms
infolettre.png
152 ms
inpage_linkid.js
13 ms
collect
19 ms
__utm.gif
11 ms
stm.info 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-hidden="true"] elements contain focusable descendents
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes are not valid or misspelled
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
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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Definition list items are not wrapped in <dl> elements
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
stm.info SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a valid hreflang
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
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stm.info 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 Stm.info 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.
stm.info
Open Graph data is detected on the main page of STM. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: