Tools & Wizards About Us
washigtonpost.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

washigtonpost.com

The Washington Post: Breaking News, World, US, DC News and Analysis

Page Load Speed

5.5 sec in total

First Response

79 ms

Resources Loaded

4.1 sec

Page Rendered

1.3 sec

washigtonpost.com screenshot

About Website

Click here to check amazing Washigton Post content for United States. Otherwise, check out these important facts you probably never knew about washigtonpost.com

Breaking news and analysis on politics, business, world national news, entertainment more. In-depth DC, Virginia, Maryland news coverage including traffic, weather, crime, education, restaurant review...

Visit washigtonpost.com

Key Findings

We analyzed Washigtonpost.com page load time and found that the first response time was 79 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

washigtonpost.com performance score

0

Network Requests Diagram

washigtonpost.com

79 ms

www.washingtonpost.com

9 ms

www.washingtonpost.com

65 ms

7 ms

48 ms

Our browser made a total of 122 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Washigtonpost.com, 29% (35 requests) were made to Washingtonpost.com and 11% (13 requests) were made to Img.washingtonpost.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Me-ssl.effectivemeasure.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (53%)

Content Size

2.8 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Washigtonpost.com main page is 2.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. 80% 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. Javascripts take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 220.2 kB

  • Original 274.4 kB
  • After minification 274.4 kB
  • After compression 54.2 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 220.2 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 12.0 kB

  • Original 652.7 kB
  • After minification 640.7 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. Washigton Post images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 1.0 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 571.4 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 1.0 MB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 233.9 kB

  • Original 279.9 kB
  • After minification 279.6 kB
  • After compression 46.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. Washigtonpost.com needs all CSS files to be minified and compressed as it can save up to 233.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 75 (69%)

Requests Now

109

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Washigton 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 56 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

washigtonpost.com

washigtonpost.com

79 ms

www.washingtonpost.com

www.washingtonpost.com

9 ms

www.washingtonpost.com

www.washingtonpost.com

65 ms

7 ms

48 ms

headerfonts.css

headerfonts.css

83 ms

ba39e182ae.css

ba39e182ae.css

86 ms

style.css

style.css

51 ms

f65e4f3f81.js

f65e4f3f81.js

116 ms

head.min.js

head.min.js

114 ms

9adf0167ec.js

9adf0167ec.js

114 ms

16db91d4b3.js

16db91d4b3.js

114 ms

YTConfig.js

YTConfig.js

206 ms

e7f066f51e.js

e7f066f51e.js

168 ms

hi-pri-render.js

hi-pri-render.js

183 ms

loader.min.js

loader.min.js

169 ms

06e27c89ae.js

06e27c89ae.js

168 ms

WapoVideoEmbed.min.js

WapoVideoEmbed.min.js

363 ms

render.js

render.js

180 ms

ab2a22c20d.js

ab2a22c20d.js

181 ms

7a5b554023.js

7a5b554023.js

33 ms

b5411285f6.js

b5411285f6.js

27 ms

938c258067.css

938c258067.css

27 ms

a925dd0217.js

a925dd0217.js

26 ms

main.js

main.js

26 ms

8f8c39c9d8.js

8f8c39c9d8.js

26 ms

identity-retargeting.js

identity-retargeting.js

198 ms

twp-masthead-415x57.svg

twp-masthead-415x57.svg

368 ms

images.washingtonpost.com

images.washingtonpost.com

419 ms

thewashingtonpost-white-2x.png

thewashingtonpost-white-2x.png

130 ms

washingtonpost_black_32.png

washingtonpost_black_32.png

133 ms

star-md.png

star-md.png

133 ms

AWSIntel-Logo.png

AWSIntel-Logo.png

133 ms

Obama_Supreme_Court-0289e.jpg

Obama_Supreme_Court-0289e.jpg

647 ms

254466274_0-5.jpg

254466274_0-5.jpg

648 ms

crop_358516677394.jpg

crop_358516677394.jpg

648 ms

imrs.php

imrs.php

645 ms

imrs.php

imrs.php

643 ms

spacer.gif

spacer.gif

637 ms

Ax1_module2.jpg

Ax1_module2.jpg

650 ms

cube.png

cube.png

647 ms

images.washingtonpost.com

images.washingtonpost.com

633 ms

images.washingtonpost.com

images.washingtonpost.com

642 ms

images.washingtonpost.com

images.washingtonpost.com

641 ms

images.washingtonpost.com

images.washingtonpost.com

637 ms

images.washingtonpost.com

images.washingtonpost.com

640 ms

images.washingtonpost.com

images.washingtonpost.com

639 ms

images.washingtonpost.com

images.washingtonpost.com

642 ms

images.washingtonpost.com

images.washingtonpost.com

645 ms

AcoNCCs=

AcoNCCs=

10 ms

p5ccfdkIC4w==

p5ccfdkIC4w==

7 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

485 ms

Fzt2n2EAAAA=

Fzt2n2EAAAA=

8 ms

imrs.php

imrs.php

422 ms

ad-sprite.png

ad-sprite.png

341 ms

diversions-icons.woff

diversions-icons.woff

405 ms

moatcontent.js

moatcontent.js

710 ms

em.js

em.js

1215 ms

WapoVideoEmbed.main.min.js

WapoVideoEmbed.main.min.js

258 ms

245 ms

iframe_api

iframe_api

587 ms

imrs.php

imrs.php

171 ms

amzn_ads.js

amzn_ads.js

804 ms

info

info

912 ms

wp.css

wp.css

425 ms

jstag

jstag

1002 ms

WapoVideoPlayer.min.css

WapoVideoPlayer.min.css

478 ms

streamsense.min.js

streamsense.min.js

622 ms

WDSy9G5kYXAAH0yK4AAAA

WDSy9G5kYXAAH0yK4AAAA

98 ms

wp_secure.min.js

wp_secure.min.js

387 ms

www-widgetapi.js

www-widgetapi.js

292 ms

bid

bid

290 ms

iui3

iui3

212 ms

pubads_impl_82.js

pubads_impl_82.js

127 ms

pubsub.js

pubsub.js

54 ms

rta.js

rta.js

227 ms

QatBuaCoGbI

QatBuaCoGbI

95 ms

underscore-min.js

underscore-min.js

82 ms

sync

sync

300 ms

i.js

i.js

518 ms

sync

sync

308 ms

container.html

container.html

511 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

253 ms

www-embed-player.js

www-embed-player.js

334 ms

base.js

base.js

632 ms

ads

ads

805 ms

jwplayer.js

jwplayer.js

314 ms

pixel.gif

pixel.gif

869 ms

wprum.min.js

wprum.min.js

221 ms

test-statistics

test-statistics

923 ms

833 ms

beacon.js

beacon.js

743 ms

chartbeat.js

chartbeat.js

830 ms

plugin.js

plugin.js

753 ms

107 ms

JWPlayerConfig.js

JWPlayerConfig.js

439 ms

js

js

593 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

389 ms

ad_status.js

ad_status.js

413 ms

ads

ads

207 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

308 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

377 ms

osd.js

osd.js

367 ms

jwPlayerWrapper.min.js

jwPlayerWrapper.min.js

197 ms

pixel.gif

pixel.gif

195 ms

0fG3f1M0Gpq

0fG3f1M0Gpq

143 ms

js

js

204 ms

ping

ping

178 ms

pixel.gif

pixel.gif

52 ms

streamsense.min.js

streamsense.min.js

42 ms

image0041458162130.jpg

image0041458162130.jpg

42 ms

render.js

render.js

40 ms

spacer.gif

spacer.gif

36 ms

acj

acj

95 ms

saveLatency

saveLatency

134 ms

pixel.gif

pixel.gif

61 ms

vid_exclusions.js

vid_exclusions.js

59 ms

ads

ads

251 ms

save

save

45 ms

save

save

12 ms

s6931665273383

s6931665273383

111 ms

saveLatency

saveLatency

73 ms

SEO Factors

washigtonpost.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Washigtonpost.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 Washigtonpost.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.

Social Sharing Optimization

washigtonpost.com

Open Graph data is detected on the main page of Washigton Post. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: