3.5 sec in total
41 ms
2.5 sec
983 ms
Visit thewashingtonpost.com now to see the best up-to-date The Washington Post content and also check out these interesting facts you probably never knew about thewashingtonpost.com
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 thewashingtonpost.comWe analyzed Thewashingtonpost.com page load time and found that the first response time was 41 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.
thewashingtonpost.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value21.5 s
0/100
25%
Value12.9 s
2/100
10%
Value12,110 ms
0/100
30%
Value0.022
100/100
15%
Value28.8 s
0/100
10%
41 ms
23 ms
56 ms
8 ms
34 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Thewashingtonpost.com, 33% (31 requests) were made to Washingtonpost.com and 14% (13 requests) were made to Img.washingtonpost.com. The less responsive or slowest element that took the longest time to load (878 ms) relates to the external source Img.washingtonpost.com.
Page size can be reduced by 1.3 MB (46%)
2.8 MB
1.5 MB
In fact, the total size of Thewashingtonpost.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. 65% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 230.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 230.7 kB or 81% of the original size.
Potential reduce by 14.9 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. The Washington 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. Thewashingtonpost.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 54 (66%)
82
28
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of The 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 41 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
thewashingtonpost.com
41 ms
www.washingtonpost.com
23 ms
www.washingtonpost.com
56 ms
8 ms
34 ms
headerfonts.css
69 ms
ba39e182ae.css
61 ms
style.css
48 ms
f65e4f3f81.js
79 ms
head.min.js
43 ms
9adf0167ec.js
46 ms
16db91d4b3.js
67 ms
e7f066f51e.js
67 ms
hi-pri-render.js
109 ms
loader.min.js
66 ms
06e27c89ae.js
66 ms
WapoVideoEmbed.min.js
110 ms
render.js
111 ms
ab2a22c20d.js
110 ms
7a5b554023.js
10 ms
b5411285f6.js
397 ms
938c258067.css
10 ms
a925dd0217.js
444 ms
main.js
444 ms
8f8c39c9d8.js
443 ms
identity-retargeting.js
443 ms
twp-masthead-415x57.svg
634 ms
images.washingtonpost.com
748 ms
WapoVideoEmbed.main.min.js
443 ms
441 ms
wprum.min.js
556 ms
test-statistics
712 ms
440 ms
thewashingtonpost-white-2x.png
273 ms
washingtonpost_black_32.png
272 ms
star-md.png
273 ms
imrs.php
457 ms
Obama_Supreme_Court-00dcc.jpg
588 ms
crop_90_A7C73521458133149.jpg
589 ms
imrs.php
752 ms
metroclosure-576x1024.jpg
752 ms
APTOPIX_GOP_2016_Rubio-0d838.jpg
566 ms
CompClintonTrump316.jpg
793 ms
ad-sprite.png
790 ms
spacer.gif
790 ms
Ax1_module2.jpg
751 ms
cube.png
878 ms
imrs.php
792 ms
images.washingtonpost.com
494 ms
images.washingtonpost.com
585 ms
images.washingtonpost.com
588 ms
images.washingtonpost.com
584 ms
images.washingtonpost.com
585 ms
images.washingtonpost.com
586 ms
AcoNCCs=
50 ms
p5ccfdkIC4w==
51 ms
Fzt2n2EAAAA=
50 ms
fontawesome-webfont.woff
398 ms
diversions-icons.woff
660 ms
amzn_ads.js
451 ms
info
570 ms
wp.css
572 ms
jstag
542 ms
621 ms
moatcontent.js
706 ms
beacon.js
601 ms
chartbeat.js
600 ms
em.js
714 ms
WapoVideoPlayer.min.css
144 ms
streamsense.min.js
208 ms
WDSy9G5kYXAAH0yK4AAAA
2 ms
wp_secure.min.js
135 ms
bid
358 ms
pubsub.js
186 ms
pubads_impl_82.js
273 ms
rta.js
355 ms
plugin.js
224 ms
iui3
104 ms
underscore-min.js
96 ms
ping
285 ms
jwplayer.js
95 ms
container.html
245 ms
ads
260 ms
save
198 ms
JWPlayerConfig.js
74 ms
save
36 ms
ads
37 ms
jwPlayerWrapper.min.js
18 ms
streamsense.min.js
11 ms
vid_exclusions.js
9 ms
s56767573240213
85 ms
acj
484 ms
acj
525 ms
thewashingtonpost.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
thewashingtonpost.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
thewashingtonpost.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 Thewashingtonpost.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 Thewashingtonpost.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.
thewashingtonpost.com
Open Graph data is detected on the main page of The Washington Post. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: