5 sec in total
184 ms
3.9 sec
911 ms
Visit performance.seattle.gov now to see the best up-to-date Performance Seattle content for United States and also check out these interesting facts you probably never knew about performance.seattle.gov
Visit performance.seattle.govWe analyzed Performance.seattle.gov page load time and found that the first response time was 184 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
performance.seattle.gov performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value21.0 s
0/100
25%
Value16.7 s
0/100
10%
Value1,630 ms
12/100
30%
Value0.226
55/100
15%
Value25.6 s
0/100
10%
184 ms
600 ms
152 ms
226 ms
230 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 67% of them (36 requests) were addressed to the original Performance.seattle.gov, 20% (11 requests) were made to Use.typekit.net and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Performance.seattle.gov.
Page size can be reduced by 1.0 MB (72%)
1.4 MB
412.1 kB
In fact, the total size of Performance.seattle.gov main page is 1.4 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. 45% of websites need less resources to load. Javascripts take 954.2 kB which makes up the majority of the site volume.
Potential reduce by 152.0 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 152.0 kB or 78% of the original size.
Potential reduce by 2.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. Obviously, Performance Seattle needs image optimization as it can save up to 2.6 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 635.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 635.6 kB or 67% of the original size.
Potential reduce by 244.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. Performance.seattle.gov needs all CSS files to be minified and compressed as it can save up to 244.6 kB or 85% of the original size.
Number of requests can be reduced by 19 (44%)
43
24
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Performance Seattle. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
performance.seattle.gov
184 ms
performance.seattle.gov
600 ms
base.css
152 ms
socrata-apps.css
226 ms
ss-pika.css
230 ms
govstat-base.css
237 ms
errors.js
249 ms
components.css
245 ms
ibw7sgf.js
243 ms
current_site.css
245 ms
govstat_site.css
296 ms
mixpanel-analytics.js
305 ms
base.js
631 ms
new-base.js
248 ms
canvas.js
451 ms
jquery.min.js
79 ms
performance.seattle.gov
104 ms
analytics.js
91 ms
634D0BF9-6CC6-455A-B68E-2142F079AB84
89 ms
77B337BC-B4EA-4048-AF72-C5CDE20125DE
89 ms
FD4A4F57-D49D-4D1C-8BD6-B5AE4249FF07
107 ms
03C8D9C2-4093-4A0E-8061-5E186AB5805B
106 ms
f7ARFQ3KNAOdII41NBNSL_jM_5C8PtPHRsQiprenhVo
154 ms
s7brHshmBysyzFACvsm8LUQqh2crvfo3cY913mO-ybE
2601 ms
gHCj1vAa9egLQDF4UJIJq1oyyUJwAQ05eFY5xWII_h4
1744 ms
v7WeGgTflxaHkNsqGlasUsJcGc0Rg1knIkLdK4XWYic
938 ms
Tp34vFReuLGsZiFA-LFL1iqIH6X-1AE6CS5fo7Kx6AI
1040 ms
O990jJ5WOAwcTmrNuPPkI8m6OWWvsKKE9CbY7XTT0Xg
1957 ms
8uTqBq42fmPcaeFxK3TKT0__ZQ33YfClppxeXJlh0Mc
640 ms
nRJLoIpDVVUd4uy0G7qdsZfLtm5qu9IpTV-MjmcD_mw
1078 ms
fe7nmK_bpei28qqOOYG64Pl8Lg3fMkFnhLiS7I60y49ff5fRgsMWeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
54 ms
66kCel_hUndEcUX_soEa6mSLix5R9Fj4OaeEp643hxMff5eRgsMWeMJ6Mk6g5MZfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
81 ms
dVO_34o4Avjv1Enp_Ypil-2oUbfAYzuWJRFd7q7HL4XffJcFgsMWeMJ6Mk6f5Mb.woff
105 ms
HCFijVj9ZMBZIsSQuoJieyO3iwe9ypvAqJMwG6aU3tJffwAQgsMWeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
129 ms
collect
47 ms
font-awesome.min.css
201 ms
mixpanel-2.2.min.js
200 ms
ipwr-ycfe.json
613 ms
spinner_background.png
556 ms
menu_icons.png
564 ms
collect
41 ms
cLL67R0h99hLCxa6nWvmA8CUT0yxzYGpbOcs3ue8GNXffO-LgsMWeMJ6Mk6f5Mt.woff
50 ms
vrlWZfSfCFzdzCYhj9je7yaw5y_EGCVU8xeBP313ljtffO7LgsMWeMJ6Mk6f5gI.woff
51 ms
2hhbDQEBcWx1z9YfDGURW64Y8SFX95BSyueLRzCEowMffOALgsMWeMJ6Mk6f5Mb.woff
49 ms
_-R0gdV_SpbwEr1jVhGSoe4kgpy_7GHvRxYXjTh3tZbffOeLgsMWeMJ6Mk6f5MJ.woff
50 ms
q5Lz9UMgTagG3s7jgnyVoJ4OVCvdpcZTnHIj342bl4GffOcLgsMWeMJ6Mk6f5MS.woff
71 ms
snuffleupasnake.gif
561 ms
BrandedSpinner.gif
614 ms
p.gif
134 ms
socket.io
429 ms
client-bridge
708 ms
rows.json
739 ms
191 ms
print.css
85 ms
performance.seattle.gov 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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
performance.seattle.gov best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
performance.seattle.gov 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 Performance.seattle.gov 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 Performance.seattle.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.
performance.seattle.gov
Open Graph description is not detected on the main page of Performance Seattle. 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: