Tools & Wizards About Us
tripplanner.kingcounty.gov screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 42

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

tripplanner.kingcounty.gov

INFO-Web Transit Information

Page Load Speed

3.1 sec in total

First Response

680 ms

Resources Loaded

2.2 sec

Page Rendered

189 ms

tripplanner.kingcounty.gov screenshot

About Website

Visit tripplanner.kingcounty.gov now to see the best up-to-date Tripplanner Kingcounty content for United States and also check out these interesting facts you probably never knew about tripplanner.kingcounty.gov

INFO-Web Trip Planner allows you to plan a trip, view upcoming departure times, and to view the positions of vehicles in real time.

Visit tripplanner.kingcounty.gov

Key Findings

We analyzed Tripplanner.kingcounty.gov page load time and found that the first response time was 680 ms and then it took 2.4 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.

Performance Metrics

tripplanner.kingcounty.gov performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value25.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value35.4 s

0/100

25%

SI (Speed Index)

Value27.7 s

0/100

10%

TBT (Total Blocking Time)

Value1,690 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.159

73/100

15%

TTI (Time to Interactive)

Value34.5 s

0/100

10%

Network Requests Diagram

tripplanner.kingcounty.gov

680 ms

system.js

134 ms

MapDraw.css

138 ms

detect.js

138 ms

MapNav.js

203 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 40% of them (39 requests) were addressed to the original Tripplanner.kingcounty.gov, 38% (37 requests) were made to Maps.googleapis.com and 9% (9 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (680 ms) belongs to the original domain Tripplanner.kingcounty.gov.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (63%)

Content Size

2.3 MB

After Optimization

834.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tripplanner.kingcounty.gov main page is 2.3 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.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 56.6 kB

  • Original 66.5 kB
  • After minification 64.5 kB
  • After compression 9.9 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 56.6 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 18.4 kB

  • Original 467.0 kB
  • After minification 448.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. Tripplanner Kingcounty images are well optimized though.

JavaScript Optimization

-78%

Potential reduce by 1.3 MB

  • Original 1.7 MB
  • After minification 1.3 MB
  • After compression 367.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 1.3 MB or 78% of the original size.

CSS Optimization

-86%

Potential reduce by 49.0 kB

  • Original 57.2 kB
  • After minification 36.4 kB
  • After compression 8.2 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. Tripplanner.kingcounty.gov needs all CSS files to be minified and compressed as it can save up to 49.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (53%)

Requests Now

93

After Optimization

44

  • Images
  • JavaScript
  • CSS

The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tripplanner Kingcounty. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

tripplanner.kingcounty.gov

tripplanner.kingcounty.gov

680 ms

system.js

system.js

134 ms

MapDraw.css

MapDraw.css

138 ms

detect.js

detect.js

138 ms

MapNav.js

MapNav.js

203 ms

InfoWeb.css

InfoWeb.css

139 ms

infowebFull.css

infowebFull.css

206 ms

Info.js

Info.js

200 ms

EventsInfo.js

EventsInfo.js

264 ms

Notifications.js

Notifications.js

265 ms

dateAndTimeFormats.js

dateAndTimeFormats.js

207 ms

prototype.js

prototype.js

336 ms

common.js

common.js

511 ms

utils.js

utils.js

271 ms

calendar.js

calendar.js

339 ms

calendar-setup.js

calendar-setup.js

328 ms

calendar-en.js

calendar-en.js

329 ms

js

js

86 ms

GoogleMapping.js

GoogleMapping.js

337 ms

header_footer.css

header_footer.css

139 ms

jquery.js

jquery.js

531 ms

jquery.fixer.js

jquery.fixer.js

395 ms

tab-menu.js

tab-menu.js

399 ms

logging.js

logging.js

403 ms

autocomplete.js

autocomplete.js

405 ms

ajax.js

ajax.js

465 ms

autocomplete.css

autocomplete.css

468 ms

layout-3d.css

layout-3d.css

278 ms

layout-common.css

layout-common.css

70 ms

ga.js

ga.js

43 ms

header_bg1.jpg

header_bg1.jpg

73 ms

minusSign.gif

minusSign.gif

70 ms

BtnBar.jpg

BtnBar.jpg

69 ms

ui-bg_grade_fff_e7f0f8_1x200.png

ui-bg_grade_fff_e7f0f8_1x200.png

71 ms

origin.png

origin.png

70 ms

BlackTabSmall.png

BlackTabSmall.png

72 ms

GreyTabSmall.png

GreyTabSmall.png

70 ms

reverseicon.png

reverseicon.png

137 ms

destination.png

destination.png

134 ms

calendar02.gif

calendar02.gif

137 ms

plusSign.gif

plusSign.gif

137 ms

access.gif

access.gif

136 ms

plan_a_trip_title.jpg

plan_a_trip_title.jpg

188 ms

metro_logo.png

metro_logo.png

232 ms

footer_bg1.jpg

footer_bg1.jpg

146 ms

king_county_logo.png

king_county_logo.png

158 ms

__utm.gif

__utm.gif

12 ms

BtnBarActive.jpg

BtnBarActive.jpg

79 ms

common.js

common.js

22 ms

map.js

map.js

48 ms

util.js

util.js

84 ms

geocoder.js

geocoder.js

73 ms

onion.js

onion.js

16 ms

openhand_8_8.cur

openhand_8_8.cur

96 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

97 ms

stats.js

stats.js

29 ms

controls.js

controls.js

28 ms

infowindow.js

infowindow.js

55 ms

css

css

107 ms

transparent.png

transparent.png

90 ms

marker.js

marker.js

22 ms

google4.png

google4.png

32 ms

mapcnt6.png

mapcnt6.png

67 ms

sv5.png

sv5.png

97 ms

tmapctrl.png

tmapctrl.png

90 ms

cb_scout5.png

cb_scout5.png

102 ms

tmapctrl4.png

tmapctrl4.png

88 ms

imgs8.png

imgs8.png

89 ms

vt

vt

60 ms

vt

vt

42 ms

vt

vt

39 ms

vt

vt

40 ms

vt

vt

49 ms

vt

vt

49 ms

vt

vt

48 ms

vt

vt

49 ms

vt

vt

76 ms

vt

vt

76 ms

vt

vt

76 ms

vt

vt

75 ms

vt

vt

74 ms

vt

vt

75 ms

vt

vt

84 ms

vt

vt

85 ms

vt

vt

88 ms

vt

vt

85 ms

vt

vt

85 ms

vt

vt

86 ms

vt

vt

95 ms

vt

vt

97 ms

vt

vt

110 ms

vt

vt

97 ms

vt

vt

98 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

75 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

85 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

99 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

119 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

17 ms

Accessibility Review

tripplanner.kingcounty.gov accessibility score

90

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

Best Practices

tripplanner.kingcounty.gov best practices score

42

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

tripplanner.kingcounty.gov SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tripplanner.kingcounty.gov 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 Tripplanner.kingcounty.gov 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.

Social Sharing Optimization

tripplanner.kingcounty.gov

Open Graph description is not detected on the main page of Tripplanner Kingcounty. 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: