Report Summary

  • 84

    Performance

    Renders faster than
    88% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 0

    Best Practices

  • 69

    SEO

    Google-friendlier than
    28% of websites

richel.com

RICHEL Inc. Waterjet Consultants - Used Waterjets - Waterjet Training

Page Load Speed

458 ms in total

First Response

228 ms

Resources Loaded

229 ms

Page Rendered

1 ms

richel.com screenshot

About Website

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

Abrasive Waterjet Cutting Consultants. Jet Edge, Ingersoll Rand, Calypso, Flow International, Omax, DARDI, and other manufacturers. Abrasive recycling systems, waterjet accessories, and training. Rich...

Visit richel.com

Key Findings

We analyzed Richel.com page load time and found that the first response time was 228 ms and then it took 230 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

richel.com performance score

84

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.8 s

100/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value0.9 s

100/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.11

87/100

15%

TTI (Time to Interactive)

Value2.2 s

99/100

10%

Network Requests Diagram

richel.com

228 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Richel.com and no external sources were called. The less responsive or slowest element that took the longest time to load (228 ms) belongs to the original domain Richel.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 kB (1%)

Content Size

186.4 kB

After Optimization

184.4 kB

In fact, the total size of Richel.com main page is 186.4 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 166.4 kB which makes up the majority of the site volume.

HTML Optimization

-54%

Potential reduce by 767 B

  • Original 1.4 kB
  • After minification 1.4 kB
  • After compression 649 B

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 767 B or 54% of the original size.

Image Optimization

-0%

Potential reduce by 49 B

  • Original 166.4 kB
  • After minification 166.3 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. RICHEL images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.1 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

-80%

Potential reduce by 1.1 kB

  • Original 1.4 kB
  • After minification 1.3 kB
  • After compression 286 B

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. Richel.com needs all CSS files to be minified and compressed as it can save up to 1.1 kB or 80% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

richel.com accessibility score

60

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

richel.com SEO score

69

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Richel.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Richel.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 RICHEL. 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: