3.4 sec in total
29 ms
2.5 sec
942 ms
Visit washintonpost.com now to see the best up-to-date Washinton Post content for United States and also check out these interesting facts you probably never knew about washintonpost.com
Breaking news, live coverage, investigations, analysis, video, photos and opinions from The Washington Post. Subscribe for the latest on U.S. and international news, politics, business, technology, cl...
Visit washintonpost.comWe analyzed Washintonpost.com page load time and found that the first response time was 29 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
washintonpost.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value18.4 s
0/100
25%
Value16.4 s
0/100
10%
Value12,260 ms
0/100
30%
Value0.016
100/100
15%
Value32.5 s
0/100
10%
29 ms
7 ms
32 ms
39 ms
36 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Washintonpost.com, 40% (41 requests) were made to Washingtonpost.com and 11% (11 requests) were made to Js.washingtonpost.com. The less responsive or slowest element that took the longest time to load (827 ms) relates to the external source Me-ssl.effectivemeasure.net.
Page size can be reduced by 1.3 MB (46%)
2.8 MB
1.5 MB
In fact, the total size of Washintonpost.com main page is 2.8 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. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 224.7 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 224.7 kB or 81% of the original size.
Potential reduce by 10.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. Washinton Post images are well optimized though.
Potential reduce by 1.0 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.0 MB or 70% of the original size.
Potential reduce by 31.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. Washintonpost.com needs all CSS files to be minified and compressed as it can save up to 31.3 kB or 88% of the original size.
Number of requests can be reduced by 53 (58%)
91
38
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Washinton 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 41 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
washintonpost.com
29 ms
www.washingtonpost.com
7 ms
www.washingtonpost.com
32 ms
39 ms
headerfonts.css
36 ms
ba39e182ae.css
50 ms
style.css
58 ms
f65e4f3f81.js
79 ms
head.min.js
49 ms
9adf0167ec.js
78 ms
16db91d4b3.js
77 ms
e7f066f51e.js
105 ms
hi-pri-render.js
110 ms
loader.min.js
96 ms
06e27c89ae.js
108 ms
WapoVideoEmbed.min.js
110 ms
render.js
108 ms
ab2a22c20d.js
108 ms
7a5b554023.js
198 ms
b5411285f6.js
196 ms
938c258067.css
10 ms
a925dd0217.js
198 ms
main.js
197 ms
8f8c39c9d8.js
194 ms
identity-retargeting.js
196 ms
twp-masthead-415x57.svg
324 ms
images.washingtonpost.com
613 ms
thewashingtonpost-white-2x.png
251 ms
washingtonpost_black_32.png
250 ms
star-md.png
250 ms
crop_9071456026130.jpg
260 ms
crop_90goprace231456179017.jpg
321 ms
crop_90b1456446670.jpg
250 ms
crop_90ff1456196231.jpg
558 ms
crop_90b1456368131.jpg
557 ms
crop_90Botsford_TRUMP_SC_16_02_17_07421455753491.jpg
568 ms
star-blue.jpg
555 ms
star-red.jpg
568 ms
AWSIntel-Logo.png
572 ms
crop_90Sorenson1457476271.jpg
319 ms
20160306_EgyptComedy_4841457367339.jpg
580 ms
ad-sprite.png
567 ms
imrs.php
556 ms
spacer.gif
567 ms
Ax1_module2.jpg
573 ms
cube.png
573 ms
images.washingtonpost.com
568 ms
images.washingtonpost.com
564 ms
images.washingtonpost.com
587 ms
images.washingtonpost.com
574 ms
images.washingtonpost.com
572 ms
images.washingtonpost.com
590 ms
AcoNCCs=
73 ms
p5ccfdkIC4w==
34 ms
Fzt2n2EAAAA=
23 ms
PostoniStandard-Regular.woff
563 ms
fontawesome-webfont.woff
457 ms
diversions-icons.woff
439 ms
moatcontent.js
393 ms
em.js
827 ms
WapoVideoEmbed.main.min.js
171 ms
162 ms
imrs.php
76 ms
amzn_ads.js
508 ms
info
503 ms
wp.css
214 ms
jstag
592 ms
WapoVideoPlayer.min.css
184 ms
streamsense.min.js
295 ms
WDSy9G5kYXAAH0yK4AAAA
5 ms
wprum.min.js
126 ms
test-statistics
244 ms
280 ms
beacon.js
261 ms
chartbeat.js
364 ms
156 ms
iui3
135 ms
wp_secure.min.js
78 ms
pubsub.js
43 ms
bid
226 ms
0fyiQQPWFpt-c
85 ms
0fP2MXxWFpu
80 ms
pubads_impl_82.js
279 ms
underscore-min.js
86 ms
rta.js
266 ms
plugin.js
249 ms
crop_90parasite05D1456414273.jpg
29 ms
frame_2.3.3.html
458 ms
jwplayer.js
111 ms
ping
188 ms
JWPlayerConfig.js
153 ms
save
117 ms
container.html
102 ms
ads
121 ms
save
18 ms
jwPlayerWrapper.min.js
11 ms
streamsense.min.js
6 ms
vid_exclusions.js
7 ms
ads
37 ms
acj
488 ms
p
100 ms
s36372454171068
93 ms
washintonpost.com 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
washintonpost.com 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
washintonpost.com 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 Washintonpost.com 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 Washintonpost.com 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.
washintonpost.com
Open Graph data is detected on the main page of Washinton Post. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: