3.7 sec in total
209 ms
3 sec
445 ms
Click here to check amazing Pce UW content for United States. Otherwise, check out these important facts you probably never knew about pce.uw.edu
We make it possible for you to keep learning at the University of Washington, even if you work full time or live outside of the Seattle area.
Visit pce.uw.eduWe analyzed Pce.uw.edu page load time and found that the first response time was 209 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
pce.uw.edu performance score
name
value
score
weighting
Value3.1 s
48/100
10%
Value6.4 s
9/100
25%
Value4.8 s
67/100
10%
Value340 ms
74/100
30%
Value0
100/100
15%
Value11.6 s
18/100
10%
209 ms
847 ms
525 ms
729 ms
423 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 62% of them (39 requests) were addressed to the original Pce.uw.edu, 6% (4 requests) were made to S.ytimg.com and 5% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Pce.uw.edu.
Page size can be reduced by 2.8 MB (65%)
4.3 MB
1.5 MB
In fact, the total size of Pce.uw.edu main page is 4.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. 55% of websites need less resources to load. CSS take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 51.8 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 21.5 kB, which is 32% 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 51.8 kB or 76% of the original size.
Potential reduce by 6.4 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. Pce UW images are well optimized though.
Potential reduce by 506.8 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 506.8 kB or 68% of the original size.
Potential reduce by 2.2 MB
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. Pce.uw.edu needs all CSS files to be minified and compressed as it can save up to 2.2 MB or 96% of the original size.
Number of requests can be reduced by 21 (47%)
45
24
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pce UW. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
pce.uw.edu
209 ms
www.pce.uw.edu
847 ms
bootstrap.css
525 ms
main.css
729 ms
ScriptResource.axd
423 ms
vendor.js
534 ms
main.js
469 ms
gtm.js
223 ms
sdk.js
183 ms
print.css
214 ms
open-sans-regular-webfont.woff
155 ms
T8Yfz-H--ew
234 ms
sprite.svg
127 ms
gold-bar.svg
126 ms
GetAzureFile.aspx
288 ms
GetAzureFile.aspx
404 ms
GetAzureFile.aspx
272 ms
GetAzureFile.aspx
546 ms
GetAzureFile.aspx
316 ms
GetAzureFile.aspx
401 ms
GetAzureFile.aspx
407 ms
GetAzureFile.aspx
631 ms
GetAzureFile.aspx
546 ms
GetAzureFile.aspx
547 ms
GetAzureFile.aspx
553 ms
GetAzureFile.aspx
553 ms
GetAzureFile.aspx
609 ms
GetAzureFile.aspx
606 ms
GetAzureFile.aspx
614 ms
GetAzureFile.aspx
739 ms
footer.jpg
625 ms
iframe_api
116 ms
GetAzureFile.aspx
779 ms
encodesanscompressed-800-extrabold-webfont.woff
585 ms
encodesanscompressed-600-semibold-webfont.woff
575 ms
open-sans-700-webfont.woff
600 ms
encodesanscompressed-300-light-webfont.woff
928 ms
encodesansnarrow-400-regular-webfont.woff
1087 ms
encodesanscompressed-700-bold-webfont.woff
670 ms
open-sans-300italic-webfont.woff
1064 ms
encodesanscompressed-900-black-webfont.woff
708 ms
open-sans-300-webfont.woff
760 ms
glyphicons-halflings-regular.woff
796 ms
168 ms
xd_arbiter.php
123 ms
analytics.js
119 ms
conversion_async.js
83 ms
fbevents.js
50 ms
www-embed-player-vflQrT_sR.css
132 ms
www-embed-player.js
153 ms
base.js
209 ms
www-widgetapi.js
189 ms
101 ms
52 ms
collect
26 ms
collect
56 ms
53 ms
collect
178 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
16 ms
ad_status.js
71 ms
ga-audiences
60 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
98 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
108 ms
pce.uw.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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pce.uw.edu 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
pce.uw.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pce.uw.edu 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 Pce.uw.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.
pce.uw.edu
Open Graph description is not detected on the main page of Pce UW. 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: