Tools & Wizards About Us
rich.agency screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

rich.agency

Inbound Marketing Firm | THE RiCH agency | California, USA

Page Load Speed

42.6 sec in total

First Response

702 ms

Resources Loaded

38.7 sec

Page Rendered

3.2 sec

rich.agency screenshot

About Website

Click here to check amazing RiCH content for Russia. Otherwise, check out these important facts you probably never knew about rich.agency

Your Inbound Marketing is our vision, with an Account Based Marketing (ABM) Strategy as the route and Marketing Automation Platform (MAP) including, AI & BI platforms in our veins we generate engageme...

Visit rich.agency

Key Findings

We analyzed Rich.agency page load time and found that the first response time was 702 ms and then it took 41.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

rich.agency performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value3,040 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.043

99/100

15%

TTI (Time to Interactive)

Value24.0 s

1/100

10%

Network Requests Diagram

rich.agency

702 ms

normalize.css

964 ms

tipsy.css

347 ms

style.css

558 ms

jquery-1.9.0.min.js

904 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 68% of them (79 requests) were addressed to the original Rich.agency, 5% (6 requests) were made to Front.facetz.net and 4% (5 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (19.8 sec) belongs to the original domain Rich.agency.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (14%)

Content Size

8.6 MB

After Optimization

7.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rich.agency main page is 8.6 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. 45% of websites need less resources to load. Images take 8.4 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 45.8 kB

  • Original 51.9 kB
  • After minification 41.2 kB
  • After compression 6.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 10.7 kB, which is 21% 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 45.8 kB or 88% of the original size.

Image Optimization

-13%

Potential reduce by 1.1 MB

  • Original 8.4 MB
  • After minification 7.4 MB

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. Obviously, RiCH needs image optimization as it can save up to 1.1 MB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-42%

Potential reduce by 12.9 kB

  • Original 30.5 kB
  • After minification 30.5 kB
  • After compression 17.7 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 12.9 kB or 42% of the original size.

CSS Optimization

-91%

Potential reduce by 94.9 kB

  • Original 103.9 kB
  • After minification 72.9 kB
  • After compression 9.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. Rich.agency needs all CSS files to be minified and compressed as it can save up to 94.9 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (37%)

Requests Now

104

After Optimization

66

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rich.agency

rich.agency

702 ms

normalize.css

normalize.css

964 ms

tipsy.css

tipsy.css

347 ms

style.css

style.css

558 ms

jquery-1.9.0.min.js

jquery-1.9.0.min.js

904 ms

jquery.hasEventListener-1.0.5.min.js

jquery.hasEventListener-1.0.5.min.js

1083 ms

jquery.leanModal.js

jquery.leanModal.js

1117 ms

jquery.tipsy.js

jquery.tipsy.js

1287 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

1334 ms

jquery.visible.min.js

jquery.visible.min.js

1349 ms

PhoneFormat.js

PhoneFormat.js

3440 ms

jquery.nicescroll.js

jquery.nicescroll.js

1676 ms

jquery.waitforimages.min.js

jquery.waitforimages.min.js

1400 ms

main.js

main.js

1479 ms

utp.jpg

utp.jpg

5593 ms

stylesheet.css

stylesheet.css

1005 ms

pluso-like.js

pluso-like.js

1829 ms

empty.png

empty.png

220 ms

right_bottom.png

right_bottom.png

251 ms

left_top.png

left_top.png

252 ms

right_bottom.png

right_bottom.png

267 ms

left_top.png

left_top.png

412 ms

right_bottom.png

right_bottom.png

423 ms

left_top.png

left_top.png

430 ms

right_bottom.png

right_bottom.png

439 ms

left_top.png

left_top.png

614 ms

right_bottom.png

right_bottom.png

1422 ms

left_top.png

left_top.png

1462 ms

right_bottom.png

right_bottom.png

1082 ms

left_top.png

left_top.png

1341 ms

forty_header.png

forty_header.png

1776 ms

right_bottom.png

right_bottom.png

1484 ms

left_top.png

left_top.png

1583 ms

work_header.png

work_header.png

1815 ms

lato-light-webfont.woff

lato-light-webfont.woff

5641 ms

lato-thin-webfont.woff

lato-thin-webfont.woff

8751 ms

lato-semibold-webfont.woff

lato-semibold-webfont.woff

8710 ms

lato-bold-webfont.woff

lato-bold-webfont.woff

7104 ms

lato-heavy-webfont.woff

lato-heavy-webfont.woff

4625 ms

lato-regular-webfont.woff

lato-regular-webfont.woff

8527 ms

process

process

196 ms

process

process

899 ms

hit;PLUSO

hit;PLUSO

394 ms

header.jpg

header.jpg

14955 ms

topbar.png

topbar.png

6121 ms

logo.png

logo.png

6356 ms

1.png

1.png

6305 ms

main.jpg

main.jpg

19736 ms

main_answer.png

main_answer.png

6691 ms

kb.js

kb.js

1372 ms

collect_pluso.js

collect_pluso.js

417 ms

hit;PLUSO

hit;PLUSO

184 ms

crossd_pluso_iframe.html

crossd_pluso_iframe.html

321 ms

dct.js

dct.js

240 ms

h.gif

h.gif

190 ms

s.js

s.js

376 ms

3696d9c5412d7dbcbaf1f52aba44c40f

3696d9c5412d7dbcbaf1f52aba44c40f

141 ms

328 ms

sync.cgi

sync.cgi

328 ms

image

image

258 ms

pixel

pixel

119 ms

pixel

pixel

33 ms

collect

collect

105 ms

image

image

163 ms

pixel

pixel

38 ms

p.gif

p.gif

1403 ms

image

image

168 ms

collect

collect

136 ms

pixel

pixel

55 ms

289 ms

collect

collect

219 ms

dcamobile

dcamobile

335 ms

dcadsp

dcadsp

333 ms

dcadmp

dcadmp

333 ms

cm.gif

cm.gif

426 ms

collect

collect

114 ms

rHUky6FzRiWyFaZ6VydK0w

rHUky6FzRiWyFaZ6VydK0w

235 ms

1460145705441

1460145705441

358 ms

rHUky6FzRiWyFaZ6VydK0w

rHUky6FzRiWyFaZ6VydK0w

170 ms

watch.js

watch.js

1 ms

pixel

pixel

39 ms

why.jpg

why.jpg

5244 ms

1.png

1.png

192 ms

2.png

2.png

245 ms

cm.gif

cm.gif

221 ms

named.jpg

named.jpg

2243 ms

named_woman.png

named_woman.png

4831 ms

record.jpg

record.jpg

19780 ms

before.jpg

before.jpg

497 ms

before_woman.png

before_woman.png

6377 ms

before_calendar.png

before_calendar.png

1654 ms

forty.jpg

forty.jpg

7689 ms

2.png

2.png

160 ms

seven.jpg

seven.jpg

2060 ms

trust.jpg

trust.jpg

9173 ms

after_adaptive.png

after_adaptive.png

9370 ms

1.png

1.png

1283 ms

2.png

2.png

1476 ms

3.png

3.png

1638 ms

4.png

4.png

1797 ms

5.png

5.png

2762 ms

speed.jpg

speed.jpg

1089 ms

1.jpg

1.jpg

2449 ms

work_right_bottom.png

work_right_bottom.png

183 ms

work_left_top.png

work_left_top.png

191 ms

3.png

3.png

180 ms

2.jpg

2.jpg

3074 ms

3.jpg

3.jpg

3918 ms

4.jpg

4.jpg

1053 ms

5.jpg

5.jpg

1400 ms

6.jpg

6.jpg

1737 ms

7.jpg

7.jpg

2467 ms

8.jpg

8.jpg

4063 ms

9.jpg

9.jpg

4525 ms

10.jpg

10.jpg

4973 ms

11.jpg

11.jpg

6069 ms

Accessibility Review

rich.agency accessibility score

75

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Best Practices

rich.agency 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

High

Page has valid source maps

SEO Factors

rich.agency SEO score

77

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rich.agency can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Russian language. Our system also found out that Rich.agency 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

rich.agency

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