5.1 sec in total
371 ms
4.2 sec
497 ms
Welcome to goingstrong.gotransit.com homepage info - get ready to check GO Ingstrong Transit best content for Canada right away, or after learning these important things about goingstrong.gotransit.com
A division of Metrolinx, GO Transit is the regional public transit service for the Greater Golden Horseshoe.
Visit goingstrong.gotransit.comWe analyzed Goingstrong.gotransit.com page load time and found that the first response time was 371 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
goingstrong.gotransit.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value24.0 s
0/100
25%
Value13.5 s
2/100
10%
Value20,650 ms
0/100
30%
Value0.243
51/100
15%
Value31.5 s
0/100
10%
371 ms
157 ms
43 ms
41 ms
443 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Goingstrong.gotransit.com, 7% (4 requests) were made to Api.gotransit.com and 5% (3 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Api.gotransit.com.
Page size can be reduced by 2.1 MB (74%)
2.8 MB
718.0 kB
In fact, the total size of Goingstrong.gotransit.com main page is 2.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. 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. CSS take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 98.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 98.8 kB or 86% of the original size.
Potential reduce by 15.1 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. GO Ingstrong Transit images are well optimized though.
Potential reduce by 180.0 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 180.0 kB or 67% of the original size.
Potential reduce by 1.8 MB
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. Goingstrong.gotransit.com needs all CSS files to be minified and compressed as it can save up to 1.8 MB or 98% of the original size.
Number of requests can be reduced by 28 (55%)
51
23
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GO Ingstrong Transit. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
www.gotransit.com
371 ms
app.css
157 ms
config.js
43 ms
modernizr.custom.js
41 ms
vendor.js
443 ms
home.page.js
100 ms
navigation.page.js
100 ms
pageCustom.js
76 ms
gtm.js
631 ms
sprite.svg
598 ms
sprite.svg
589 ms
sprite.svg
590 ms
s.png
586 ms
sprite.svg
177 ms
sprite.svg
198 ms
Polaris-Book.woff
193 ms
Polaris-Bold.woff
188 ms
Polaris-Medium.woff
188 ms
copies
153 ms
app.js
167 ms
algoliasearch.min.js
165 ms
autocomplete.min.js
167 ms
algoliasearch.helper.min.js
168 ms
optimize.js
804 ms
hotjar-2426167.js
1229 ms
fbevents.js
1217 ms
iframe_api
1379 ms
pixie.js
1369 ms
up_loader.1.1.0.js
1346 ms
js
925 ms
activityi;src=9896292;type=pagev0;cat=dcm-g0;ord=1;num=4822651146818;gtm=2wga30;auiddc=1633448534.1664949000;~oref=https%3A%2F%2Fwww.gotransit.com%2F
1491 ms
activityi;src=11500151;type=metro005;cat=dcm-g0;ord=6214090417791;gtm=2wga30;auiddc=1633448534.1664949000;~oref=https%3A%2F%2Fwww.gotransit.com%2F
1461 ms
reacturl
958 ms
newfare-date
1204 ms
all
1270 ms
all
1549 ms
sprite.svg
666 ms
chevron-down.svg
434 ms
eTicket_444x210.jpg
587 ms
336x150-train-service-change-orange.jpg
425 ms
general
1307 ms
Spring20_GO_Hero_EN.jpg
752 ms
analytics.js
333 ms
1805725693006529
190 ms
modules.cbd9768ba80ba0be5b17.js
375 ms
box-69edcc3187336f9b0a3fbb4c73be9fe6.html
365 ms
pixie
754 ms
collect
122 ms
www-widgetapi.js
179 ms
pixie
437 ms
pixie
699 ms
435 ms
830913800735268
132 ms
collect
810 ms
src=11500151;type=metro005;cat=dcm-g0;ord=6214090417791;gtm=2wga30;auiddc=1633448534.1664949000;~oref=https%3A%2F%2Fwww.gotransit.com%2F
567 ms
src=9896292;type=pagev0;cat=dcm-g0;ord=1;num=4822651146818;gtm=2wga30;auiddc=1633448534.1664949000;~oref=https%3A%2F%2Fwww.gotransit.com%2F
558 ms
ga-audiences
60 ms
goingstrong.gotransit.com 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
ARIA IDs are not unique
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
goingstrong.gotransit.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
goingstrong.gotransit.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Goingstrong.gotransit.com 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 Goingstrong.gotransit.com 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.
goingstrong.gotransit.com
Open Graph description is not detected on the main page of GO Ingstrong Transit. 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: