Tools & Wizards About Us
wshingtonpost.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

wshingtonpost.com

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

Page Load Speed

84.6 sec in total

First Response

36 ms

Resources Loaded

70.8 sec

Page Rendered

13.8 sec

wshingtonpost.com screenshot

About Website

Welcome to wshingtonpost.com homepage info - get ready to check Wshington Post best content right away, or after learning these important things about wshingtonpost.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 wshingtonpost.com

Key Findings

We analyzed Wshingtonpost.com page load time and found that the first response time was 36 ms and then it took 84.6 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 71 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

wshingtonpost.com performance score

0

Network Requests Diagram

wshingtonpost.com

36 ms

www.washingtonpost.com

10183 ms

tetro.min.js

20469 ms

main.js

9076 ms

main.js

8337 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wshingtonpost.com, 84% (90 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.5 sec) relates to the external source Washingtonpost.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (80%)

Content Size

1.8 MB

After Optimization

362.2 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wshingtonpost.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. 45% of websites need less resources to load. HTML takes 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 1.4 MB

  • Original 1.7 MB
  • After minification 1.6 MB
  • After compression 239.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 1.4 MB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 96.3 kB
  • After minification 96.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. Wshington Post images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 30 B

  • Original 26.2 kB
  • After minification 26.2 kB
  • After compression 26.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 18 (62%)

Requests Now

29

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wshingtonpost.com

wshingtonpost.com

36 ms

www.washingtonpost.com

www.washingtonpost.com

10183 ms

tetro.min.js

tetro.min.js

20469 ms

main.js

main.js

9076 ms

main.js

main.js

8337 ms

gtm.js

gtm.js

71 ms

optimize.js

optimize.js

51 ms

scroll.js

scroll.js

32 ms

M

M

158 ms

ef4b35930a189b02c101.css

ef4b35930a189b02c101.css

8072 ms

polyfills-c7210d653eb000f69002.js

polyfills-c7210d653eb000f69002.js

9095 ms

c8f7fe3b0e41be846d5687592cf2018ff6e22687.6cd3d9310fb629cabbdb.js

c8f7fe3b0e41be846d5687592cf2018ff6e22687.6cd3d9310fb629cabbdb.js

10417 ms

38.2036f6fb14c8b706c331.js

38.2036f6fb14c8b706c331.js

16030 ms

49.3be7bfbb3eb8185a9760.js

49.3be7bfbb3eb8185a9760.js

18372 ms

7e6c0f8bb652c3b8f51c7037ba32240ea3cc4901.39844d4eadec2cf4908b.js

7e6c0f8bb652c3b8f51c7037ba32240ea3cc4901.39844d4eadec2cf4908b.js

18034 ms

63.bce811879a3209d7218f.js

63.bce811879a3209d7218f.js

17113 ms

52.a810015a157e41af3b26.js

52.a810015a157e41af3b26.js

20392 ms

47.521c2dca1ef20f96fbe7.js

47.521c2dca1ef20f96fbe7.js

20392 ms

50.27f79e1b9b828fe5109a.js

50.27f79e1b9b828fe5109a.js

20393 ms

53.e4b2ad41fc105abff989.js

53.e4b2ad41fc105abff989.js

20393 ms

65.6e63a8c8ca2cf6a59acb.js

65.6e63a8c8ca2cf6a59acb.js

20395 ms

20.2b9b7e7623c90d9c50b5.js

20.2b9b7e7623c90d9c50b5.js

20395 ms

67.b01ee5676547819a9ef5.js

67.b01ee5676547819a9ef5.js

20395 ms

43.194f0d696c79592678aa.js

43.194f0d696c79592678aa.js

20397 ms

61.90886fd91eeeedf75726.js

61.90886fd91eeeedf75726.js

20398 ms

40.a6514d0e618642d95965.js

40.a6514d0e618642d95965.js

20398 ms

66.60b49083e20115563f80.js

66.60b49083e20115563f80.js

20398 ms

35.312a70c8c608ea68d0cf.js

35.312a70c8c608ea68d0cf.js

20399 ms

59.3735923b5377b0069581.js

59.3735923b5377b0069581.js

20400 ms

60.7870bbda8c7863c0270a.js

60.7870bbda8c7863c0270a.js

20401 ms

48.866c4d447b1fd0be5967.js

48.866c4d447b1fd0be5967.js

20402 ms

webpack-cd6265837d360d55a12e.js

webpack-cd6265837d360d55a12e.js

20401 ms

framework.f951950a693377f87b11.js

framework.f951950a693377f87b11.js

20402 ms

commons.a3258ba176346f73635b.js

commons.a3258ba176346f73635b.js

20402 ms

91f3178531c1c62e4d27b722f834a66197539e8b.04e85bb285e9c96da377.js

91f3178531c1c62e4d27b722f834a66197539e8b.04e85bb285e9c96da377.js

20403 ms

362aa2e1cb5854114eb1f90d6896a23b9297be9e.3e8a9ce40eda24fd6793.js

362aa2e1cb5854114eb1f90d6896a23b9297be9e.3e8a9ce40eda24fd6793.js

20404 ms

main-27d9030410d761f0c411.js

main-27d9030410d761f0c411.js

20404 ms

c6f1a4b7eb075032039786b5aa07362b55d813e1.9551207e01f31242bbe8.js

c6f1a4b7eb075032039786b5aa07362b55d813e1.9551207e01f31242bbe8.js

20405 ms

_app-38ec5ae0064d593a7c16.js

_app-38ec5ae0064d593a7c16.js

20405 ms

cb9b4dcd.e60e14f31581656bfb48.js

cb9b4dcd.e60e14f31581656bfb48.js

20406 ms

0f1ac474.2268d241c43a680cf6c8.js

0f1ac474.2268d241c43a680cf6c8.js

20407 ms

cbbf40fbb8df40f88c3e24ceaea718b4.min.js

cbbf40fbb8df40f88c3e24ceaea718b4.min.js

84 ms

76a316fd32b54ef155c733699e3ba2e815c7ab71.36b0fe74e4880345e41c.js

76a316fd32b54ef155c733699e3ba2e815c7ab71.36b0fe74e4880345e41c.js

20376 ms

web-vitals

web-vitals

67 ms

chartbeat_mab.js

chartbeat_mab.js

26 ms

chartbeat.js

chartbeat.js

3 ms

web-vitals@3.0.2

web-vitals@3.0.2

141 ms

web-vitals.iife.js

web-vitals.iife.js

17 ms

2L2Z6-GDWNL-RH2G3-MVS3W-7M6WF

2L2Z6-GDWNL-RH2G3-MVS3W-7M6WF

235 ms

27ec36ac922dc15281442cb5a55c49518bf1b622.68004c3c0700950783c7.js

27ec36ac922dc15281442cb5a55c49518bf1b622.68004c3c0700950783c7.js

20146 ms

0baf31ec139491fbde7ba9fc2da5f7b7165b3a24.dab39ee719d40241d57c.js

0baf31ec139491fbde7ba9fc2da5f7b7165b3a24.dab39ee719d40241d57c.js

20117 ms

config.json

config.json

145 ms

%5Bslug%5D-5c7b7e0f4962e887a7b3.js

%5Bslug%5D-5c7b7e0f4962e887a7b3.js

20392 ms

mab

mab

70 ms

ping

ping

36 ms

_buildManifest.js

_buildManifest.js

19003 ms

bundle.es5.min.js

bundle.es5.min.js

73 ms

_ssgManifest.js

_ssgManifest.js

19248 ms

ITC_Franklin-Light.woff2

ITC_Franklin-Light.woff2

13481 ms

ITC_Franklin-Bold.woff2

ITC_Franklin-Bold.woff2

20277 ms

PostoniWide-Bold.woff2

PostoniWide-Bold.woff2

18420 ms

PostoniWide-Regular.woff2

PostoniWide-Regular.woff2

20037 ms

imrs.php

imrs.php

17821 ms

imrs.php

imrs.php

18848 ms

imrs.php

imrs.php

17819 ms

imrs.php

imrs.php

19998 ms

imrs.php

imrs.php

19996 ms

imrs.php

imrs.php

19996 ms

imrs.php

imrs.php

19996 ms

imrs.php

imrs.php

19995 ms

imrs.php

imrs.php

19995 ms

imrs.php

imrs.php

19999 ms

imrs.php

imrs.php

19998 ms

imrs.php

imrs.php

19997 ms

imrs.php

imrs.php

19997 ms

imrs.php

imrs.php

19996 ms

imrs.php

imrs.php

19995 ms

imrs.php

imrs.php

19995 ms

imrs.php

imrs.php

19994 ms

imrs.php

imrs.php

19994 ms

imrs.php

imrs.php

19994 ms

imrs.php

imrs.php

19993 ms

imrs.php

imrs.php

19992 ms

imrs.php

imrs.php

19991 ms

imrs.php

imrs.php

19991 ms

imrs.php

imrs.php

19991 ms

imrs.php

imrs.php

19990 ms

imrs.php

imrs.php

19991 ms

imrs.php

imrs.php

19949 ms

imrs.php

imrs.php

20000 ms

imrs.php

imrs.php

19999 ms

imrs.php

imrs.php

19905 ms

imrs.php

imrs.php

20001 ms

imrs.php

imrs.php

19725 ms

imrs.php

imrs.php

20388 ms

imrs.php

imrs.php

19836 ms

imrs.php

imrs.php

18983 ms

imrs.php

imrs.php

20180 ms

imrs.php

imrs.php

19147 ms

imrs.php

imrs.php

19669 ms

imrs.php

imrs.php

19964 ms

ping

ping

6 ms

imrs.php

imrs.php

20000 ms

imrs.php

imrs.php

19999 ms

imrs.php

imrs.php

19999 ms

imrs.php

imrs.php

19999 ms

imrs.php

imrs.php

19999 ms

SEO Factors

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

wshingtonpost.com

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