2.8 sec in total
292 ms
2.2 sec
355 ms
Welcome to apl.washington.edu homepage info - get ready to check APL Washington best content for United States right away, or after learning these important things about apl.washington.edu
Visit apl.washington.eduWe analyzed Apl.washington.edu page load time and found that the first response time was 292 ms and then it took 2.6 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.
apl.washington.edu performance score
name
value
score
weighting
Value8.9 s
0/100
10%
Value32.3 s
0/100
25%
Value11.5 s
5/100
10%
Value50 ms
100/100
30%
Value0
100/100
15%
Value9.9 s
27/100
10%
292 ms
68 ms
135 ms
135 ms
139 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 98% of them (99 requests) were addressed to the original Apl.washington.edu, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Apl.washington.edu.
Page size can be reduced by 3.5 MB (66%)
5.3 MB
1.8 MB
In fact, the total size of Apl.washington.edu main page is 5.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. 45% of websites need less resources to load. Images take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 31.4 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 31.4 kB or 83% of the original size.
Potential reduce by 3.3 MB
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, APL Washington needs image optimization as it can save up to 3.3 MB or 65% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 75.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 75.9 kB or 69% of the original size.
Potential reduce by 37.7 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. Apl.washington.edu needs all CSS files to be minified and compressed as it can save up to 37.7 kB or 77% of the original size.
Number of requests can be reduced by 47 (47%)
99
52
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of APL 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 21 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
apl.washington.edu
292 ms
font_faces.css
68 ms
main.css
135 ms
general.css
135 ms
framework-vert.css
139 ms
layoutAssistant.css
136 ms
layout_objects.css
137 ms
modal_bg.css
134 ms
buttons.css
201 ms
images.css
198 ms
videos.css
202 ms
animation_strip.css
206 ms
lists.css
205 ms
video_strip.css
202 ms
page_items.css
264 ms
page_menu.css
264 ms
page_filters.css
266 ms
page_content.css
265 ms
zoom_image.css
266 ms
carousel.css
267 ms
research.css
327 ms
people.css
328 ms
jobs.css
330 ms
campus_map.css
330 ms
in_the_news.css
331 ms
publications.css
331 ms
seminars.css
393 ms
notices.css
392 ms
modifiers.css
394 ms
AjaxRequest.js
397 ms
JSON.js
395 ms
Utils.js
396 ms
Network.js
456 ms
Browser.js
461 ms
Transform.js
459 ms
Actions.js
460 ms
BrowserWindow.js
460 ms
Site.js
408 ms
Menus.js
402 ms
PageMenu.js
404 ms
Buttons.js
404 ms
Images.js
404 ms
YouTubeVideos.js
404 ms
PageItems.js
404 ms
AnimationStrips.js
402 ms
PageFilters.js
403 ms
PageGrid.js
400 ms
Notices.js
402 ms
Carousel.js
435 ms
bg_image.jpg
570 ms
bg_image-repeat.jpg
80 ms
spacer.png
81 ms
title-vert.png
140 ms
apl-uw_logo-norm.png
83 ms
menu_bg-15_trans.png
82 ms
menu_shadow-vert-left.png
139 ms
menu_shadow-vert-middle.png
142 ms
menu_shadow-vert-right.png
139 ms
uw_band-left.png
142 ms
uw_patch-left.png
199 ms
youtube-small.png
199 ms
facebook-small.png
201 ms
footer_shadow-vert-left.png
202 ms
footer_shadow-vert-middle.png
203 ms
footer_shadow-vert-right.png
267 ms
footer_bg_trans.png
265 ms
mars_pixl-600x400.png
1066 ms
psw2016_carousel_img_600x400.png
727 ms
air_swift-600x400.png
1063 ms
inner_shelf-600x400.png
1096 ms
biennial_report_2015-600x400.png
1194 ms
btn_play-norm.png
631 ms
more_info-norm.png
696 ms
btn_previous-norm.png
763 ms
btn_next-norm.png
792 ms
btn_previous-norm.png
829 ms
btn_next-norm.png
861 ms
loading_animation_strip_v1.png
895 ms
btn_previous-hover.png
927 ms
btn_previous-active.png
964 ms
btn_next-hover.png
994 ms
btn_next-active.png
1030 ms
btn_play-hover.png
1062 ms
btn_play-active.png
1079 ms
OpenSans-Regular-webfont.woff
1101 ms
btn_pause-hover.png
1054 ms
btn_pause-active.png
1075 ms
trans_black_75.png
1084 ms
trans_blue_4180af_20.png
1088 ms
ga.js
29 ms
__utm.gif
11 ms
trans_black_65.png
1062 ms
trans_black_15.png
1062 ms
article_438.png
1063 ms
article_437.png
1092 ms
article_436.png
1162 ms
publication_2466.png
1066 ms
publication_2465.png
1068 ms
publication_2458.png
1066 ms
pulldown_menu_bg_gradient.png
1067 ms
trans_black_85.png
1097 ms
apl.washington.edu accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
apl.washington.edu best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Page has valid source maps
apl.washington.edu SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
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 Apl.washington.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 Apl.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.
apl.washington.edu
Open Graph description is not detected on the main page of APL 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: