4.4 sec in total
46 ms
3.8 sec
512 ms
Click here to check amazing TTC content for Canada. Otherwise, check out these important facts you probably never knew about ttc.ca
Visit ttc.caWe analyzed Ttc.ca page load time and found that the first response time was 46 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ttc.ca performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value20.6 s
0/100
25%
Value12.1 s
4/100
10%
Value6,750 ms
0/100
30%
Value0.418
23/100
15%
Value27.7 s
0/100
10%
46 ms
443 ms
147 ms
330 ms
273 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Ttc.ca, 52% (46 requests) were made to Cdn.ttc.ca and 22% (19 requests) were made to Whitelabel.triplinx.ca. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Cdn.ttc.ca.
Page size can be reduced by 295.2 kB (8%)
3.6 MB
3.3 MB
In fact, the total size of Ttc.ca main page is 3.6 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. 80% 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 1.9 MB which makes up the majority of the site volume.
Potential reduce by 47.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. This page needs HTML code to be minified as it can gain 6.5 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 47.1 kB or 80% of the original size.
Potential reduce by 37.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. TTC images are well optimized though.
Potential reduce by 122.1 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. This website has mostly compressed JavaScripts.
Potential reduce by 88.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. Ttc.ca needs all CSS files to be minified and compressed as it can save up to 88.4 kB or 46% of the original size.
Number of requests can be reduced by 45 (58%)
78
33
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TTC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
ttc.ca
46 ms
www.ttc.ca
443 ms
optimized-min.css
147 ms
optimized-min.css
330 ms
optimized-min.css
273 ms
optimized-min.css
379 ms
jquery.min.js
31 ms
optimized-min.js
1013 ms
optimized-min.js
338 ms
optimized-min.js
277 ms
optimized-min.js
493 ms
optimized-min.js
492 ms
optimized-min.js
493 ms
optimized-min.js
500 ms
index.js
511 ms
optimized-min.js
630 ms
gtm.js
120 ms
JourneyPlanner
1030 ms
TTC-LOGO.svg
130 ms
search.svg
188 ms
schedules.svg
190 ms
fares-passes.svg
132 ms
service-advisories.svg
335 ms
customer-service.svg
523 ms
WheelTrans-icon.svg
324 ms
accessibility-revised.svg
336 ms
RidingTheTTC-icon.svg
338 ms
News-icon.svg
524 ms
diversity.svg
552 ms
trip-planner.svg
552 ms
TTC17-OpsStock-7076.jpg
929 ms
G-04-B003-Subway-01.svg
924 ms
G-04-B006-Streetcars-Buses-02.svg
920 ms
G-04-A102-Elevator_RGB.svg
923 ms
1024X512-web_ONE-FARE_TTC-All_V1.jpg
925 ms
redarrow.svg
921 ms
Transit-enforcement-CTA-1216x448.png
1309 ms
Lifestyle-Stock-2011011-5188-2.jpg
1210 ms
external-link.svg
926 ms
back-to-top-arrow.svg
998 ms
128x128_Twitter_White.svg
999 ms
128x128_Facebook_White.svg
1026 ms
128x128_LI_White.svg
995 ms
128x128_Insta_White.svg
1203 ms
128x128_Youtube_White.svg
1207 ms
swz721medium-webfont-woff.woff
1263 ms
swz721normal-webfont-woff.woff
1163 ms
swz721light-webfont-woff.woff
1357 ms
swz721bold-webfont-woff.woff
1408 ms
js
58 ms
js
168 ms
js
248 ms
analytics.js
347 ms
beacon
344 ms
siteanalyze_6084610.js
375 ms
9vc7cd4g3b
369 ms
beacon
338 ms
collect
301 ms
clarity.js
296 ms
LiveAlertsWidget_1ec33fc7_chunk.css
389 ms
LiveAlertsWidget_2d17da78.js
656 ms
site-637970872864063931.css
373 ms
print-637970872864063931.css
309 ms
LinesColor-v638503776000000000.css
332 ms
white-label-637970872864063931.css
412 ms
algoliasearch.min.js
198 ms
Base-vendor-637970872864063931.js
613 ms
Base-637970872864063931.js
577 ms
script-4-637970872864063931.js
719 ms
Map-637970872864063931.js
808 ms
bundle-map-637970872864063931.js
577 ms
logo.png
777 ms
select-arrow.svg
333 ms
ProximaNova-Regular.woff
641 ms
ProximaNova-SemiBold.woff
307 ms
metrolinx.woff
856 ms
adobeblank.woff
870 ms
collect
376 ms
png8
276 ms
RetrievePointsInBoundingBox
237 ms
default-legend-template.html
384 ms
collect
215 ms
collect
162 ms
js
51 ms
ga-audiences
298 ms
GetLegend
124 ms
collect
17 ms
c.gif
8 ms
ttc.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-hidden="true"] elements contain focusable descendents
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
ttc.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
Missing source maps for large first-party JavaScript
ttc.ca SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ttc.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 Ttc.ca main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
ttc.ca
Open Graph description is not detected on the main page of TTC. 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: