Tools & Wizards About Us
wpost.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

wpost.com

Washington Post Podcasts

Page Load Speed

12 sec in total

First Response

339 ms

Resources Loaded

3.6 sec

Page Rendered

8.1 sec

wpost.com screenshot

About Website

Welcome to wpost.com homepage info - get ready to check W Post best content right away, or after learning these important things about wpost.com

Audio news, discussions and documentaries

Visit wpost.com

Key Findings

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

Performance Metrics

wpost.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value21.2 s

0/100

25%

SI (Speed Index)

Value20.5 s

0/100

10%

TBT (Total Blocking Time)

Value19,260 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.13

81/100

15%

TTI (Time to Interactive)

Value41.3 s

0/100

10%

Network Requests Diagram

www.washingtonpost.com

339 ms

tetro.min.js

247 ms

main.js

272 ms

main.js

289 ms

gtm.js

753 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Wpost.com, 3% (3 requests) were made to Unpkg.com and 2% (2 requests) were made to Static.chartbeat.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Washingtonpost.com.

Page Optimization Overview & Recommendations

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

Content Size

2.1 MB

After Optimization

659.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Wpost.com main page is 2.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. HTML takes 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 1.4 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 231.3 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 86% of the original size.

Image Optimization

-0%

Potential reduce by 13 B

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

JavaScript Optimization

-0%

Potential reduce by 32 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 48 (58%)

Requests Now

83

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.washingtonpost.com

www.washingtonpost.com

339 ms

tetro.min.js

tetro.min.js

247 ms

main.js

main.js

272 ms

main.js

main.js

289 ms

gtm.js

gtm.js

753 ms

optimize.js

optimize.js

1581 ms

scroll.js

scroll.js

299 ms

M

M

1555 ms

ef4b35930a189b02c101.css

ef4b35930a189b02c101.css

294 ms

polyfills-c7210d653eb000f69002.js

polyfills-c7210d653eb000f69002.js

562 ms

c8f7fe3b0e41be846d5687592cf2018ff6e22687.1e764fb19edfd53ef3dd.js

c8f7fe3b0e41be846d5687592cf2018ff6e22687.1e764fb19edfd53ef3dd.js

1428 ms

40.3c2c7da0e4363c0e2606.js

40.3c2c7da0e4363c0e2606.js

169 ms

50.d3f5ca3c3c022368de0f.js

50.d3f5ca3c3c022368de0f.js

642 ms

7e6c0f8bb652c3b8f51c7037ba32240ea3cc4901.39844d4eadec2cf4908b.js

7e6c0f8bb652c3b8f51c7037ba32240ea3cc4901.39844d4eadec2cf4908b.js

1424 ms

63.bce811879a3209d7218f.js

63.bce811879a3209d7218f.js

1425 ms

53.d23ddc51c09f1b25d05a.js

53.d23ddc51c09f1b25d05a.js

1424 ms

48.4217b2a9042a69f55bbd.js

48.4217b2a9042a69f55bbd.js

1423 ms

51.0f0fded269ff0b3e205d.js

51.0f0fded269ff0b3e205d.js

1659 ms

54.b13f42f4ea5316a51cb3.js

54.b13f42f4ea5316a51cb3.js

1660 ms

66.60b49083e20115563f80.js

66.60b49083e20115563f80.js

1428 ms

42.f533ed977bedbe623e5b.js

42.f533ed977bedbe623e5b.js

1652 ms

67.b01ee5676547819a9ef5.js

67.b01ee5676547819a9ef5.js

1654 ms

44.c7894ca7bb5f1ce61dc7.js

44.c7894ca7bb5f1ce61dc7.js

1654 ms

39.277d36cac59918d7b838.js

39.277d36cac59918d7b838.js

1658 ms

65.6e63a8c8ca2cf6a59acb.js

65.6e63a8c8ca2cf6a59acb.js

1689 ms

20.2b9b7e7623c90d9c50b5.js

20.2b9b7e7623c90d9c50b5.js

1668 ms

35.312a70c8c608ea68d0cf.js

35.312a70c8c608ea68d0cf.js

1687 ms

60.f0d6b08b5937e641a96e.js

60.f0d6b08b5937e641a96e.js

1685 ms

61.267c2907fbd159bfc318.js

61.267c2907fbd159bfc318.js

1659 ms

49.0721e5a8ec6d7e039970.js

49.0721e5a8ec6d7e039970.js

1657 ms

webpack-765c436675090697845f.js

webpack-765c436675090697845f.js

1686 ms

framework.f951950a693377f87b11.js

framework.f951950a693377f87b11.js

1688 ms

commons.16b24ac742196e8d8eca.js

commons.16b24ac742196e8d8eca.js

1705 ms

91f3178531c1c62e4d27b722f834a66197539e8b.04e85bb285e9c96da377.js

91f3178531c1c62e4d27b722f834a66197539e8b.04e85bb285e9c96da377.js

1686 ms

362aa2e1cb5854114eb1f90d6896a23b9297be9e.3e8a9ce40eda24fd6793.js

362aa2e1cb5854114eb1f90d6896a23b9297be9e.3e8a9ce40eda24fd6793.js

1707 ms

main-27d9030410d761f0c411.js

main-27d9030410d761f0c411.js

1854 ms

c6f1a4b7eb075032039786b5aa07362b55d813e1.9551207e01f31242bbe8.js

c6f1a4b7eb075032039786b5aa07362b55d813e1.9551207e01f31242bbe8.js

1702 ms

_app-38ec5ae0064d593a7c16.js

_app-38ec5ae0064d593a7c16.js

1687 ms

cb9b4dcd.e60e14f31581656bfb48.js

cb9b4dcd.e60e14f31581656bfb48.js

1702 ms

0f1ac474.2268d241c43a680cf6c8.js

0f1ac474.2268d241c43a680cf6c8.js

1687 ms

cbbf40fbb8df40f88c3e24ceaea718b4.min.js

cbbf40fbb8df40f88c3e24ceaea718b4.min.js

1396 ms

76a316fd32b54ef155c733699e3ba2e815c7ab71.e608a85da53d7d505bb8.js

76a316fd32b54ef155c733699e3ba2e815c7ab71.e608a85da53d7d505bb8.js

1799 ms

27ec36ac922dc15281442cb5a55c49518bf1b622.a5879bf7f2e953932033.js

27ec36ac922dc15281442cb5a55c49518bf1b622.a5879bf7f2e953932033.js

1785 ms

0baf31ec139491fbde7ba9fc2da5f7b7165b3a24.dab39ee719d40241d57c.js

0baf31ec139491fbde7ba9fc2da5f7b7165b3a24.dab39ee719d40241d57c.js

1769 ms

%5Bslug%5D-5c7b7e0f4962e887a7b3.js

%5Bslug%5D-5c7b7e0f4962e887a7b3.js

1719 ms

2L2Z6-GDWNL-RH2G3-MVS3W-7M6WF

2L2Z6-GDWNL-RH2G3-MVS3W-7M6WF

1460 ms

_buildManifest.js

_buildManifest.js

1302 ms

_ssgManifest.js

_ssgManifest.js

1305 ms

imrs.php

imrs.php

1308 ms

imrs.php

imrs.php

443 ms

imrs.php

imrs.php

445 ms

imrs.php

imrs.php

443 ms

imrs.php

imrs.php

456 ms

imrs.php

imrs.php

455 ms

imrs.php

imrs.php

442 ms

imrs.php

imrs.php

229 ms

imrs.php

imrs.php

227 ms

imrs.php

imrs.php

229 ms

imrs.php

imrs.php

224 ms

imrs.php

imrs.php

225 ms

imrs.php

imrs.php

228 ms

imrs.php

imrs.php

222 ms

imrs.php

imrs.php

221 ms

imrs.php

imrs.php

210 ms

imrs.php

imrs.php

210 ms

imrs.php

imrs.php

197 ms

imrs.php

imrs.php

206 ms

imrs.php

imrs.php

196 ms

imrs.php

imrs.php

210 ms

imrs.php

imrs.php

207 ms

imrs.php

imrs.php

207 ms

imrs.php

imrs.php

190 ms

imrs.php

imrs.php

203 ms

imrs.php

imrs.php

201 ms

imrs.php

imrs.php

199 ms

imrs.php

imrs.php

197 ms

ITC_Franklin-Light.woff2

ITC_Franklin-Light.woff2

196 ms

ITC_Franklin-Bold.woff2

ITC_Franklin-Bold.woff2

541 ms

PostoniWide-Bold.woff2

PostoniWide-Bold.woff2

531 ms

PostoniWide-Regular.woff2

PostoniWide-Regular.woff2

533 ms

imrs.php

imrs.php

530 ms

imrs.php

imrs.php

531 ms

web-vitals

web-vitals

395 ms

chartbeat_mab.js

chartbeat_mab.js

804 ms

bundle.es5.min.js

bundle.es5.min.js

642 ms

config.json

config.json

620 ms

web-vitals@3.0.2

web-vitals@3.0.2

455 ms

web-vitals.iife.js

web-vitals.iife.js

36 ms

chartbeat.js

chartbeat.js

36 ms

68 ms

mab

mab

53 ms

ping

ping

47 ms

Accessibility Review

wpost.com accessibility score

85

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

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

High

Links do not have a discernible name

Best Practices

wpost.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wpost.com SEO score

98

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

wpost.com

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