Analyze

washingtonpost.org: Washington Post: Breaking News, World, US, DC News & Analysis - The Washington Post

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...

Page load speed analysis

  • 59/100

    Normal result
  • 7

    Successful tests
  • 1

    Failed test
  • First response

    11 ms

  • Resources loaded

    2.8 sec

  • Page rendered

    988 ms

  • Total page load time

    3.8 sec

Click here to check amazing Washington Post content. Otherwise, check out these important facts you probably never knew about washingtonpost.org

We analyzed Washingtonpost.org page load time and found that the first response time was 11 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Page optimization

  • HTML 310.9 kB
    Images 1.8 MB
    Javascripts 1.7 MB
    CSS 279.9 kB

    In fact, the total size of Washingtonpost.org main page is 4.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. 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. Images take 1.8 MB which makes up the majority of the site volume.

    • Original 310.9 kB
    • After minification 310.9 kB
    • After compression 59.4 kB

    HTML optimization

    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 251.5 kB or 81% of the original size.

    • Original 1.8 MB
    • After optimization 1.8 MB

    Image optimization

    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. Washington Post images are well optimized though.

    • Original 1.7 MB
    • After minification 1.7 MB
    • After compression 513.0 kB

    JavaScript optimization

    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.2 MB or 70% of the original size.

    • Original 279.9 kB
    • After minification 279.6 kB
    • After compression 46.0 kB

    CSS optimization

    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. Washingtonpost.org needs all CSS files to be minified and compressed as it can save up to 233.9 kB or 84% of the original size.

Network requests diagram

  • washingtonpost.org
  • www.washingtonpost.com
  • www.washingtonpost.com
  • headerfonts.css
  • ba39e182ae.css
  • style.css
  • f65e4f3f81.js
  • head.min.js
  • 9adf0167ec.js
  • 16db91d4b3.js
  • YTConfig.js
  • e7f066f51e.js
  • hi-pri-render.js
  • loader.min.js
  • 06e27c89ae.js
  • WapoVideoEmbed.min.js
  • render.js
  • ab2a22c20d.js
  • 7a5b554023.js
  • b5411285f6.js
  • 938c258067.css
  • a925dd0217.js
  • main.js
  • 8f8c39c9d8.js
  • identity-retargeting.js
  • twp-masthead-415x57.svg
  • images.washingtonpost.com
  • thewashingtonpost-white-2x.png
  • washingtonpost_black_32.png
  • star-blue.jpg
  • star-red.jpg
  • crop_90Botsford_TRUMP_16_02_07_04781454875511.jpg
  • L4A-clinton-cheer-3x2.jpg
  • crop_9027071455129974.jpg
  • crop_90Botsford_CRUZ_16_02_05_04251454727071.jpg
  • crop_90031457647631.jpg
  • crop_90bs241454706550.jpg
  • AWSIntel-Logo.png
  • imrs.php
  • imrs.php
  • crop_90White_Sox_LaRoche_Son_Baseball-0061b.jpg
  • Aleppo-pair21458333251.jpg
  • imrs.php
  • imrs.php
  • imrs.php
  • imrs.php
  • spacer.gif
  • Ax1_module2.jpg
  • cube.png
  • images.washingtonpost.com
  • images.washingtonpost.com
  • images.washingtonpost.com
  • images.washingtonpost.com
  • images.washingtonpost.com
  • images.washingtonpost.com
  • images.washingtonpost.com
  • AcoNCCs=
  • WapoVideoEmbed.main.min.js
  • YTConfig.js
  • iframe_api
  • ad-sprite.png
  • imrs.php
  • p5ccfdkIC4w==
  • Fzt2n2EAAAA=
  • PostoniStandard-Regular.woff
  • fontawesome-webfont.woff
  • diversions-icons.woff
  • amzn_ads.js
  • info
  • wp.css
  • jstag
  • moatcontent.js
  • em.js
  • WapoVideoPlayer.min.css
  • streamsense.min.js
  • 92d280a2-7d90-11e0-b6cc-e4e4a8a38cf0
  • WDSy9G5kYXAAH0yK4AAAA
  • www-widgetapi.js
  • pubsub.js
  • iui3
  • bid
  • wp_secure.min.js
  • underscore-min.js
  • wprum.min.js
  • beacon.js
  • chartbeat.js
  • LRXeR4KYJ9A
  • pubads_impl_82.js
  • jwplayer.js
  • rta.js
  • plugin.js
  • frame_2.3.3.html
  • JWPlayerConfig.js
  • www-embed-player-vflfNyN_r.css
  • www-embed-player.js
  • base.js
  • jwPlayerWrapper.min.js
  • container.html
  • ads
  • ping
  • streamsense.min.js
  • vid_exclusions.js
  • fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
  • ad_status.js
  • CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
  • RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
  • save
  • ads
  • acj
  • trending-videos-overall.json
  • polyfills.promise.js
  • p
  • bekle.css
  • save
  • index.html
  • save
  • index.html
  • loading_wp_white_100.gif
  • wAAABgAAAAAABcAAAQAAAAAAAAAAAAAAAAAAABsEAAAAAAAAAAAAAAACAAAABgAAYAQAAEAFAABABQAAQAYAAEAGAABABAAA4ASAAEAEAABABgAAQAYAAD0D4ABDBIAARgQAAIAEAACABIAASgOAAEMEwABABMAAQAQAAEAGAABABAAAZgQAAEQAAAAAAAoAFAAeAIgAuAEEAWAChgOyA9QECAQqBKQFJgXoBgAGGgYqBkIGgAaSBvQHFgdQB4YHuAABAAAAGwDPAAYAAAAAAAIAAAAAAAAAAAAAAAAAAAAAAAAADgCuAAEAAAAAAAEADAAAAAEAAAAAAAIABwCNAAEAAAAAAAMADABFAAEAAAAAAAQADACiAAEAAAAAAAUACwAkAAEAAAAAAAYADABpAAEAAAAAAAoAGgDGAAMAAQQJAAEAGAAMAAMAAQQJAAIADgCUAAMAAQQJAAMAGABRAAMAAQQJAAQAGACuAAMAAQQJAAUAFgAvAAMAAQQJAAYAGAB1AAMAAQQJAAoANADganctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzVmVyc2lvbiAxLjEAVgBlAHIAcwBpAG8AbgAgADEALgAxanctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzanctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzUmVndWxhcgBSAGUAZwB1AGwAYQByanctc2l4LWljb25zAGoAdwAtAHMAaQB4AC0AaQBjAG8AbgBzRm9udCBnZW5lcmF0ZWQgYnkgSWNvTW9vbi4ARgBvAG4AdAAgAGcAZQBuAGUAcgBhAHQAZQBkACAAYgB5ACAASQBjAG8ATQBvAG8AbgAuAAAAAwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA==
  • s88304954736959
  • s85768613575492
  • s88972550167236

Our browser made a total of 127 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Washingtonpost.org, 31% (40 requests) were made to Washingtonpost.com and 11% (14 requests) were made to Js.washingtonpost.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Plugin.mediavoice.com.

Additional info on washingtonpost.org

Requests

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

50

Javascripts

39

Images

8

CSS

15

AJAX

112

All

Possible request optimization

1

Javascripts

28

Images

1

CSS

15

AJAX

67

Optimized

45

All

Normal result

Redirects

As for redirects, our browser reached this domain in four steps. The first redirect led to http://www.washingtonpost.com, then it was forwarded to https://www.washingtonpost.com/, and afterwards it was sent to http://www.washingtonpost.com/regional/ and a few other URLs (see the full list below) before we finally managed to reach this website. We strongly recommend that the redirects should be reduced, as the more redirects a site has, the slower it loads.

IP address

Washingtonpost.org uses IP address which is currently shared with 4 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Poor result

IP Trace

washingtonpost.org

thewashingtonpost.com

washpost.com

washpostco.com

washingtonpostmedia.com

198.72.14.16

DNS records

Type Host Target/ip TTL Other
A

washingtonpost.org

198.72.14.16 14388
NS

washingtonpost.org

dns1.cscdns.net 14399
NS

washingtonpost.org

dns2.cscdns.net 14399
SOA

washingtonpost.org

14399 Mname: dns1.cscdns.net
Rname: hostmaster.cscdns.net
Serial: 2013030104
Refresh: 28800
Retry: 7200
Expire: 604800
Minimum-ttl: 14400

Language and encoding

Good result

Language

EN en language flag

Detected

EN en language flag

Claimed

Encoding

UTF-8

Claimed

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

HTTPS certificate

SSL Certificate

Washingtonpost.org has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

The server of Washingtonpost.org is located in United States, but, unfortunately, we cannot identify the countries where the visitors come from and thus it’s impossible to define if the distance can potentially affect the page load time.

Good result

Good result

Social Sharing Optimization

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

washingtonpost.org

Share this report in social media

Analyze another website

Analyze