Tools & Wizards About Us
post-dispatch.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 0

    Best Practices

  • 83

    SEO

    Google-friendlier than
    46% of websites

post-dispatch.com

St. Louis Post-Dispatch | Breaking News | Read St. Louis, MO and Missouri breaking news. Get latest news, events and information on Missouri sports, w...

Page Load Speed

1.8 sec in total

First Response

82 ms

Resources Loaded

1.1 sec

Page Rendered

582 ms

post-dispatch.com screenshot

About Website

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

Read breaking news for St. Louis, Missouri, serving the St. Louis metropolitan area, weather, traffic, crime, sports, entertainment, politics, and more on www.stltoday.com.

Visit post-dispatch.com

Key Findings

We analyzed Post-dispatch.com page load time and found that the first response time was 82 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

post-dispatch.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value24.9 s

0/100

10%

TBT (Total Blocking Time)

Value14,210 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.124

83/100

15%

TTI (Time to Interactive)

Value50.1 s

0/100

10%

Network Requests Diagram

post-dispatch.com

82 ms

www.stltoday.com

26 ms

www.stltoday.com

80 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

99 ms

layout.d9bf9fa5b377514df7224a864456e96d.css

90 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Post-dispatch.com, 41% (26 requests) were made to Bloximages.newyork1.vip.townnews.com and 30% (19 requests) were made to Stltoday.com. The less responsive or slowest element that took the longest time to load (344 ms) relates to the external source Polyfill.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 583.1 kB (49%)

Content Size

1.2 MB

After Optimization

614.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Post-dispatch.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. 70% of websites need less resources to load. HTML takes 551.5 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 499.1 kB

  • Original 551.5 kB
  • After minification 450.4 kB
  • After compression 52.4 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 101.2 kB, which is 18% 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 499.1 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-12%

Potential reduce by 68.1 kB

  • Original 549.5 kB
  • After minification 549.5 kB
  • After compression 481.4 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 68.1 kB or 12% of the original size.

CSS Optimization

-20%

Potential reduce by 15.8 kB

  • Original 79.7 kB
  • After minification 79.7 kB
  • After compression 63.9 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. Post-dispatch.com needs all CSS files to be minified and compressed as it can save up to 15.8 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (81%)

Requests Now

48

After Optimization

9

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Post 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 35 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

post-dispatch.com

post-dispatch.com

82 ms

www.stltoday.com

www.stltoday.com

26 ms

www.stltoday.com

www.stltoday.com

80 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

99 ms

layout.d9bf9fa5b377514df7224a864456e96d.css

layout.d9bf9fa5b377514df7224a864456e96d.css

90 ms

lee.ds.css

lee.ds.css

86 ms

flex-notification-controls.e115619c5ab5d4eb38fbd29cc0d2ea9b.css

flex-notification-controls.e115619c5ab5d4eb38fbd29cc0d2ea9b.css

85 ms

stl.dsv3.css

stl.dsv3.css

85 ms

owl.carousel.d631cca58a0d014854c4a6c1815f1da3.css

owl.carousel.d631cca58a0d014854c4a6c1815f1da3.css

102 ms

osano.js

osano.js

97 ms

access.d7adebba498598b0ec2c.js

access.d7adebba498598b0ec2c.js

45 ms

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

102 ms

user.js

user.js

68 ms

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

101 ms

common.08a61544f369cc43bf02e71b2d10d49f.js

common.08a61544f369cc43bf02e71b2d10d49f.js

102 ms

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

118 ms

application.3c64d611e594b45dd35b935162e79d85.js

application.3c64d611e594b45dd35b935162e79d85.js

121 ms

polyfill.min.js

polyfill.min.js

344 ms

apstag.js

apstag.js

94 ms

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

118 ms

stltoday.com.v2.js

stltoday.com.v2.js

116 ms

owl.carousel.50dc41fa734414148ce4b489fd904c5f.js

owl.carousel.50dc41fa734414148ce4b489fd904c5f.js

121 ms

tnt.notify.a814fe612f2dcba9061edc229aeaf90b.js

tnt.notify.a814fe612f2dcba9061edc229aeaf90b.js

124 ms

tnt.notify.panel.bacbeac9a1ca6ee75b79b21a0e2e99f2.js

tnt.notify.panel.bacbeac9a1ca6ee75b79b21a0e2e99f2.js

121 ms

firebase-app.js

firebase-app.js

88 ms

firebase-messaging.js

firebase-messaging.js

116 ms

messaging.js

messaging.js

115 ms

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

119 ms

tracking.js

tracking.js

98 ms

prebid8.39.0.js

prebid8.39.0.js

123 ms

lee.common.js

lee.common.js

123 ms

fontawesome.568f3d1ab17b33ce05854081baadadac.js

fontawesome.568f3d1ab17b33ce05854081baadadac.js

128 ms

tracker.js

tracker.js

114 ms

op.js

op.js

101 ms

stltoday.com.js

stltoday.com.js

109 ms

dfp.lazy.ozone.js

dfp.lazy.ozone.js

114 ms

gtm.js

gtm.js

54 ms

[object%20URL]

[object%20URL]

23 ms

9b98b5bc-7564-11ec-9b25-e32a5add2fc1.png

9b98b5bc-7564-11ec-9b25-e32a5add2fc1.png

24 ms

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

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

21 ms

user_no_avatar.82c8fc38eb25dca10493a994ca1bfb90.png

user_no_avatar.82c8fc38eb25dca10493a994ca1bfb90.png

22 ms

newsplus_white.png

newsplus_white.png

22 ms

logo-tagline.png

logo-tagline.png

22 ms

tracker.gif

tracker.gif

20 ms

gtm.js

gtm.js

60 ms

20 ms

33 ms

80 ms

48 ms

serif-ds.woff

serif-ds.woff

48 ms

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

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

163 ms

52 ms

47 ms

iframe

iframe

99 ms

53 ms

js

js

64 ms

analytics.js

analytics.js

149 ms

9044ad82-110c-4c5a-ae3e-7f494f648854

9044ad82-110c-4c5a-ae3e-7f494f648854

11 ms

32 ms

121 ms

getuid

getuid

160 ms

linkid.js

linkid.js

12 ms

ml.gz.js

ml.gz.js

16 ms

i

i

16 ms

Accessibility Review

post-dispatch.com accessibility score

88

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

SEO Factors

post-dispatch.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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Post-dispatch.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 Post-dispatch.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

post-dispatch.com

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