Access eedition.washingtontimes.com. National Digital Edition Transition

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value4.8 s

68/100

10%

TBT (Total Blocking Time)

Value4,230 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.232

54/100

15%

TTI (Time to Interactive)

Value20.8 s

2/100

10%

eedition.washingtontimes.com

59 ms

eedition.washingtontimes.com

40 ms

75 ms

main.85b45e5ae2e7.css

57 ms

font-awesome.css

91 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Eedition.washingtontimes.com, 20% (11 requests) were made to Washingtontimes.com and 6% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (421 ms) relates to the external source T.co.

Content Size

1.1 MB

After Optimization

909.7 kB

In fact, the total size of Eedition.washingtontimes.com main page is 1.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. 70% of websites need less resources to load. Javascripts take 872.4 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 108.0 kB

Original 153.3 kB
After minification 144.5 kB
After compression 45.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 108.0 kB or 70% of the original size.

JavaScript Optimization

-5%

Potential reduce by 46.5 kB

Original 872.4 kB
After minification 872.4 kB
After compression 825.9 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.

CSS Optimization

-0%

Potential reduce by 0 B

Original 38.5 kB
After minification 38.5 kB
After compression 38.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Eedition.washingtontimes.com has all CSS files already compressed.

Requests Now

After Optimization

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Edition Washington Times. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Issues

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

Buttons do not have an accessible name

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

High

Requests the notification permission on page load

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

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 Eedition.washingtontimes.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 Eedition.washingtontimes.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 description is not detected on the main page of E Edition Washington Times. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: