7.2 sec in total
1 sec
1.9 sec
4.2 sec
Visit washingtonpost.com now to see the best up-to-date Washington Post content for United States and also check out these interesting facts you probably never knew about washingtonpost.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 washingtonpost.comWe analyzed Washingtonpost.com page load time and found that the first response time was 1 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
washingtonpost.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value30.0 s
0/100
25%
Value28.3 s
0/100
10%
Value29,100 ms
0/100
30%
Value0.003
100/100
15%
Value55.5 s
0/100
10%
1039 ms
83 ms
72 ms
1071 ms
96 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 99% of them (77 requests) were addressed to the original Washingtonpost.com, 1% (1 request) were made to S.go-mpulse.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Washingtonpost.com.
Page size can be reduced by 2.0 MB (80%)
2.5 MB
499.7 kB
In fact, the total size of Washingtonpost.com main page is 2.5 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. 85% 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. HTML takes 2.3 MB which makes up the majority of the site volume.
Potential reduce by 2.0 MB
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 2.0 MB or 88% of the original size.
Potential reduce by 0 B
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.
Number of requests can be reduced by 47 (64%)
73
26
The browser has sent 73 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 48 to 1 for JavaScripts and as a result speed up the page load time.
www.washingtonpost.com
1039 ms
main.js
83 ms
tetro.min.js
72 ms
main.js
1071 ms
d21cc98347c3b2e1.css
96 ms
polyfills-c67a75d1b6f99dc8.js
507 ms
9734.179d4001ab7ac238.js
92 ms
4472.567d9ce90adb35fb.js
637 ms
7034.57b1b945e5a151e7.js
508 ms
4276.0173292bcdec38b3.js
632 ms
7783.47edb9caf48d906d.js
637 ms
8065.144350c6886b8328.js
517 ms
7544.267a5403cd70242d.js
636 ms
5803.14a4121e318a0c38.js
1055 ms
5343.a632dba9f5fd20ff.js
1065 ms
2146.d1953986fa6c1d2c.js
1053 ms
2369.ac8743fa9214e141.js
1076 ms
fec483df.c26fdb99934c2bc4.js
1067 ms
29107295.86be9227af37d71e.js
1072 ms
70406f79.ba9e8b815397878b.js
1113 ms
1903.7cc74f7d3e86c586.js
1110 ms
2234.c12a67abf34155a3.js
1073 ms
7437.1bdb6fb3661c7eb4.js
1178 ms
7441.8d21e3d768c30f8d.js
1183 ms
786.a3e0f96abcda6a7a.js
1180 ms
9476.22d77395b6889dc0.js
1124 ms
3969.6bf6b8ec5eb3043c.js
1194 ms
9111.8db1861e2641c7e7.js
1181 ms
5019.088d3bd8e0f79aec.js
1183 ms
3975.683cfdf79a090320.js
1197 ms
6913.d3c52600ad130c6e.js
1187 ms
6588.5c66880fa82f8f92.js
1184 ms
3836.cdf32e00c8b50848.js
1186 ms
webpack-e26263e93174a981.js
1193 ms
framework-5ccac30e2ba32021.js
1192 ms
main-2fdef9cbdcd0ebad.js
1188 ms
_app-625468b13a991209.js
1211 ms
0f1ac474-9321609fe9851653.js
1214 ms
582fd9bb-a3d8660c9d33adda.js
1184 ms
2L2Z6-GDWNL-RH2G3-MVS3W-7M6WF
934 ms
5082-8f6052f9036e0099.js
783 ms
9076-485bf45e92c7dfad.js
774 ms
2921-9304a8a0cd78312e.js
769 ms
4977-3b62b79e0155c316.js
653 ms
5792-5abfdfcaa7b69463.js
646 ms
7395-06ff64ffad11fe2c.js
651 ms
5863-300ded375b587165.js
677 ms
%5Bslug%5D-705694376d63217a.js
296 ms
_buildManifest.js
288 ms
_ssgManifest.js
272 ms
imrs.php
270 ms
imrs.php
265 ms
imrs.php
264 ms
imrs.php
253 ms
imrs.php
253 ms
imrs.php
227 ms
imrs.php
220 ms
imrs.php
221 ms
imrs.php
278 ms
ITC_Franklin-Light.woff2
205 ms
ITC_Franklin-Bold.woff2
387 ms
PostoniWide-Regular.woff2
391 ms
PostoniWide-Bold.woff2
343 ms
imrs.php
344 ms
imrs.php
343 ms
imrs.php
352 ms
imrs.php
349 ms
imrs.php
350 ms
imrs.php
350 ms
imrs.php
348 ms
imrs.php
370 ms
imrs.php
300 ms
imrs.php
280 ms
imrs.php
300 ms
imrs.php
298 ms
imrs.php
293 ms
imrs.php
298 ms
wp_grey.jpg
292 ms
washingtonpost.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-hidden="true"] elements contain focusable descendents
[role] values are not valid
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
washingtonpost.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
washingtonpost.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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.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 Washingtonpost.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.
washingtonpost.com
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: