Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

washingtonpost.com

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

Page Load Speed

7.2 sec in total

First Response

1 sec

Resources Loaded

1.9 sec

Page Rendered

4.2 sec

washingtonpost.com screenshot

About Website

Visit washingtonpost.com now to see the best up-to-date Washington Post content for United States and also check out these interesting facts you probably never knew about 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 washingtonpost.com

Key Findings

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

Performance Metrics

washingtonpost.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

28/100

10%

LCP (Largest Contentful Paint)

Value30.0 s

0/100

25%

SI (Speed Index)

Value28.3 s

0/100

10%

TBT (Total Blocking Time)

Value29,100 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value55.5 s

0/100

10%

Network Requests Diagram

www.washingtonpost.com

1039 ms

main.js

83 ms

tetro.min.js

72 ms

main.js

1071 ms

d21cc98347c3b2e1.css

96 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 99% of them (77 requests) were addressed to the original Washingtonpost.com, 1% (1 request) were made to S.go-mpulse.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Washingtonpost.com.

Page Optimization Overview & Recommendations

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

Content Size

2.5 MB

After Optimization

499.7 kB

In fact, the total size of Washingtonpost.com main page is 2.5 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. 85% 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 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 2.0 MB

  • Original 2.3 MB
  • After minification 2.3 MB
  • After compression 288.1 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 2.0 MB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

Requests Breakdown

Number of requests can be reduced by 47 (64%)

Requests Now

73

After Optimization

26

The browser has sent 73 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 48 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

washingtonpost.com accessibility score

83

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

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

Best Practices

washingtonpost.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

washingtonpost.com SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 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 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 Washington Post. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: