3.8 sec in total
11 ms
2.8 sec
988 ms
Click here to check amazing Washington Post content. Otherwise, check out these important facts you probably never knew about washingtonpost.org
Breaking news and analysis on politics, business, world national news, entertainment more. In-depth DC, Virginia, Maryland news coverage including traffic, weather, crime, education, restaurant review...
Visit washingtonpost.orgWe analyzed Washingtonpost.org page load time and found that the first response time was 11 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
washingtonpost.org performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value16.9 s
0/100
25%
Value16.8 s
0/100
10%
Value10,360 ms
0/100
30%
Value0.319
36/100
15%
Value30.1 s
0/100
10%
11 ms
13 ms
33 ms
4 ms
32 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Washingtonpost.org, 31% (40 requests) were made to Washingtonpost.com and 11% (14 requests) were made to Js.washingtonpost.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Plugin.mediavoice.com.
Page size can be reduced by 1.7 MB (41%)
4.1 MB
2.4 MB
In fact, the total size of Washingtonpost.org main page is 4.1 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 251.5 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 251.5 kB or 81% of the original size.
Potential reduce by 44.1 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 Post images are well optimized though.
Potential reduce by 1.1 MB
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.1 MB or 69% of the original size.
Potential reduce by 233.9 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. Washingtonpost.org needs all CSS files to be minified and compressed as it can save up to 233.9 kB or 84% of the original size.
Number of requests can be reduced by 67 (60%)
112
45
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Washington Post. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
washingtonpost.org
11 ms
www.washingtonpost.com
13 ms
www.washingtonpost.com
33 ms
4 ms
32 ms
headerfonts.css
70 ms
ba39e182ae.css
33 ms
style.css
59 ms
f65e4f3f81.js
77 ms
head.min.js
75 ms
9adf0167ec.js
75 ms
16db91d4b3.js
96 ms
YTConfig.js
151 ms
e7f066f51e.js
98 ms
hi-pri-render.js
99 ms
loader.min.js
97 ms
06e27c89ae.js
98 ms
WapoVideoEmbed.min.js
98 ms
render.js
98 ms
ab2a22c20d.js
101 ms
7a5b554023.js
267 ms
b5411285f6.js
264 ms
938c258067.css
7 ms
a925dd0217.js
267 ms
main.js
264 ms
8f8c39c9d8.js
265 ms
identity-retargeting.js
265 ms
twp-masthead-415x57.svg
412 ms
images.washingtonpost.com
409 ms
thewashingtonpost-white-2x.png
292 ms
washingtonpost_black_32.png
292 ms
star-blue.jpg
292 ms
star-red.jpg
291 ms
crop_90Botsford_TRUMP_16_02_07_04781454875511.jpg
294 ms
L4A-clinton-cheer-3x2.jpg
292 ms
crop_9027071455129974.jpg
399 ms
crop_90Botsford_CRUZ_16_02_05_04251454727071.jpg
400 ms
crop_90031457647631.jpg
489 ms
crop_90bs241454706550.jpg
405 ms
AWSIntel-Logo.png
399 ms
imrs.php
416 ms
imrs.php
475 ms
crop_90White_Sox_LaRoche_Son_Baseball-0061b.jpg
654 ms
Aleppo-pair21458333251.jpg
592 ms
imrs.php
415 ms
imrs.php
487 ms
imrs.php
522 ms
imrs.php
522 ms
spacer.gif
590 ms
Ax1_module2.jpg
645 ms
cube.png
650 ms
images.washingtonpost.com
468 ms
images.washingtonpost.com
468 ms
images.washingtonpost.com
468 ms
images.washingtonpost.com
410 ms
images.washingtonpost.com
482 ms
images.washingtonpost.com
487 ms
images.washingtonpost.com
518 ms
AcoNCCs=
223 ms
WapoVideoEmbed.main.min.js
247 ms
318 ms
YTConfig.js
231 ms
iframe_api
439 ms
ad-sprite.png
425 ms
imrs.php
557 ms
p5ccfdkIC4w==
31 ms
Fzt2n2EAAAA=
30 ms
PostoniStandard-Regular.woff
402 ms
fontawesome-webfont.woff
223 ms
diversions-icons.woff
403 ms
amzn_ads.js
366 ms
info
365 ms
wp.css
451 ms
jstag
484 ms
moatcontent.js
420 ms
em.js
605 ms
WapoVideoPlayer.min.css
170 ms
streamsense.min.js
236 ms
92d280a2-7d90-11e0-b6cc-e4e4a8a38cf0
241 ms
WDSy9G5kYXAAH0yK4AAAA
2 ms
www-widgetapi.js
183 ms
pubsub.js
123 ms
iui3
169 ms
bid
313 ms
wp_secure.min.js
126 ms
underscore-min.js
106 ms
wprum.min.js
73 ms
259 ms
beacon.js
129 ms
chartbeat.js
314 ms
98 ms
LRXeR4KYJ9A
172 ms
pubads_impl_82.js
170 ms
jwplayer.js
77 ms
rta.js
272 ms
plugin.js
1080 ms
frame_2.3.3.html
1075 ms
JWPlayerConfig.js
24 ms
www-embed-player-vflfNyN_r.css
92 ms
www-embed-player.js
133 ms
base.js
227 ms
jwPlayerWrapper.min.js
94 ms
container.html
307 ms
ads
318 ms
ping
277 ms
streamsense.min.js
83 ms
vid_exclusions.js
157 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
63 ms
ad_status.js
51 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
55 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
55 ms
save
19 ms
ads
543 ms
acj
518 ms
trending-videos-overall.json
29 ms
polyfills.promise.js
7 ms
p
92 ms
bekle.css
11 ms
save
69 ms
index.html
86 ms
save
105 ms
index.html
76 ms
loading_wp_white_100.gif
50 ms
wAAABgAAAAAABcAAAQAAAAAAAAAAAAAAAAAAABsEAAAAAAAAAAAAAAACAAAABgAAYAQAAEAFAABABQAAQAYAAEAGAABABAAA4ASAAEAEAABABgAAQAYAAD0D4ABDBIAARgQAAIAEAACABIAASgOAAEMEwABABMAAQAQAAEAGAABABAAAZgQAAEQAAAAAAAoAFAAeAIgAuAEEAWAChgOyA9QECAQqBKQFJgXoBgAGGgYqBkIGgAaSBvQHFgdQB4YHuAABAAAAGwDPAAYAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEADAAAAAEAAAAAAAIABwCNAAEAAAAAAAMADABFAAEAAAAAAAQADACiAAEAAAAAAAUACwAkAAEAAAAAAAYADABpAAEAAAAAAAoAGgDGAAMAAQQJAAEAGAAMAAMAAQQJAAIADgCUAAMAAQQJAAMAGABRAAMAAQQJAAQAGACuAAMAAQQJAAUAFgAvAAMAAQQJAAYAGAB1AAMAAQQJAAoANADganctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzVmVyc2lvbiAxLjEAVgBlAHIAcwBpAG8AbgAgADEALgAxanctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzanctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzUmVndWxhcgBSAGUAZwB1AGwAYQByanctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzRm9udCBnZW5lcmF0ZWQgYnkgSWNvTW9vbi4ARgBvAG4AdAAgAGcAZQBuAGUAcgBhAHQAZQBkACAAYgB5ACAASQBjAG8ATQBvAG8AbgAuAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
0 ms
s88304954736959
185 ms
s85768613575492
104 ms
s88972550167236
85 ms
washingtonpost.org 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 do not match their roles
ARIA IDs are not unique
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
Links do not have a discernible name
washingtonpost.org 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
Browser errors were logged to the console
Page has valid source maps
washingtonpost.org 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 Washingtonpost.org 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 Washingtonpost.org 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.
washingtonpost.org
Open Graph data is detected on the main page of Washington Post. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: