Access js.washingtonpost.com. The Washington Post - Breaking news and latest headlines, U.S. news, world news, and video

Report Summary

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

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%

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.

Content Size

2.1 MB

After Optimization

672.4 kB

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 Now

After Optimization

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.

Accessibility Issues

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.

High

[aria-hidden="true"] elements contain focusable descendents

High

[role] values are not valid

High

ARIA IDs are not unique

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

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

High

Heading elements are not in a sequentially-descending order

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.

High

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

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

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

Search Engine Optimization Advices

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

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

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: