3.5 sec in total
221 ms
1.1 sec
2.2 sec
Visit voices.washingtonpost.com now to see the best up-to-date Voices Washington Post content for United States and also check out these interesting facts you probably never knew about voices.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 voices.washingtonpost.comWe analyzed Voices.washingtonpost.com page load time and found that the first response time was 221 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.
voices.washingtonpost.com performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value4.1 s
48/100
25%
Value28.4 s
0/100
10%
Value12,380 ms
0/100
30%
Value0.129
82/100
15%
Value41.0 s
0/100
10%
221 ms
43 ms
43 ms
206 ms
59 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Voices.washingtonpost.com, 1% (1 request) were made to S.go-mpulse.net and 1% (1 request) were made to C.go-mpulse.net. The less responsive or slowest element that took the longest time to load (506 ms) relates to the external source Washingtonpost.com.
Page size can be reduced by 2.1 MB (67%)
3.1 MB
1.0 MB
In fact, the total size of Voices.washingtonpost.com main page is 3.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. 75% 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.0 MB which makes up the majority of the site volume.
Potential reduce by 1.7 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 1.7 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. Voices Washington Post 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 40 (46%)
87
47
The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Voices 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 as a result speed up the page load time.
www.washingtonpost.com
221 ms
main.js
43 ms
tetro.min.js
43 ms
main.js
206 ms
78432c5812c29c3a.css
59 ms
polyfills-78c92fac7aa8fdd8.js
118 ms
7949.f7ea4b76cbf5a497.js
194 ms
7750.22f19e13f82452bd.js
175 ms
3397.3dcdf983ce7f85a5.js
193 ms
4413.f74e21e9a4950cb0.js
193 ms
6583.1283cb2987120b7d.js
192 ms
5953.a3c1c4bf7f2d5189.js
211 ms
1498.4405456a4c429ce6.js
213 ms
3681.d3a6b30d248f1de5.js
212 ms
4065.dc05be607fbf0497.js
213 ms
7069.c5f5cd0e43ccbb75.js
229 ms
6358.0d1cb29777430ca5.js
229 ms
6681.f4f95cb36fa3d811.js
323 ms
9175.029a88e2115a920f.js
316 ms
9485.6d904d5c0373a43c.js
316 ms
5535.19687b3f50824652.js
234 ms
6426.900cbfe5e7f2ac61.js
328 ms
9168.822cfa1642f60916.js
319 ms
6588.cc2d94adaa7a6d0b.js
319 ms
8495.c47ec85ba892a113.js
320 ms
webpack-470d4a6cb31fb024.js
319 ms
framework-6c7157b94eb0c29a.js
323 ms
main-c81352ad4baf570c.js
339 ms
_app-9da73638fd8b9299.js
323 ms
d92eadb3-dc820555586ffd71.js
335 ms
fec483df-c14ea6a95604bad0.js
357 ms
582fd9bb-a48161c2e70db9bb.js
334 ms
b85465e7-d48024ff19d67302.js
374 ms
9561-bf97e200d7f33d0f.js
369 ms
3909-523f94a8e84a6cda.js
429 ms
9189-8a872010f211ab89.js
369 ms
7738-f70512864a0596ec.js
506 ms
7722-a2c255800c46df3c.js
357 ms
2L2Z6-GDWNL-RH2G3-MVS3W-7M6WF
130 ms
1793-175feb201648b7f4.js
292 ms
%5Bslug%5D-b44998773294a65c.js
264 ms
_buildManifest.js
230 ms
_ssgManifest.js
249 ms
imrs.php
247 ms
imrs.php
254 ms
imrs.php
292 ms
imrs.php
291 ms
imrs.php
315 ms
imrs.php
262 ms
imrs.php
268 ms
imrs.php
286 ms
imrs.php
309 ms
config.json
100 ms
imrs.php
322 ms
imrs.php
301 ms
imrs.php
318 ms
imrs.php
250 ms
imrs.php
241 ms
imrs.php
245 ms
imrs.php
289 ms
imrs.php
252 ms
imrs.php
420 ms
imrs.php
351 ms
imrs.php
284 ms
ITC_Franklin-Light.woff2
259 ms
ITC_Franklin-Bold.woff2
274 ms
PostoniWide-Regular.woff2
338 ms
PostoniWide-Bold.woff2
339 ms
imrs.php
397 ms
imrs.php
311 ms
imrs.php
306 ms
imrs.php
305 ms
imrs.php
301 ms
imrs.php
351 ms
imrs.php
339 ms
imrs.php
340 ms
imrs.php
334 ms
imrs.php
310 ms
imrs.php
308 ms
imrs.php
342 ms
imrs.php
296 ms
imrs.php
267 ms
imrs.php
295 ms
imrs.php
316 ms
imrs.php
266 ms
imrs.php
262 ms
imrs.php
250 ms
imrs.php
273 ms
imrs.php
321 ms
imrs.php
251 ms
wp_grey.jpg
281 ms
imrs.php
429 ms
voices.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
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.
voices.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
voices.washingtonpost.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 Voices.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 Voices.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.
voices.washingtonpost.com
Open Graph data is detected on the main page of Voices Washington Post. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: