Tools & Wizards About Us
eedition.washingtontimes.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% 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

  • 96

    SEO

    Google-friendlier than
    90% of websites

eedition.washingtontimes.com

National Digital Edition Transition - Washington Times

Page Load Speed

1.9 sec in total

First Response

59 ms

Resources Loaded

1.5 sec

Page Rendered

323 ms

eedition.washingtontimes.com screenshot

About Website

Welcome to eedition.washingtontimes.com homepage info - get ready to check E Edition Washington Times best content for United States right away, or after learning these important things about eedition.washingtontimes.com

The Washington Times delivers breaking news and commentary on the issues that affect the future of our nation.

Visit eedition.washingtontimes.com

Key Findings

We analyzed Eedition.washingtontimes.com page load time and found that the first response time was 59 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

eedition.washingtontimes.com performance score

22

Measured Metrics

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%

Network Requests Diagram

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.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.6 kB (12%)

Content Size

1.0 MB

After Optimization

910.1 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Eedition.washingtontimes.com main page is 1.0 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 840.9 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

-2%

Potential reduce by 14.6 kB

  • Original 840.9 kB
  • After minification 840.9 kB
  • After compression 826.3 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 Breakdown

Number of requests can be reduced by 35 (70%)

Requests Now

50

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

eedition.washingtontimes.com

eedition.washingtontimes.com

59 ms

eedition.washingtontimes.com

eedition.washingtontimes.com

40 ms

75 ms

main.85b45e5ae2e7.css

main.85b45e5ae2e7.css

57 ms

font-awesome.css

font-awesome.css

91 ms

ari-ci.js

ari-ci.js

78 ms

chartbeat_mab.js

chartbeat_mab.js

85 ms

pushly-sdk.min.js

pushly-sdk.min.js

92 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

92 ms

gpt.js

gpt.js

228 ms

twt_app.37f4bfb0660c.js

twt_app.37f4bfb0660c.js

70 ms

85d8ddb05bcf089b2c29e59623ae519ad02e2a929bfaac10d875c38b93211525

85d8ddb05bcf089b2c29e59623ae519ad02e2a929bfaac10d875c38b93211525

207 ms

prebid8.42.0.5866ee185820.js

prebid8.42.0.5866ee185820.js

88 ms

global.5b5acddae9c7.js

global.5b5acddae9c7.js

71 ms

css2

css2

62 ms

brandjs.js

brandjs.js

23 ms

chartbeat.js

chartbeat.js

82 ms

subscriptions.js

subscriptions.js

81 ms

advertising.js

advertising.js

192 ms

a8a084cb03100cac9e44c5e69dd87fd1686ea33cd4-prod.js

a8a084cb03100cac9e44c5e69dd87fd1686ea33cd4-prod.js

387 ms

player.js

player.js

380 ms

twt-logo.3490fc26f61e.svg

twt-logo.3490fc26f61e.svg

163 ms

quant.js

quant.js

267 ms

insight.min.js

insight.min.js

334 ms

twt-logo-white.7e41d5d882fc.svg

twt-logo-white.7e41d5d882fc.svg

121 ms

white-mail-icon.02bb72920d70.svg

white-mail-icon.02bb72920d70.svg

119 ms

W_RedCircle.af82cbe68606.svg

W_RedCircle.af82cbe68606.svg

120 ms

gtm.js

gtm.js

250 ms

load

load

304 ms

mab

mab

264 ms

ping

ping

262 ms

pubads_impl.js

pubads_impl.js

65 ms

font

font

253 ms

135 ms

main.js

main.js

122 ms

5856

5856

176 ms

apstag.js

apstag.js

159 ms

rules-p-c69_1G6fdlihY.js

rules-p-c69_1G6fdlihY.js

167 ms

js

js

152 ms

uwt.js

uwt.js

332 ms

core.js

core.js

292 ms

a-01en.min.js

a-01en.min.js

291 ms

analytics.js

analytics.js

286 ms

fbevents.js

fbevents.js

244 ms

tinypass.min.js

tinypass.min.js

309 ms

567611540109994

567611540109994

69 ms

load-legacy.js

load-legacy.js

86 ms

piano.es5.js

piano.es5.js

61 ms

adsct

adsct

421 ms

adsct

adsct

418 ms

329974197684672

329974197684672

169 ms

t

t

117 ms

collect

collect

104 ms

collect

collect

23 ms

Accessibility Review

eedition.washingtontimes.com accessibility score

85

Accessibility Issues

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

Buttons do not have an accessible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

eedition.washingtontimes.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

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

eedition.washingtontimes.com SEO score

96

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

eedition.washingtontimes.com

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: