8.1 sec in total
191 ms
7.6 sec
305 ms
Visit soundtransit.org now to see the best up-to-date Sound Transit content for United States and also check out these interesting facts you probably never knew about soundtransit.org
Ride the Wave
Visit soundtransit.orgWe analyzed Soundtransit.org page load time and found that the first response time was 191 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
soundtransit.org performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value10.4 s
0/100
25%
Value8.1 s
21/100
10%
Value2,380 ms
5/100
30%
Value0.001
100/100
15%
Value17.7 s
4/100
10%
191 ms
404 ms
147 ms
252 ms
168 ms
Our browser made a total of 98 requests to load all elements on the main page. We found that 80% of them (78 requests) were addressed to the original Soundtransit.org, 8% (8 requests) were made to Apis.google.com and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Soundtransit.org.
Page size can be reduced by 304.3 kB (59%)
517.4 kB
213.0 kB
In fact, the total size of Soundtransit.org main page is 517.4 kB. 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 201.0 kB which makes up the majority of the site volume.
Potential reduce by 70.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 70.1 kB or 80% of the original size.
Potential reduce by 30.8 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. Obviously, Sound Transit needs image optimization as it can save up to 30.8 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 36.6 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 36.6 kB or 60% of the original size.
Potential reduce by 166.8 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. Soundtransit.org needs all CSS files to be minified and compressed as it can save up to 166.8 kB or 83% of the original size.
Number of requests can be reduced by 46 (50%)
92
46
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sound 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 from 13 to 1 for CSS and as a result speed up the page load time.
soundtransit.org
191 ms
www.soundtransit.org
404 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
147 ms
css_TGGIY6aKm-mOfr1AdmhQHE8UC3b4erTcShbRaIsGxZM.css
252 ms
css_EPsgvacVXxxhwhLr4DGj8P1D4es4L_QnnRJPHn_TJHE.css
168 ms
css_MnXiytJtb186Ydycnpwpw34cuUsHaKc80ey5LiQXhSY.css
177 ms
css_LdPNeuK50isVMHb5n7Y2HQrSqL13xICgNfA5NDQmVRs.css
393 ms
player.css
381 ms
player_slide.css
223 ms
player_playlist.css
256 ms
trip-planner-form.css
349 ms
css_wXAPcct2AcCm0D3eDIyIaY-W5HLro4jq8UK3sgB4v2k.css
317 ms
soundtransit-front.css
348 ms
css_qmrgrnc-8W1h26e9w463CzmNbR-zBlnu8lnAnI4jv7Y.css
348 ms
modernizr.custom.14957.js
430 ms
js_jhnccERkDPQ8UmghBLZyq9it6KYh2arsF7w_E6IRoss.js
512 ms
js_oEeRT9dYr67w-PCJSYMojgcEv1-FI_l-o6gSQwNNjSg.js
625 ms
js_XTy727E9vPxT4ZFsuB5hkAB86frtHrlHmzlJ4_nVVj0.js
486 ms
js_4SNKk3ZRpNAsvmOmFu8cbIXwM_AkVaF1McHflBi968M.js
487 ms
swfobject.js
487 ms
player.js
624 ms
js_6lR3Uk2qAZ_UxnZq_P9tXffKkebKasSna--WglAKn8g.js
623 ms
trip-planner-form.js
622 ms
util.js
622 ms
js_T2QH8sXOyArCAq5KhureH1gsYXF6wy4SRBdrTMrwKjE.js
623 ms
js_1-Ru_tXQVHUJ7kiUtCKEDzIjMNr_n0Xj-C_K_0xOa-4.js
792 ms
platform.js
190 ms
bg-body.gif
340 ms
analytics.js
44 ms
HomePageSUBHero_ST3_272x135_07082015.png
206 ms
icon_airport_33x33.jpg
206 ms
ICON_WINTER_33X33.jpg
206 ms
ICON_PARKING_33X33.jpg
207 ms
ICON_EVENTS_33X33.jpg
192 ms
toggle.png
192 ms
fares-icon.png
192 ms
parking-icon.png
193 ms
location-icon.png
192 ms
collect
86 ms
cb=gapi.loaded_0
44 ms
cb=gapi.loaded_1
26 ms
follow
225 ms
collect
163 ms
postmessageRelay
76 ms
rs=AGLTcCOFWKsnI38o6vFCDk5Jl0cU7zLIcw
10 ms
rs=AGLTcCNqoVEd4LqzgXRuOn4SyAGjnQoU1A
403 ms
rs=AGLTcCP5zEl6jagebztunOiTSYyE5oZm1g
627 ms
api.js
597 ms
core:rpc:shindig.random:shindig.sha1.js
950 ms
2536007149-postmessagerelay.js
1021 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
1040 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
1026 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
1025 ms
widgets.js
483 ms
sdk.js
930 ms
bg-wrapper.gif
481 ms
logo.gif
757 ms
bg-search-box.png
755 ms
sep-top-nav.gif
735 ms
bg-nav.png
755 ms
icon-home.png
735 ms
sep-main-nav.png
756 ms
bg-center.gif
823 ms
icon-shovel.png
823 ms
sprite-front.png
856 ms
icon_homepagenews_238X64.gif
823 ms
a-flag.png
822 ms
b-flag.png
823 ms
calendar.png
1566 ms
bus-modal-icon.png
1540 ms
sounder-modal-icon.png
1564 ms
link-modal-icon.png
1565 ms
wheelchair-icon.png
1566 ms
trip-submit.png
1566 ms
bg-footer-lines.png
1595 ms
bg-footer-bottom.gif
1566 ms
bg-footer.gif
1595 ms
ico-footer01.gif
1594 ms
ico-footer02.gif
5484 ms
ico-footer03.gif
1595 ms
ico-footer04.gif
1595 ms
ico-footer05.gif
1595 ms
sprite-global.png
1596 ms
12694
728 ms
facebook.png
293 ms
twitter.png
291 ms
email.png
262 ms
back.png
290 ms
next.png
271 ms
loading.gif
271 ms
ui-bg_flat_75_ffffff_40x100.png
270 ms
ui-bg_glass_75_e6e6e6_1x400.png
271 ms
ui-icons_888888_256x240.png
295 ms
ui-icons_888888_256x240.png
295 ms
ui-icons_222222_256x240.png
295 ms
FACEBOOK_012616_Link%20Launch%20Anouncement_Still.jpg
423 ms
play_over.png
395 ms
xd_arbiter.php
114 ms
soundtransit.org accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
soundtransit.org 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
soundtransit.org 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Soundtransit.org 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 Soundtransit.org 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.
soundtransit.org
Open Graph data is detected on the main page of Sound Transit. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: