2 sec in total
128 ms
1.7 sec
110 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 128 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
stm.info performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value11.8 s
0/100
25%
Value8.2 s
20/100
10%
Value5,760 ms
0/100
30%
Value0.108
87/100
15%
Value35.1 s
0/100
10%
128 ms
79 ms
31 ms
78 ms
22 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 87% of them (136 requests) were addressed to the original Stm.info, 3% (5 requests) were made to Googletagmanager.com and 2% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (680 ms) belongs to the original domain Stm.info.
Page size can be reduced by 366.7 kB (19%)
2.0 MB
1.6 MB
In fact, the total size of Stm.info main page is 2.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 975.1 kB which makes up the majority of the site volume.
Potential reduce by 173.8 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 173.8 kB or 85% of the original size.
Potential reduce by 72.3 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. STM images are well optimized though.
Potential reduce by 97.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 97.5 kB or 14% of the original size.
Potential reduce by 23.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. Stm.info needs all CSS files to be minified and compressed as it can save up to 23.2 kB or 26% of the original size.
Number of requests can be reduced by 80 (53%)
152
72
The browser has sent 152 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 58 to 1 for JavaScripts and as a result speed up the page load time.
fr
128 ms
LiveChatBootstrapper.js
79 ms
modernizr-2.6.1.min.js
31 ms
purify.min.js
78 ms
banner.js
22 ms
css_JRaTBVhzkSPsu5O7BK7U1IMyz4tAQ-IJ2yOdKp2ME40.css
78 ms
css_cxm7Xg5EOkgdfk2RDpNcC8-daV4JzZrcfX9ag0fB9A4.css
95 ms
css_zvYiO8wRj2oWglByIUTX2ZcOSZSwqGWKUpNXWGVEQ-0.css
126 ms
jquery.min.js
90 ms
jquery-extend-3.4.0.js
71 ms
jquery-html-prefilter-3.5.0-backport.js
113 ms
jquery.once.js
107 ms
drupal.js
107 ms
jquery.ui.core.min.js
177 ms
jquery.ui.widget.min.js
120 ms
stmap-context.js
179 ms
stmapdt.min.js
185 ms
api.js
180 ms
jquery.ui.tabs.min.js
181 ms
jquery.ui.accordion.min.js
181 ms
jquery.ui.position.min.js
206 ms
jquery.ui.position-1.13.0-backport.js
205 ms
jquery.ui.autocomplete.min.js
205 ms
jquery.ui.datepicker.min.js
228 ms
jquery.ui.datepicker-1.13.0-backport.js
227 ms
locale.datepicker.js
232 ms
jquery.ui.button.min.js
233 ms
jquery.ui.mouse.min.js
233 ms
jquery.ui.draggable.min.js
264 ms
jquery.ui.resizable.min.js
233 ms
jquery.ui.dialog.min.js
265 ms
jquery.ui.dialog-1.13.0-backport.js
266 ms
jquery.ui.menu.min.js
298 ms
jquery.ui.tooltip.min.js
267 ms
jquery.hoverIntent.js
265 ms
stm_nav.js
295 ms
fr_xkRAuRErgLUM3hiQsSgji3_QMXEaSfYPwJ5rdhkqsCU.js
296 ms
scripts.js
299 ms
jscharting.js
344 ms
slick.min.js
278 ms
stm_app.js
275 ms
stm_app_metro.js
274 ms
stm_app_schedule.js
257 ms
jquery.console.log.js
257 ms
jquery.scrollTo.js
254 ms
jquery.images-loaded.js
300 ms
jquery.cookie.js
301 ms
jquery.jcarousel.js
300 ms
konami.js
291 ms
gtm.js
123 ms
DFPAudiencePixel;ord=4923461028374.731;dc_seg=6562607057
143 ms
fbevents.js
78 ms
scripts.js
242 ms
weekly-schedule.js
239 ms
gradient-body.png
239 ms
header-logo.png
238 ms
20000_reseaux.png
454 ms
20000_etat_du_service.png
453 ms
20000_titres_et_tarifs.png
429 ms
service_a_la_clientele_0.png
429 ms
20000_conseils_aux_passagers.png
408 ms
20000_reglements_et_securite.png
409 ms
stmmontreal_bold-webfont.woff
667 ms
stmmontreal_regular-webfont.woff
663 ms
55000_accessibilite-universelle_1_1.png
658 ms
sirta_reserv_-icon150.png
658 ms
ico-nous-joindre_1.jpg
658 ms
41000_a-propos-du-transport-adapte.png
657 ms
42000_admission.png
670 ms
20000_titres_et_tarifs_2.png
661 ms
44000_utiliser-le-transport-adapte.png
661 ms
45000_consignes-et-conseils.png
680 ms
47000_formulaires_0.png
630 ms
petit_icone_spectacle.png
629 ms
ico-sorties_0_0.png
650 ms
15500_13-infolettre_icone.png
657 ms
17014_02-picto.png
645 ms
decouvrez-la-stm-et-son-histoire.png
645 ms
js
96 ms
js
305 ms
ga.js
162 ms
analytics.js
301 ms
destination
299 ms
insight.min.js
298 ms
conversion.min.js
553 ms
22817_02_pictopagegrandprojet_80x100_1.png
620 ms
gouvernance_picto.png
635 ms
53000_informations-corporatives-et-financieres.png
635 ms
57000_communaute-developpeurs.png
635 ms
espace-affaires.png
634 ms
20037_04b_sitestm_picto_sondage_80x100.png
604 ms
picto-mes-alertes.svg
598 ms
icons-small.png
608 ms
icon-accessibilite.png
596 ms
map-application-tabs-sprite.png
593 ms
wheelchair-white-24x24.png
590 ms
wheelchair-blue-24x24.png
601 ms
white-warning-24x24.png
601 ms
general-plan.png
535 ms
inpage_linkid.js
293 ms
tarifs_0.jpg
398 ms
carte_opus_1.jpg
398 ms
cartetrans_1.jpg
409 ms
opus_date.gif
409 ms
opus_date_1.gif
410 ms
info.png
423 ms
collect
85 ms
insight_tag_errors.gif
251 ms
tarifs_0_0.jpg
170 ms
tarifs_0_2.jpg
166 ms
map-application-open-close.png
180 ms
map-service-state.png
180 ms
advertising-sprite.png
179 ms
23009_09-recrut_carrousel_f.png
196 ms
__utm.gif
19 ms
111188217-1_artm_recharge_opus_stm_340x210_fr_2.jpg
161 ms
23025-carrousel-p_hivernal-_ambassadeurs_f_0.png
173 ms
224650_01_carrousel_340x210_8_f_0.png
187 ms
carrousel_fr_2.png
174 ms
collect
15 ms
js
48 ms
21450_07_sitestm_carrousel_340x210_fr.png
165 ms
collect
11 ms
ga-audiences
74 ms
24015_01_carrousel_340x210_fr.png
169 ms
footer-services-sprite.png
174 ms
icons-social-small.png
183 ms
infolettre.png
178 ms
ga-audiences
71 ms
icons-plus.svg
174 ms
icons-minus.svg
179 ms
bus-position-control-icon.png
187 ms
icons-icon-couches-cartes.svg
177 ms
315.png
256 ms
315.png
310 ms
316.png
318 ms
314.png
309 ms
316.png
307 ms
314.png
308 ms
315.png
309 ms
315.png
328 ms
316.png
344 ms
314.png
346 ms
316.png
324 ms
314.png
319 ms
315.png
347 ms
315.png
327 ms
316.png
351 ms
314.png
356 ms
316.png
141 ms
314.png
83 ms
315.png
101 ms
316.png
78 ms
314.png
79 ms
315.png
82 ms
316.png
94 ms
314.png
87 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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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 best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
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: