3.4 sec in total
25 ms
1.1 sec
2.3 sec
Visit wapo.com now to see the best up-to-date Wapo content for United States and also check out these interesting facts you probably never knew about wapo.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 wapo.comWe analyzed Wapo.com page load time and found that the first response time was 25 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
wapo.com performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value4.7 s
32/100
25%
Value34.2 s
0/100
10%
Value10,190 ms
0/100
30%
Value0.129
82/100
15%
Value38.6 s
0/100
10%
25 ms
328 ms
47 ms
124 ms
337 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wapo.com, 97% (89 requests) were made to Washingtonpost.com and 1% (1 request) were made to S.go-mpulse.net. The less responsive or slowest element that took the longest time to load (467 ms) relates to the external source Washingtonpost.com.
Page size can be reduced by 2.3 MB (67%)
3.4 MB
1.1 MB
In fact, the total size of Wapo.com main page is 3.4 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. Only a small number of websites need less resources to load. 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 87% 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. Wapo images are well optimized though.
Potential reduce by 340.2 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 340.2 kB or 65% of the original size.
Number of requests can be reduced by 41 (48%)
86
45
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wapo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and as a result speed up the page load time.
wapo.com
25 ms
www.washingtonpost.com
328 ms
main.js
47 ms
tetro.min.js
124 ms
main.js
337 ms
78432c5812c29c3a.css
41 ms
polyfills-78c92fac7aa8fdd8.js
253 ms
7949.f7ea4b76cbf5a497.js
252 ms
7750.22f19e13f82452bd.js
117 ms
3397.3dcdf983ce7f85a5.js
251 ms
4413.f74e21e9a4950cb0.js
251 ms
6583.1283cb2987120b7d.js
330 ms
5953.a3c1c4bf7f2d5189.js
332 ms
1498.4405456a4c429ce6.js
332 ms
3681.d3a6b30d248f1de5.js
334 ms
4065.dc05be607fbf0497.js
329 ms
7069.c5f5cd0e43ccbb75.js
333 ms
6358.0d1cb29777430ca5.js
329 ms
6681.f4f95cb36fa3d811.js
331 ms
9175.029a88e2115a920f.js
370 ms
9485.6d904d5c0373a43c.js
334 ms
5535.19687b3f50824652.js
334 ms
6426.900cbfe5e7f2ac61.js
334 ms
9168.822cfa1642f60916.js
335 ms
6588.cc2d94adaa7a6d0b.js
373 ms
2953.01f4a0fb2739a373.js
368 ms
8495.c47ec85ba892a113.js
368 ms
webpack-470d4a6cb31fb024.js
370 ms
framework-6c7157b94eb0c29a.js
371 ms
main-c81352ad4baf570c.js
371 ms
_app-9da73638fd8b9299.js
401 ms
d92eadb3-dc820555586ffd71.js
384 ms
fec483df-c14ea6a95604bad0.js
402 ms
582fd9bb-a48161c2e70db9bb.js
436 ms
b85465e7-d48024ff19d67302.js
409 ms
9561-bf97e200d7f33d0f.js
409 ms
3909-523f94a8e84a6cda.js
411 ms
9189-8a872010f211ab89.js
377 ms
2L2Z6-GDWNL-RH2G3-MVS3W-7M6WF
279 ms
7738-f70512864a0596ec.js
301 ms
7722-a2c255800c46df3c.js
317 ms
1793-175feb201648b7f4.js
190 ms
%5Bslug%5D-b44998773294a65c.js
189 ms
_buildManifest.js
181 ms
_ssgManifest.js
209 ms
imrs.php
219 ms
imrs.php
179 ms
imrs.php
158 ms
imrs.php
139 ms
imrs.php
148 ms
imrs.php
140 ms
imrs.php
174 ms
imrs.php
165 ms
imrs.php
311 ms
imrs.php
199 ms
imrs.php
381 ms
imrs.php
213 ms
imrs.php
244 ms
imrs.php
242 ms
ITC_Franklin-Light.woff2
199 ms
ITC_Franklin-Bold.woff2
275 ms
PostoniWide-Regular.woff2
208 ms
PostoniWide-Bold.woff2
271 ms
imrs.php
369 ms
imrs.php
270 ms
imrs.php
330 ms
imrs.php
259 ms
config.json
57 ms
imrs.php
340 ms
imrs.php
324 ms
imrs.php
304 ms
imrs.php
304 ms
imrs.php
304 ms
imrs.php
424 ms
imrs.php
334 ms
imrs.php
339 ms
imrs.php
352 ms
imrs.php
344 ms
imrs.php
344 ms
imrs.php
381 ms
imrs.php
347 ms
imrs.php
337 ms
imrs.php
335 ms
imrs.php
342 ms
imrs.php
348 ms
imrs.php
361 ms
imrs.php
467 ms
imrs.php
365 ms
imrs.php
414 ms
imrs.php
384 ms
wp_grey.jpg
367 ms
imrs.php
332 ms
wapo.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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
wapo.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
wapo.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 Wapo.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 Wapo.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.
wapo.com
Open Graph data is detected on the main page of Wapo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: