2.6 sec in total
103 ms
2.1 sec
437 ms
Click here to check amazing Grt content for Canada. Otherwise, check out these important facts you probably never knew about grt.ca
Visit grt.caWe analyzed Grt.ca page load time and found that the first response time was 103 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
grt.ca performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value19.8 s
0/100
25%
Value8.6 s
17/100
10%
Value810 ms
36/100
30%
Value0.006
100/100
15%
Value15.7 s
6/100
10%
103 ms
94 ms
167 ms
84 ms
41 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 66% of them (80 requests) were addressed to the original Grt.ca, 11% (13 requests) were made to Js.esolutionsgroup.ca and 4% (5 requests) were made to App.ca.five9.com. The less responsive or slowest element that took the longest time to load (569 ms) belongs to the original domain Grt.ca.
Page size can be reduced by 234.0 kB (3%)
6.8 MB
6.5 MB
In fact, the total size of Grt.ca main page is 6.8 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. 55% of websites need less resources to load. Images take 5.8 MB which makes up the majority of the site volume.
Potential reduce by 82.3 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 82.3 kB or 77% of the original size.
Potential reduce by 11.2 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. Grt images are well optimized though.
Potential reduce by 132.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 132.9 kB or 17% of the original size.
Potential reduce by 7.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. Grt.ca needs all CSS files to be minified and compressed as it can save up to 7.6 kB or 11% of the original size.
Number of requests can be reduced by 80 (70%)
114
34
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 45 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
grt.ca
103 ms
grt.ca
94 ms
www.grt.ca
167 ms
index.aspx
84 ms
css
41 ms
styles.css
144 ms
icreate.css
157 ms
mediaelementplayer.min.css
52 ms
jquery.min.js
78 ms
jquery-ui.min.css
117 ms
jquery-ui.min.js
132 ms
jquery.cookie.min.js
116 ms
jquery.hoverIntent.min.js
116 ms
mediaelement-and-player.min.js
130 ms
icrt-toDateTimeString.min.js
131 ms
general.js
187 ms
email.js
186 ms
contextMenu.min.css
130 ms
jquery.contextMenu.min.js
130 ms
svg4everybody.min.js
185 ms
video_playlist_player.css
188 ms
video-playlist.min.js
569 ms
youTubePlayer.js
191 ms
ContactsExtended.css
195 ms
contactsV2.js
195 ms
cludo-search-default.min.css
38 ms
homepage.css
211 ms
jquery.iosslider.min.js
128 ms
sliderInit.js
211 ms
icrtShortcut.js
219 ms
jquery.rotatingbanners.min.js
240 ms
NewsFeedPlugin.js
219 ms
feedbackStructure.js
277 ms
feedback.css
236 ms
icModal.js
273 ms
jquery.AlertModal.js
274 ms
AlertModal.js
282 ms
EmergencyAlertModal.css
284 ms
element.js
57 ms
js
113 ms
responsiveScripts.js
304 ms
navigation.js
289 ms
triptools.js
284 ms
headroom.min.js
306 ms
scrollmagic.min.js
326 ms
scroll_init.js
308 ms
jquery-icrtaccordion-clean.min.js
319 ms
placeholders.jquery.min.js
333 ms
monsido-script.js
59 ms
js
96 ms
grt-alerts.js
332 ms
search-script.min.js
39 ms
five9-social-widget.min.js
54 ms
widgets.js
91 ms
icon-sprite.svg
49 ms
logo.svg
41 ms
icon-detours.svg
43 ms
icon-findSchedule.svg
44 ms
icon-routeMap.svg
45 ms
icon-systemMap.svg
44 ms
icon-fares.svg
55 ms
icon-pay.svg
56 ms
icon-reload.svg
52 ms
icon-where.svg
51 ms
icon-plan.svg
56 ms
icon-accessibility.svg
79 ms
icon-lost.svg
80 ms
icon-cycling.svg
81 ms
icon-contact.svg
93 ms
icon-new-directions-02.svg
91 ms
ion-featured-menu-icon-01.svg
92 ms
icon-plan.svg
110 ms
icon-schedule.svg
108 ms
icon-ride.svg
110 ms
icon-alert.svg
112 ms
info-icon.svg
107 ms
google_on_white.png
111 ms
GRT_0669-MPLUS-vehicle-Kitchener-City-Hall-592x561-px.jpg
340 ms
icon-feedback.svg
216 ms
icon-detour.svg
213 ms
icon-fares.svg
215 ms
icon-findschedule.svg
217 ms
icon-twitter.svg
216 ms
icon-facebook.svg
287 ms
icon-instagram.svg
289 ms
Twitter-alert-icon.svg
289 ms
logo-region.svg
287 ms
icon-sprite.svg
265 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
31 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
32 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
36 ms
five9-social-widget.css
26 ms
bg-services.jpg
273 ms
chat-small.png
120 ms
siteanalyze_562946.js
244 ms
minus-32.png
191 ms
external-link-32.png
212 ms
analytics.js
175 ms
GetContactHTML.ashx
173 ms
jquery.rotatingbanners.min.css
229 ms
getTopFiveNews.ashx
124 ms
api.js
136 ms
en
301 ms
getAlertBannerFeeds.ashx
108 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
147 ms
slider-chevron-left.svg
98 ms
slider-chevron-right.svg
142 ms
JMM_1980-Route-72-Sportsworld-Station-1683x665px.jpg
259 ms
2024-04-15-GRT_3311-206-crossing-Freeport-bridge.jpg
534 ms
GRT_8300-Train-tulips-Benton-Charles-1400x553px.jpg
240 ms
slider-pause.svg
146 ms
linkid.js
38 ms
alert_icon_blue.svg
40 ms
settings
125 ms
recaptcha__en.js
36 ms
feedback.min.css
14 ms
logo.svg
24 ms
print.css
165 ms
tracking.monsido.com
74 ms
mon-page-assist-loader.js
47 ms
page-correct.js
79 ms
grt.ca 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 are not valid or misspelled
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
grt.ca 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grt.ca can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that 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.
grt.ca
Open Graph description is not detected on the main page of 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: