Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

richerlink.com

RicherLink | GPON EPON ONU OLT Manufacturers,EoC Master Slave

Page Load Speed

26.9 sec in total

First Response

661 ms

Resources Loaded

25.6 sec

Page Rendered

678 ms

richerlink.com screenshot

About Website

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

RicherLink is China's leading provider of FTTH and cable network equipment,products including GPON EPON ONU OLT,EOC Master and EOC Slave.

Visit richerlink.com

Key Findings

We analyzed Richerlink.com page load time and found that the first response time was 661 ms and then it took 26.3 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

richerlink.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

13/100

10%

LCP (Largest Contentful Paint)

Value17.3 s

0/100

25%

SI (Speed Index)

Value17.0 s

0/100

10%

TBT (Total Blocking Time)

Value1,080 ms

24/100

30%

CLS (Cumulative Layout Shift)

Value0.602

10/100

15%

TTI (Time to Interactive)

Value25.4 s

0/100

10%

Network Requests Diagram

richerlink.com

661 ms

richerlink.com

1258 ms

bootstrap.min.css

1340 ms

index.css

1353 ms

page.css

1139 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 81% of them (72 requests) were addressed to the original Richerlink.com, 7% (6 requests) were made to Youtube.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain Richerlink.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 378.9 kB (20%)

Content Size

1.9 MB

After Optimization

1.5 MB

In fact, the total size of Richerlink.com main page is 1.9 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. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 96.5 kB

  • Original 129.3 kB
  • After minification 117.9 kB
  • After compression 32.8 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 96.5 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 29.3 kB

  • Original 1.0 MB
  • After minification 1.0 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. Richer Link images are well optimized though.

JavaScript Optimization

-41%

Potential reduce by 250.8 kB

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

CSS Optimization

-2%

Potential reduce by 2.3 kB

  • Original 111.7 kB
  • After minification 111.7 kB
  • After compression 109.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. Richerlink.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (24%)

Requests Now

83

After Optimization

63

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

Accessibility Review

richerlink.com accessibility score

79

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

richerlink.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

richerlink.com SEO score

85

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

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

Open Graph description is not detected on the main page of Richer Link. 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: