Tools & Wizards About Us
inrich.com screenshot

Report Summary

  • 12

    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

inrich.com

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

Page Load Speed

1 sec in total

First Response

77 ms

Resources Loaded

488 ms

Page Rendered

460 ms

inrich.com screenshot

About Website

Visit inrich.com now to see the best up-to-date Inrich content and also check out these interesting facts you probably never knew about inrich.com

Read breaking news for the city of Richmond, Henrico County, and the Metropolitan Area of Virginia. The latest weather, crime, politics, and more.

Visit inrich.com

Key Findings

We analyzed Inrich.com page load time and found that the first response time was 77 ms and then it took 948 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

inrich.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value8,200 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.174

69/100

15%

TTI (Time to Interactive)

Value35.0 s

0/100

10%

Network Requests Diagram

richmond.com

77 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

44 ms

layout.a20a82cd2d0545ab6b327211aa0ea22b.css

67 ms

lee.ds.css

53 ms

flex-notification-controls.e115619c5ab5d4eb38fbd29cc0d2ea9b.css

56 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Inrich.com, 21% (9 requests) were made to Richmond.com and 5% (2 requests) were made to Bloximages.chicago2.vip.townnews.com. The less responsive or slowest element that took the longest time to load (190 ms) relates to the external source Bloximages.newyork1.vip.townnews.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 429.0 kB (44%)

Content Size

976.4 kB

After Optimization

547.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inrich.com main page is 976.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Javascripts take 451.2 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 373.9 kB

  • Original 415.2 kB
  • After minification 333.8 kB
  • After compression 41.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. This page needs HTML code to be minified as it can gain 81.4 kB, which is 20% 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 373.9 kB or 90% of the original size.

Image Optimization

-10%

Potential reduce by 2.9 kB

  • Original 30.1 kB
  • After minification 27.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. Inrich images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 36.3 kB

  • Original 451.2 kB
  • After minification 451.2 kB
  • After compression 414.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

-20%

Potential reduce by 15.8 kB

  • Original 79.8 kB
  • After minification 79.8 kB
  • After compression 64.0 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. Inrich.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 31 (82%)

Requests Now

38

After Optimization

7

  • Images
  • JavaScript
  • CSS

The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Inrich. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 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

77 ms

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

bootstrap.min.87df60d54091cf1e8f8173c2e568260c.css

44 ms

layout.a20a82cd2d0545ab6b327211aa0ea22b.css

layout.a20a82cd2d0545ab6b327211aa0ea22b.css

67 ms

lee.ds.css

lee.ds.css

53 ms

flex-notification-controls.e115619c5ab5d4eb38fbd29cc0d2ea9b.css

flex-notification-controls.e115619c5ab5d4eb38fbd29cc0d2ea9b.css

56 ms

owl.carousel.d631cca58a0d014854c4a6c1815f1da3.css

owl.carousel.d631cca58a0d014854c4a6c1815f1da3.css

57 ms

osano.js

osano.js

70 ms

access.d7adebba498598b0ec2c.js

access.d7adebba498598b0ec2c.js

42 ms

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

jquery.min.d6d18fcf88750a16d256e72626e676a6.js

66 ms

user.js

user.js

66 ms

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

bootstrap.min.d457560d3dfbf1d56a225eb99d7b0702.js

66 ms

common.08a61544f369cc43bf02e71b2d10d49f.js

common.08a61544f369cc43bf02e71b2d10d49f.js

84 ms

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

tnt.ee95c0b6f1daceb31bf5ef84353968c6.js

86 ms

application.3c64d611e594b45dd35b935162e79d85.js

application.3c64d611e594b45dd35b935162e79d85.js

85 ms

apstag.js

apstag.js

84 ms

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

tnt.navigation.accessibility.7a9170240d21440159b9bd59db72933b.js

94 ms

richmond.com.v2.js

richmond.com.v2.js

85 ms

owl.carousel.50dc41fa734414148ce4b489fd904c5f.js

owl.carousel.50dc41fa734414148ce4b489fd904c5f.js

98 ms

tnt.notify.a814fe612f2dcba9061edc229aeaf90b.js

tnt.notify.a814fe612f2dcba9061edc229aeaf90b.js

100 ms

tnt.notify.panel.bacbeac9a1ca6ee75b79b21a0e2e99f2.js

tnt.notify.panel.bacbeac9a1ca6ee75b79b21a0e2e99f2.js

100 ms

firebase-app.js

firebase-app.js

53 ms

firebase-messaging.js

firebase-messaging.js

84 ms

messaging.js

messaging.js

67 ms

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

tnt.ads.adverts.66a3812a7b5c12fde8cd998fd691ad7d.js

97 ms

tracking.js

tracking.js

82 ms

prebid8.39.0.js

prebid8.39.0.js

99 ms

lee.common.js

lee.common.js

97 ms

fontawesome.2ad05b1a23d01a1240fecfa3e776a67c.js

fontawesome.2ad05b1a23d01a1240fecfa3e776a67c.js

190 ms

tracker.js

tracker.js

84 ms

op.js

op.js

52 ms

richmond.com.js

richmond.com.js

171 ms

dfp.lazy.ozone.js

dfp.lazy.ozone.js

171 ms

gtm.js

gtm.js

130 ms

tracker.gif

tracker.gif

82 ms

gtm.js

gtm.js

83 ms

syd-logo.png

syd-logo.png

39 ms

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

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

62 ms

user_no_avatar.82c8fc38eb25dca10493a994ca1bfb90.png

user_no_avatar.82c8fc38eb25dca10493a994ca1bfb90.png

61 ms

newsplus_white.png

newsplus_white.png

62 ms

logo-tagline.png

logo-tagline.png

59 ms

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

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

60 ms

65 ms

serif-ds.woff

serif-ds.woff

13 ms

Accessibility Review

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

inrich.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 Inrich.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 Inrich.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

inrich.com

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