3.2 sec in total
97 ms
2.9 sec
200 ms
Click here to check amazing Stats Washington Post content for United States. Otherwise, check out these important facts you probably never knew about stats.washingtonpost.com
The Washington Post Sports section provides sports news, video, scores, analysis and updates about high school, college, and pro sports teams, including the Capitals, Nationals, Washington Football Te...
Visit stats.washingtonpost.comWe analyzed Stats.washingtonpost.com page load time and found that the first response time was 97 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
stats.washingtonpost.com performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value7.3 s
4/100
25%
Value8.1 s
20/100
10%
Value2,720 ms
3/100
30%
Value0.197
63/100
15%
Value21.2 s
1/100
10%
97 ms
64 ms
92 ms
9 ms
6 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Stats.washingtonpost.com, 17% (19 requests) were made to Js.washingtonpost.com and 6% (7 requests) were made to Hosted.stats.com. The less responsive or slowest element that took the longest time to load (426 ms) relates to the external source Cdn3.doubleverify.com.
Page size can be reduced by 1.1 MB (65%)
1.7 MB
603.9 kB
In fact, the total size of Stats.washingtonpost.com main page is 1.7 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 112.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 112.7 kB or 83% of the original size.
Potential reduce by 2.3 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. Stats Washington Post images are well optimized though.
Potential reduce by 933.0 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 933.0 kB or 69% of the original size.
Potential reduce by 74.0 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. Stats.washingtonpost.com needs all CSS files to be minified and compressed as it can save up to 74.0 kB or 82% of the original size.
Number of requests can be reduced by 84 (79%)
106
22
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stats 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 51 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
stats.washingtonpost.com
97 ms
current_week.asp
64 ms
scoreboard.asp
92 ms
marketwatch.css
9 ms
stats.css
6 ms
twp-internal.js
8 ms
generic_ad.js
38 ms
wp.js
36 ms
shsdefault.css
47 ms
shs.css
33 ms
pfbdefault.css
48 ms
pfb.css
36 ms
urchin.js
41 ms
marketwatch.js
31 ms
stats.css
51 ms
combo
20 ms
combo
253 ms
combo
228 ms
combo
229 ms
combo
218 ms
combo
228 ms
combo
249 ms
combo
224 ms
main.js
236 ms
moatcontent.js
113 ms
em.js
164 ms
amzn_ads.js
19 ms
wp_config.js
17 ms
tiffanyTiles.js
16 ms
rta.js
23 ms
krux.js
8 ms
bid
119 ms
controltag
37 ms
controltag.js.3269b976cac0388f80dbfdb09d96a4e7
52 ms
dbg52463.moatads.com
47 ms
v2_02_01.gif
15 ms
stats;wp_pvid=4871246046387-1456835271221;tile=1;ord=699359877966344300
351 ms
frame_2.3.3.html
155 ms
p
84 ms
aclk
73 ms
lidar.js
32 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
21 ms
moatad.js
71 ms
index.html
80 ms
pixel.gif
88 ms
nfldraftdefault.css
26 ms
moatad.js
58 ms
imp
100 ms
DcmEnabler_01_102.js
29 ms
gradient_tile_x.gif
36 ms
carolina_panthers.png
36 ms
denver_broncos.png
75 ms
__utm.gif
60 ms
stats;wp_pvid=4871246046387-1456835271221;tile=2;ord=699359877966344300
70 ms
pixel.gif
7 ms
pixel.gif
5 ms
cta.png
4 ms
t3.png
16 ms
t2.png
17 ms
t1.png
18 ms
logo.png
16 ms
html_inpage_rendering_lib_200_121.js
14 ms
stats;wp_pvid=4871246046387-1456835271221;tile=3;ord=699359877966344300
68 ms
backup300x600rich.jpg
18 ms
visit.jpg
94 ms
dvtp_src.js
89 ms
dc_oe=ChMIs6uNp76fywIVDUkMCh3JVg58EAAYACDqhIIh;met=1;×tamp=1456835272143;eid1=9;ecn1=1;etm1=0;
62 ms
combo
40 ms
scoreboard.asp
68 ms
beacon.js
43 ms
chartbeat.js
65 ms
backup728x90.jpg
26 ms
dvtp_src.js
48 ms
visit.jpg
172 ms
dc_oe=ChMIhbmRp76fywIVxQkMCh1cQgNyEAAYACCLhv4g;met=1;×tamp=1456835272179;eid1=9;ecn1=1;etm1=0;
23 ms
combo
10 ms
combo
141 ms
dvtp_src_internal25.js
141 ms
ping
121 ms
subscribePromo.js
86 ms
combo
286 ms
t2tv7.html
426 ms
visit.js
151 ms
visit.js
73 ms
digital-subscription-610x66.png
74 ms
proxy
28 ms
proxy
27 ms
save
156 ms
avs5634.js
45 ms
event.gif
144 ms
avs578.js
104 ms
spacer.gif
117 ms
MastheadSprite4.png
44 ms
wp-67x56.png
57 ms
ad-sprite.png
55 ms
event.jpg
55 ms
postonititling-regular-webfont.ttf
36 ms
icons-sprite.png
8 ms
icons-sprite.png
16 ms
event.gif
19 ms
event.gif
18 ms
event.jpg
9 ms
pixel.gif
4 ms
s28394200289621
83 ms
pixel.gif
3 ms
wpPlusPixels.js
21 ms
ads.css
18 ms
optout_check
19 ms
pixel.gif
7 ms
js
35 ms
js
119 ms
i.js
34 ms
stats.washingtonpost.com accessibility score
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
stats.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
stats.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
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stats.washingtonpost.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Stats.washingtonpost.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
stats.washingtonpost.com
Open Graph description is not detected on the main page of Stats Washington Post. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: