2.3 sec in total
139 ms
2 sec
160 ms
Visit realtimemap.grt.ca now to see the best up-to-date Realtime Map Grt content for Canada and also check out these interesting facts you probably never knew about realtimemap.grt.ca
The map uses real-time departure information to show where buses are up to the minute on all of GRT’s routes.
Visit realtimemap.grt.caWe analyzed Realtimemap.grt.ca page load time and found that the first response time was 139 ms and then it took 2.2 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. This domain responded with an error, which can significantly jeopardize Realtimemap.grt.ca rating and web reputation
realtimemap.grt.ca performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value9.8 s
0/100
25%
Value12.5 s
3/100
10%
Value870 ms
33/100
30%
Value0.209
59/100
15%
Value20.5 s
2/100
10%
139 ms
193 ms
312 ms
191 ms
229 ms
Our browser made a total of 165 requests to load all elements on the main page. We found that 32% of them (53 requests) were addressed to the original Realtimemap.grt.ca, 41% (68 requests) were made to Grt.ca and 17% (28 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (797 ms) relates to the external source Grt.ca.
Page size can be reduced by 1.2 MB (58%)
2.1 MB
877.4 kB
In fact, the total size of Realtimemap.grt.ca main page is 2.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. 60% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 29.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 29.1 kB or 77% of the original size.
Potential reduce by 26.6 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. Realtime Map Grt images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 73% of the original size.
Potential reduce by 109.7 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. Realtimemap.grt.ca needs all CSS files to be minified and compressed as it can save up to 109.7 kB or 83% of the original size.
Number of requests can be reduced by 106 (67%)
158
52
The browser has sent 158 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Realtime Map Grt. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
realtimemap.grt.ca
139 ms
base.css
193 ms
structure.css
312 ms
sitecontent.css
191 ms
icreate.css
229 ms
navigation.css
295 ms
jquery.autocomplete.css
187 ms
jquery-atoz-scroll.css
248 ms
jquery-ui-1.10.3.custom.css
430 ms
jquery-1.9.1.min.js
536 ms
jquery-migrate-1.2.1.min.js
331 ms
jquery-ui.1.10.2.min.js
797 ms
jquery.cookies.js
397 ms
superfish.js
389 ms
general.js
423 ms
quicklinks-dropdown.js
440 ms
jquery.autocomplete.min.js
467 ms
email.js
476 ms
mailto.js
484 ms
textSize.js
507 ms
jquery-atoz-scroll.js
553 ms
supersleight.plugin.js
520 ms
feedbackStructure.js
198 ms
__utm.js
565 ms
share.css
563 ms
tablestyles.css
552 ms
share.js
582 ms
contextMenu.css
607 ms
jquery.contextMenu.js
666 ms
contact-autocomplete.css
614 ms
contactsV2.js
615 ms
__utm.gif
60 ms
uber_bg.jpg
51 ms
company_logo.jpg
87 ms
spacer.gif
52 ms
logo.jpg
70 ms
mainNav.gif
52 ms
interior_bg.gif
52 ms
top_gradient.jpg
87 ms
nav_bg.gif
66 ms
icon_share.gif
75 ms
icon_minus.gif
77 ms
icon_plus.gif
92 ms
icon_print.gif
95 ms
icon_rss.gif
106 ms
icon_email.gif
107 ms
actions_bg.jpg
148 ms
defaultInteriorBanner.jpg
120 ms
quicklinks.gif
119 ms
ql_line.gif
123 ms
Map
302 ms
footer_bg.jpg
138 ms
row.jpg
135 ms
icon_facebook.gif
145 ms
icon_twitter.gif
175 ms
esolutionsgroupLogo.gif
167 ms
eSolutionsGroupLogo.jpg
185 ms
interior_bg_wide.gif
166 ms
actions_bg_wide.jpg
234 ms
siteanalyze_562946.js
257 ms
en
122 ms
GetContactHTML.ashx
180 ms
mainnav_arrow_up.gif
192 ms
delicious.gif
234 ms
digg.gif
236 ms
facebook.gif
234 ms
linkedin.gif
267 ms
stumbleupon.gif
256 ms
technorati.gif
269 ms
twitter.gif
270 ms
feedback.png
287 ms
feedback.css
27 ms
logo_white.jpg
217 ms
jquery-ui.css
73 ms
jquery.min.js
104 ms
jquery-ui.min.js
166 ms
jquery.loadmask.css
75 ms
jquery.loadmask.min.js
61 ms
jquery.timer.js
62 ms
site.css
117 ms
js
41 ms
infobubble.js
204 ms
print.css
61 ms
common.js
23 ms
util.js
22 ms
geocoder.js
43 ms
GetVehicles
203 ms
close-bubble.png
194 ms
header-routes.png
36 ms
bg-list.png
28 ms
header-find-a-stop.png
34 ms
header-trip-planner.png
38 ms
header-legend.png
57 ms
button-buses.png
75 ms
button-stops.png
106 ms
corner-top-left.png
83 ms
corner-top-right.png
85 ms
corner-bottom-right.png
119 ms
corner-bottom-left.png
117 ms
loading.gif
116 ms
AuthenticationService.Authenticate
49 ms
GeocodeService.Search
127 ms
map.js
3 ms
onion.js
26 ms
openhand_8_8.cur
76 ms
marker.js
26 ms
ViewportInfoService.GetViewportInfo
93 ms
stats.js
19 ms
controls.js
19 ms
css
99 ms
transparent.png
36 ms
GetBusMarker
35 ms
GetBusMarker
62 ms
GetBusMarker
62 ms
GetBusMarker
61 ms
GetBusMarker
60 ms
GetBusMarker
61 ms
GetBusMarker
61 ms
GetBusMarker
91 ms
GetBusMarker
91 ms
GetBusMarker
90 ms
GetBusMarker
90 ms
GetBusMarker
90 ms
GetBusMarker
91 ms
GetBusMarker
120 ms
GetBusMarker
122 ms
GetBusMarker
122 ms
GetBusMarker
120 ms
GetBusMarker
123 ms
GetBusMarker
120 ms
GetBusMarker
140 ms
GetBusMarker
139 ms
GetBusMarker
142 ms
GetBusMarker
143 ms
GetBusMarker
141 ms
GetBusMarker
141 ms
GetBusMarker
163 ms
GetBusMarker
165 ms
GetBusMarker
166 ms
google4.png
55 ms
mapcnt6.png
81 ms
tmapctrl.png
59 ms
cb_scout5.png
75 ms
tmapctrl4.png
68 ms
imgs8.png
74 ms
vt
69 ms
vt
49 ms
vt
52 ms
vt
92 ms
vt
81 ms
vt
85 ms
vt
98 ms
vt
91 ms
vt
105 ms
vt
120 ms
vt
127 ms
vt
132 ms
vt
137 ms
vt
128 ms
vt
166 ms
vt
160 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
38 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
52 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
54 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
58 ms
realtimemap.grt.ca accessibility score
realtimemap.grt.ca 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
realtimemap.grt.ca SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Realtimemap.grt.ca can be misinterpreted by Google and other search engines. Our service has detected that English 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 Realtimemap.grt.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.
realtimemap.grt.ca
Open Graph description is not detected on the main page of Realtime Map Grt. 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: