Tools & Wizards About Us
m.timesdispatch.com screenshot

Report Summary

  • 1

    Performance

    Renders faster than
    19% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

m.timesdispatch.com

Richmond Times-Dispatch | Breaking News and Sports | Read Richmond, VA and Virginia breaking news. Get latest news, events and information on sports, ...

Page Load Speed

4 sec in total

First Response

18 ms

Resources Loaded

3.2 sec

Page Rendered

749 ms

m.timesdispatch.com screenshot

About Website

Visit m.timesdispatch.com now to see the best up-to-date M Times Dispatch content for United States and also check out these interesting facts you probably never knew about m.timesdispatch.com

Read the latest Richmond, VA news. Get the latest on Virginia weather, sports, and things to do.

Visit m.timesdispatch.com

Key Findings

We analyzed M.timesdispatch.com page load time and found that the first response time was 18 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

m.timesdispatch.com performance score

1

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value20.4 s

0/100

10%

TBT (Total Blocking Time)

Value17,210 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.905

3/100

15%

TTI (Time to Interactive)

Value47.3 s

0/100

10%

Network Requests Diagram

richmond.com

18 ms

richmond.com

73 ms

bootstrap.min.c58a1beaa3640fa94c3db09673c4d95c.css

150 ms

layout.214f487d157f8d3739105bfac8086bac.css

136 ms

lee.ds.css

142 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original M.timesdispatch.com, 11% (12 requests) were made to Richmond.com and 6% (7 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Qnhtg9kbqjgw2izax.ay.delivery.

Page Optimization Overview & Recommendations

Page size can be reduced by 560.4 kB (47%)

Content Size

1.2 MB

After Optimization

633.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of M.timesdispatch.com main page is 1.2 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 592.5 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 531.4 kB

  • Original 592.5 kB
  • After minification 494.6 kB
  • After compression 61.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. This page needs HTML code to be minified as it can gain 97.9 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 531.4 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 231 B

  • Original 306.5 kB
  • After minification 306.2 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. M Times Dispatch images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 13.1 kB

  • Original 215.8 kB
  • After minification 215.7 kB
  • After compression 202.6 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

-20%

Potential reduce by 15.7 kB

  • Original 79.1 kB
  • After minification 79.1 kB
  • After compression 63.4 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. M.timesdispatch.com needs all CSS files to be minified and compressed as it can save up to 15.7 kB or 20% of the original size.

Requests Breakdown

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

Requests Now

93

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

richmond.com

richmond.com

18 ms

richmond.com

richmond.com

73 ms

bootstrap.min.c58a1beaa3640fa94c3db09673c4d95c.css

bootstrap.min.c58a1beaa3640fa94c3db09673c4d95c.css

150 ms

layout.214f487d157f8d3739105bfac8086bac.css

layout.214f487d157f8d3739105bfac8086bac.css

136 ms

lee.ds.css

lee.ds.css

142 ms

flex-notification-controls.e115619c5ab5d4eb38fbd29cc0d2ea9b.css

flex-notification-controls.e115619c5ab5d4eb38fbd29cc0d2ea9b.css

158 ms

owl.carousel.d631cca58a0d014854c4a6c1815f1da3.css

owl.carousel.d631cca58a0d014854c4a6c1815f1da3.css

157 ms

cc.js

cc.js

112 ms

access.js

access.js

81 ms

access-legacy.js

access-legacy.js

128 ms

osano.js

osano.js

133 ms

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

176 ms

user.js

user.js

110 ms

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

171 ms

common.08a61544f369cc43bf02e71b2d10d49f.js

common.08a61544f369cc43bf02e71b2d10d49f.js

171 ms

tnt.cfb7b302c42616744a59428baa754111.js

tnt.cfb7b302c42616744a59428baa754111.js

172 ms

application.81be8dcdc3040973d38ec593fcfe8805.js

application.81be8dcdc3040973d38ec593fcfe8805.js

173 ms

polyfill.min.js

polyfill.min.js

210 ms

apstag.js

apstag.js

159 ms

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

165 ms

richmond.com.js

richmond.com.js

201 ms

owl.carousel.50dc41fa734414148ce4b489fd904c5f.js

owl.carousel.50dc41fa734414148ce4b489fd904c5f.js

203 ms

tnt.notify.a814fe612f2dcba9061edc229aeaf90b.js

tnt.notify.a814fe612f2dcba9061edc229aeaf90b.js

195 ms

tnt.notify.panel.bacbeac9a1ca6ee75b79b21a0e2e99f2.js

tnt.notify.panel.bacbeac9a1ca6ee75b79b21a0e2e99f2.js

198 ms

firebase-app.js

firebase-app.js

159 ms

firebase-messaging.js

firebase-messaging.js

160 ms

messaging.js

messaging.js

122 ms

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

195 ms

tracking.js

tracking.js

128 ms

lee.common.js

lee.common.js

197 ms

fontawesome.dd9f72114a809f3dc0619831f68070f4.js

fontawesome.dd9f72114a809f3dc0619831f68070f4.js

202 ms

tracker.js

tracker.js

127 ms

op.js

op.js

134 ms

userstitch.load.js

userstitch.load.js

188 ms

dfp.floor.js

dfp.floor.js

184 ms

dfp.lazy.pwt.js

dfp.lazy.pwt.js

191 ms

gtm.js

gtm.js

122 ms

tracker.gif

tracker.gif

44 ms

gtm.js

gtm.js

46 ms

45923b54-8390-11ec-98e6-a70b22a493cc.png

45923b54-8390-11ec-98e6-a70b22a493cc.png

32 ms

syd-logo.png

syd-logo.png

28 ms

%7B%7Bimage%7D%7D

%7B%7Bimage%7D%7D

26 ms

user_no_avatar.82c8fc38eb25dca10493a994ca1bfb90.png

user_no_avatar.82c8fc38eb25dca10493a994ca1bfb90.png

27 ms

analytics.js

analytics.js

177 ms

gtm.js

gtm.js

142 ms

gtm.js

gtm.js

168 ms

sp-gzip-2-17-3.js

sp-gzip-2-17-3.js

568 ms

fbevents.js

fbevents.js

371 ms

beacon.js

beacon.js

369 ms

a-0584.min.js

a-0584.min.js

610 ms

iframe

iframe

609 ms

client-v2.9.0-openWrap.js

client-v2.9.0-openWrap.js

1179 ms

5b5dc540-ca6c-013a-51e3-0cc47a8ffaac

5b5dc540-ca6c-013a-51e3-0cc47a8ffaac

365 ms

js

js

300 ms

serif-ds.woff

serif-ds.woff

64 ms

js

js

315 ms

6334d8bf797e2.preview.jpg

6334d8bf797e2.preview.jpg

356 ms

linkid.js

linkid.js

311 ms

publisher:getClientId

publisher:getClientId

968 ms

6334bbebead33.preview.jpg

6334bbebead33.preview.jpg

285 ms

6334bafb1703f.preview.jpg

6334bafb1703f.preview.jpg

284 ms

%7B%7Bimage%7D%7D

%7B%7Bimage%7D%7D

262 ms

analytics.min.js

analytics.min.js

904 ms

js

js

322 ms

iframe

iframe

817 ms

identity.js

identity.js

234 ms

961211893969940

961211893969940

430 ms

sync-container.js

sync-container.js

95 ms

ml.gz.js

ml.gz.js

173 ms

6334f7af231c2.image.jpg

6334f7af231c2.image.jpg

246 ms

6334b77a4ae9f.image.jpg

6334b77a4ae9f.image.jpg

290 ms

collect

collect

219 ms

collect

collect

279 ms

collect

collect

261 ms

collect

collect

278 ms

collect

collect

255 ms

collect

collect

277 ms

settings

settings

115 ms

i

i

177 ms

870.bundle.323974846b6d45afb45e.js

870.bundle.323974846b6d45afb45e.js

91 ms

ajs-destination.bundle.35a8f6f19959bf2f455f.js

ajs-destination.bundle.35a8f6f19959bf2f455f.js

107 ms

c

c

801 ms

ga-audiences

ga-audiences

88 ms

pixel

pixel

83 ms

ga-audiences

ga-audiences

84 ms

j

j

28 ms

m

m

416 ms

a-0584

a-0584

69 ms

yy2

yy2

44 ms

pixel

pixel

15 ms

syncd

syncd

153 ms

129 ms

141 ms

generic

generic

84 ms

35759

35759

51 ms

7fb1cafdc2b549089f858c31b7c35f39

7fb1cafdc2b549089f858c31b7c35f39

20 ms

appnexus

appnexus

26 ms

setuid

setuid

23 ms

7fb1cafdc2b549089f858c31b7c35f39

7fb1cafdc2b549089f858c31b7c35f39

14 ms

live_intent_sync

live_intent_sync

92 ms

10 ms

35004

35004

10 ms

9 ms

rt=ifr

rt=ifr

54 ms

sync

sync

45 ms

generic

generic

15 ms

insync

insync

57 ms

5907

5907

192 ms

gdpr_consent=

gdpr_consent=

60 ms

gdpr_consent=

gdpr_consent=

7 ms

insync

insync

6 ms

gdpr=0

gdpr=0

7 ms

Accessibility Review

m.timesdispatch.com accessibility score

81

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-*] attributes do not match their roles

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

m.timesdispatch.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

SEO Factors

m.timesdispatch.com SEO score

83

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 M.timesdispatch.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 M.timesdispatch.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

m.timesdispatch.com

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