Tools & Wizards About Us
js.washingtonpost.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 0

    Best Practices

  • 99

    SEO

    Google-friendlier than
    93% of websites

js.washingtonpost.com

The Washington Post - Breaking news and latest headlines, U.S. news, world news, and video - The Washington Post

Page Load Speed

4.1 sec in total

First Response

163 ms

Resources Loaded

1.3 sec

Page Rendered

2.7 sec

js.washingtonpost.com screenshot

About Website

Welcome to js.washingtonpost.com homepage info - get ready to check Js Washington Post best content for United States right away, or after learning these important things about js.washingtonpost.com

Breaking news, live coverage, investigations, analysis, video, photos and opinions from The Washington Post. Subscribe for the latest on U.S. and international news, politics, business, technology, cl...

Visit js.washingtonpost.com

Key Findings

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

Performance Metrics

js.washingtonpost.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value15.3 s

1/100

10%

TBT (Total Blocking Time)

Value15,370 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.111

87/100

15%

TTI (Time to Interactive)

Value45.8 s

0/100

10%

Network Requests Diagram

www.washingtonpost.com

163 ms

tetro.min.js

90 ms

main.js

90 ms

main.js

359 ms

gtm.js

138 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Js.washingtonpost.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 (863 ms) relates to the external source Washingtonpost.com.

Page Optimization Overview & Recommendations

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

Content Size

2.1 MB

After Optimization

672.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Js.washingtonpost.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 230.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 1.4 MB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 13 B

  • Original 416.0 kB
  • After minification 416.0 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. Js Washington 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 48 (52%)

Requests Now

92

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.washingtonpost.com

www.washingtonpost.com

163 ms

tetro.min.js

tetro.min.js

90 ms

main.js

main.js

90 ms

main.js

main.js

359 ms

gtm.js

gtm.js

138 ms

optimize.js

optimize.js

357 ms

scroll.js

scroll.js

112 ms

M

M

547 ms

ef4b35930a189b02c101.css

ef4b35930a189b02c101.css

204 ms

polyfills-c7210d653eb000f69002.js

polyfills-c7210d653eb000f69002.js

299 ms

c8f7fe3b0e41be846d5687592cf2018ff6e22687.6cd3d9310fb629cabbdb.js

c8f7fe3b0e41be846d5687592cf2018ff6e22687.6cd3d9310fb629cabbdb.js

298 ms

38.2036f6fb14c8b706c331.js

38.2036f6fb14c8b706c331.js

155 ms

49.3be7bfbb3eb8185a9760.js

49.3be7bfbb3eb8185a9760.js

294 ms

7e6c0f8bb652c3b8f51c7037ba32240ea3cc4901.39844d4eadec2cf4908b.js

7e6c0f8bb652c3b8f51c7037ba32240ea3cc4901.39844d4eadec2cf4908b.js

361 ms

63.bce811879a3209d7218f.js

63.bce811879a3209d7218f.js

362 ms

52.a810015a157e41af3b26.js

52.a810015a157e41af3b26.js

359 ms

47.521c2dca1ef20f96fbe7.js

47.521c2dca1ef20f96fbe7.js

298 ms

50.27f79e1b9b828fe5109a.js

50.27f79e1b9b828fe5109a.js

361 ms

69.d718f440a0a9e70689b0.js

69.d718f440a0a9e70689b0.js

361 ms

65.6e63a8c8ca2cf6a59acb.js

65.6e63a8c8ca2cf6a59acb.js

359 ms

20.2b9b7e7623c90d9c50b5.js

20.2b9b7e7623c90d9c50b5.js

496 ms

67.b01ee5676547819a9ef5.js

67.b01ee5676547819a9ef5.js

496 ms

43.194f0d696c79592678aa.js

43.194f0d696c79592678aa.js

497 ms

61.90886fd91eeeedf75726.js

61.90886fd91eeeedf75726.js

496 ms

40.a6514d0e618642d95965.js

40.a6514d0e618642d95965.js

495 ms

66.60b49083e20115563f80.js

66.60b49083e20115563f80.js

494 ms

35.312a70c8c608ea68d0cf.js

35.312a70c8c608ea68d0cf.js

568 ms

59.3735923b5377b0069581.js

59.3735923b5377b0069581.js

568 ms

60.7870bbda8c7863c0270a.js

60.7870bbda8c7863c0270a.js

567 ms

48.866c4d447b1fd0be5967.js

48.866c4d447b1fd0be5967.js

568 ms

webpack-cd6265837d360d55a12e.js

webpack-cd6265837d360d55a12e.js

569 ms

framework.f951950a693377f87b11.js

framework.f951950a693377f87b11.js

567 ms

commons.a3258ba176346f73635b.js

commons.a3258ba176346f73635b.js

625 ms

91f3178531c1c62e4d27b722f834a66197539e8b.04e85bb285e9c96da377.js

91f3178531c1c62e4d27b722f834a66197539e8b.04e85bb285e9c96da377.js

623 ms

362aa2e1cb5854114eb1f90d6896a23b9297be9e.3e8a9ce40eda24fd6793.js

362aa2e1cb5854114eb1f90d6896a23b9297be9e.3e8a9ce40eda24fd6793.js

625 ms

main-27d9030410d761f0c411.js

main-27d9030410d761f0c411.js

625 ms

c6f1a4b7eb075032039786b5aa07362b55d813e1.9551207e01f31242bbe8.js

c6f1a4b7eb075032039786b5aa07362b55d813e1.9551207e01f31242bbe8.js

623 ms

_app-38ec5ae0064d593a7c16.js

_app-38ec5ae0064d593a7c16.js

623 ms

cb9b4dcd.e60e14f31581656bfb48.js

cb9b4dcd.e60e14f31581656bfb48.js

863 ms

0f1ac474.2268d241c43a680cf6c8.js

0f1ac474.2268d241c43a680cf6c8.js

629 ms

cbbf40fbb8df40f88c3e24ceaea718b4.min.js

cbbf40fbb8df40f88c3e24ceaea718b4.min.js

147 ms

76a316fd32b54ef155c733699e3ba2e815c7ab71.36b0fe74e4880345e41c.js

76a316fd32b54ef155c733699e3ba2e815c7ab71.36b0fe74e4880345e41c.js

630 ms

27ec36ac922dc15281442cb5a55c49518bf1b622.68004c3c0700950783c7.js

27ec36ac922dc15281442cb5a55c49518bf1b622.68004c3c0700950783c7.js

610 ms

0baf31ec139491fbde7ba9fc2da5f7b7165b3a24.dab39ee719d40241d57c.js

0baf31ec139491fbde7ba9fc2da5f7b7165b3a24.dab39ee719d40241d57c.js

601 ms

%5Bslug%5D-5c7b7e0f4962e887a7b3.js

%5Bslug%5D-5c7b7e0f4962e887a7b3.js

479 ms

2L2Z6-GDWNL-RH2G3-MVS3W-7M6WF

2L2Z6-GDWNL-RH2G3-MVS3W-7M6WF

317 ms

_buildManifest.js

_buildManifest.js

347 ms

_ssgManifest.js

_ssgManifest.js

348 ms

imrs.php

imrs.php

341 ms

imrs.php

imrs.php

396 ms

imrs.php

imrs.php

393 ms

web-vitals

web-vitals

307 ms

chartbeat_mab.js

chartbeat_mab.js

306 ms

imrs.php

imrs.php

508 ms

imrs.php

imrs.php

338 ms

imrs.php

imrs.php

335 ms

imrs.php

imrs.php

338 ms

imrs.php

imrs.php

339 ms

imrs.php

imrs.php

338 ms

imrs.php

imrs.php

206 ms

imrs.php

imrs.php

207 ms

imrs.php

imrs.php

207 ms

imrs.php

imrs.php

208 ms

imrs.php

imrs.php

207 ms

imrs.php

imrs.php

208 ms

imrs.php

imrs.php

207 ms

ITC_Franklin-Light.woff2

ITC_Franklin-Light.woff2

136 ms

ITC_Franklin-Bold.woff2

ITC_Franklin-Bold.woff2

137 ms

PostoniWide-Bold.woff2

PostoniWide-Bold.woff2

138 ms

PostoniWide-Regular.woff2

PostoniWide-Regular.woff2

136 ms

imrs.php

imrs.php

138 ms

web-vitals@3.0.2

web-vitals@3.0.2

74 ms

imrs.php

imrs.php

231 ms

imrs.php

imrs.php

231 ms

imrs.php

imrs.php

233 ms

imrs.php

imrs.php

236 ms

imrs.php

imrs.php

236 ms

imrs.php

imrs.php

235 ms

imrs.php

imrs.php

234 ms

imrs.php

imrs.php

239 ms

imrs.php

imrs.php

239 ms

imrs.php

imrs.php

234 ms

imrs.php

imrs.php

363 ms

imrs.php

imrs.php

231 ms

imrs.php

imrs.php

361 ms

imrs.php

imrs.php

231 ms

imrs.php

imrs.php

180 ms

imrs.php

imrs.php

180 ms

imrs.php

imrs.php

180 ms

web-vitals.iife.js

web-vitals.iife.js

171 ms

imrs.php

imrs.php

177 ms

imrs.php

imrs.php

178 ms

imrs.php

imrs.php

178 ms

imrs.php

imrs.php

178 ms

imrs.php

imrs.php

177 ms

imrs.php

imrs.php

298 ms

imrs.php

imrs.php

296 ms

config.json

config.json

277 ms

bundle.es5.min.js

bundle.es5.min.js

139 ms

chartbeat.js

chartbeat.js

17 ms

Accessibility Review

js.washingtonpost.com accessibility score

78

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-hidden="true"] elements contain focusable descendents

High

[role] values are not valid

High

ARIA IDs are not unique

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

SEO Factors

js.washingtonpost.com SEO score

99

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

js.washingtonpost.com

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