73.5 sec in total
13 ms
67.7 sec
5.8 sec
Click here to check amazing Mobile Washington Post content for United States. Otherwise, check out these important facts you probably never knew about mobile.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 mobile.washingtonpost.comWe analyzed Mobile.washingtonpost.com page load time and found that the first response time was 13 ms and then it took 73.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 55 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
mobile.washingtonpost.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value15.7 s
0/100
25%
Value11.4 s
5/100
10%
Value12,200 ms
0/100
30%
Value0.014
100/100
15%
Value32.2 s
0/100
10%
13 ms
9280 ms
20438 ms
8132 ms
9305 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 Mobile.washingtonpost.com, 82% (76 requests) were made to Washingtonpost.com and 3% (3 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Washingtonpost.com.
Page size can be reduced by 1.4 MB (81%)
1.8 MB
343.6 kB
In fact, the total size of Mobile.washingtonpost.com main page is 1.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. 40% of websites need less resources to load. HTML takes 1.7 MB which makes up the majority of the site volume.
Potential reduce by 1.4 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.4 MB or 86% 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. Mobile Washington Post images are well optimized though.
Potential reduce by 30 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 20 (69%)
29
9
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile 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 21 to 1 for JavaScripts and as a result speed up the page load time.
mobile.washingtonpost.com
13 ms
www.washingtonpost.com
9280 ms
tetro.min.js
20438 ms
main.js
8132 ms
main.js
9305 ms
gtm.js
302 ms
optimize.js
782 ms
scroll.js
713 ms
M
923 ms
ef4b35930a189b02c101.css
10419 ms
polyfills-c7210d653eb000f69002.js
10218 ms
c8f7fe3b0e41be846d5687592cf2018ff6e22687.1e764fb19edfd53ef3dd.js
9708 ms
40.3c2c7da0e4363c0e2606.js
18007 ms
50.d3f5ca3c3c022368de0f.js
18543 ms
7e6c0f8bb652c3b8f51c7037ba32240ea3cc4901.39844d4eadec2cf4908b.js
18731 ms
63.bce811879a3209d7218f.js
19262 ms
53.d23ddc51c09f1b25d05a.js
18433 ms
48.4217b2a9042a69f55bbd.js
20288 ms
51.0f0fded269ff0b3e205d.js
20288 ms
69.d718f440a0a9e70689b0.js
20288 ms
42.f533ed977bedbe623e5b.js
20272 ms
67.b01ee5676547819a9ef5.js
20273 ms
32.2873e8b6891a84a10c4a.js
20272 ms
44.c7894ca7bb5f1ce61dc7.js
20272 ms
39.277d36cac59918d7b838.js
20272 ms
66.60b49083e20115563f80.js
20273 ms
65.6e63a8c8ca2cf6a59acb.js
20272 ms
20.2b9b7e7623c90d9c50b5.js
20272 ms
35.312a70c8c608ea68d0cf.js
20273 ms
60.f0d6b08b5937e641a96e.js
20272 ms
61.267c2907fbd159bfc318.js
20273 ms
49.0721e5a8ec6d7e039970.js
20273 ms
webpack-765c436675090697845f.js
20272 ms
framework.f951950a693377f87b11.js
20273 ms
commons.16b24ac742196e8d8eca.js
20272 ms
91f3178531c1c62e4d27b722f834a66197539e8b.04e85bb285e9c96da377.js
20273 ms
362aa2e1cb5854114eb1f90d6896a23b9297be9e.3e8a9ce40eda24fd6793.js
20273 ms
main-27d9030410d761f0c411.js
20272 ms
c6f1a4b7eb075032039786b5aa07362b55d813e1.9551207e01f31242bbe8.js
20273 ms
_app-38ec5ae0064d593a7c16.js
20273 ms
cb9b4dcd.e60e14f31581656bfb48.js
20273 ms
cbbf40fbb8df40f88c3e24ceaea718b4.min.js
736 ms
0f1ac474.2268d241c43a680cf6c8.js
20258 ms
web-vitals
319 ms
chartbeat_mab.js
243 ms
web-vitals@3.0.2
20 ms
chartbeat.js
15 ms
web-vitals.iife.js
20 ms
76a316fd32b54ef155c733699e3ba2e815c7ab71.e608a85da53d7d505bb8.js
20303 ms
27ec36ac922dc15281442cb5a55c49518bf1b622.a5879bf7f2e953932033.js
20114 ms
0baf31ec139491fbde7ba9fc2da5f7b7165b3a24.dab39ee719d40241d57c.js
19582 ms
%5Bslug%5D-5c7b7e0f4962e887a7b3.js
19110 ms
2L2Z6-GDWNL-RH2G3-MVS3W-7M6WF
259 ms
_buildManifest.js
18765 ms
bundle.es5.min.js
24 ms
mab
26 ms
ping
23 ms
config.json
34 ms
_ssgManifest.js
11321 ms
ITC_Franklin-Light.woff2
18919 ms
ITC_Franklin-Bold.woff2
18786 ms
PostoniWide-Bold.woff2
18624 ms
PostoniWide-Regular.woff2
18091 ms
imrs.php
18076 ms
t_9a19ea2233a64fc9a68926ced72397f8_name_Sequence_07_00_28_59_22_Still022.jpg
18085 ms
imrs.php
19999 ms
imrs.php
19998 ms
imrs.php
19998 ms
imrs.php
19999 ms
imrs.php
19998 ms
imrs.php
19998 ms
imrs.php
19997 ms
imrs.php
19997 ms
imrs.php
19997 ms
imrs.php
19997 ms
imrs.php
19997 ms
imrs.php
19996 ms
imrs.php
19996 ms
imrs.php
19996 ms
imrs.php
19995 ms
imrs.php
19996 ms
imrs.php
19995 ms
imrs.php
19995 ms
imrs.php
19995 ms
imrs.php
19994 ms
imrs.php
19994 ms
imrs.php
19993 ms
imrs.php
19993 ms
imrs.php
19993 ms
imrs.php
19998 ms
imrs.php
20001 ms
imrs.php
19062 ms
ping
2 ms
mobile.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-*] 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
mobile.washingtonpost.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
mobile.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 Mobile.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 Mobile.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.
mobile.washingtonpost.com
Open Graph data is detected on the main page of Mobile Washington Post. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: