4 sec in total
287 ms
2.8 sec
834 ms
Welcome to washington.edu homepage info - get ready to check Washington best content for United States right away, or after learning these important things about washington.edu
University of Washington
Visit washington.eduWe analyzed Washington.edu page load time and found that the first response time was 287 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
washington.edu performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value21.7 s
0/100
25%
Value8.5 s
18/100
10%
Value930 ms
30/100
30%
Value0.005
100/100
15%
Value18.6 s
3/100
10%
287 ms
435 ms
47 ms
202 ms
189 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 30% of them (25 requests) were addressed to the original Washington.edu, 17% (14 requests) were made to Uw-s3-cdn.s3.us-west-2.amazonaws.com and 7% (6 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Uw-s3-cdn.s3.us-west-2.amazonaws.com.
Page size can be reduced by 329.1 kB (14%)
2.3 MB
2.0 MB
In fact, the total size of Washington.edu 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. 65% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 58.6 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 58.6 kB or 76% of the original size.
Potential reduce by 15.5 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. Washington images are well optimized though.
Potential reduce by 61.7 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 61.7 kB or 62% of the original size.
Potential reduce by 193.3 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. Washington.edu needs all CSS files to be minified and compressed as it can save up to 193.3 kB or 84% of the original size.
Number of requests can be reduced by 31 (48%)
64
33
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Washington. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
www.washington.edu
287 ms
style.css
435 ms
css
47 ms
style.css
202 ms
underscore.min.js
189 ms
jquery.js
513 ms
jquery-migrate.js
188 ms
backbone.min.js
191 ms
site.js
490 ms
homepage.js
256 ms
gtm4wp-form-move-tracker.js
147 ms
homepage-event-tracking.js
161 ms
gtm.js
172 ms
year-end-story-B-desktop.jpg
769 ms
year-end-story-mobile.jpg
545 ms
ray-haug-desktopC.jpg
910 ms
ray-haug-mobileB.jpg
744 ms
BITB_Loop_2500x700_v4_dark.jpg
510 ms
boys-in-the-boat-mobile-gradient.jpg
877 ms
uwfb-national-tile-game.jpg
1080 ms
Screenshot-2023-12-05-at-1.52.18-PM.jpg
1024 ms
climate-change-wave-377x160-1.jpg
906 ms
seattle-skyline-377x160.jpg
906 ms
pulltogethertile.png
1094 ms
updated-research-fast-fact.png
996 ms
27-percent-first-to-attend-college-stat.png
995 ms
nobel-prize-2017.png
993 ms
uw-sprite.svg
143 ms
uw-sprite-focus.svg
137 ms
slash.svg
135 ms
stripes-dark-tile.svg
136 ms
pause.svg
129 ms
quad.jpg
237 ms
footer.jpg
230 ms
boundless.png
229 ms
gtm.js
136 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff
181 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff
295 ms
encodesanscompressed-600-semibold-webfont.woff
99 ms
encodesanscompressed-700-bold-webfont.woff
98 ms
encodesanscompressed-800-extrabold-webfont.woff
99 ms
encodesanscompressed-900-black-webfont.woff
259 ms
encodesanscondensed-400-regular-webfont.woff
269 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexg.woff
362 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexg.woff
394 ms
865 ms
search.svg
179 ms
js
97 ms
js
160 ms
analytics.js
104 ms
insight.min.js
368 ms
uwmunchkin.min.js
671 ms
siteanalyze_47642.js
502 ms
9gkmyab2zh
378 ms
Bootstrap.js
162 ms
up.js
384 ms
fbevents.js
315 ms
js
105 ms
collect
408 ms
collect
417 ms
js
256 ms
serverComponent.php
60 ms
insight_tag_errors.gif
238 ms
200 ms
d3d14424fac71699bdbff068d9b1184b.js
150 ms
1fc8553a686089c9698160748311de5d.js
153 ms
clarity.js
176 ms
collect
60 ms
collect
59 ms
image.aspx
27 ms
ga-audiences
49 ms
ga-audiences
42 ms
munchkin.js
17 ms
IsGDPR
344 ms
iframe
8 ms
iframe
14 ms
iframe
46 ms
iframe
74 ms
pixel
45 ms
munchkin.js
9 ms
18 ms
visitWebPage
288 ms
cksync
41 ms
c.gif
8 ms
washington.edu 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
washington.edu 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
washington.edu SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Washington.edu 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 Washington.edu 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.
washington.edu
Open Graph description is not detected on the main page of Washington. 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: