Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

irri.us

Refrigeration Solution - Interstate Refrigerant Recovery Inc

Page Load Speed

1.1 sec in total

First Response

75 ms

Resources Loaded

702 ms

Page Rendered

273 ms

About Website

Visit irri.us now to see the best up-to-date Irri content and also check out these interesting facts you probably never knew about irri.us

Interstate Refrigerant Recovery Inc specializes in on-site refrigerant recovery for commercial refrigeration. Contact us today.

Visit irri.us

Key Findings

We analyzed Irri.us page load time and found that the first response time was 75 ms and then it took 975 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

irri.us performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

33/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value2.6 s

98/100

10%

Network Requests Diagram

interstaterefrigerantrecovery.com

75 ms

style.min.css

18 ms

all.min.css

25 ms

9-layout.css

92 ms

style.min.css

33 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Irri.us, 6% (5 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Nebula.wsimg.com. The less responsive or slowest element that took the longest time to load (314 ms) relates to the external source Interstaterefrigerantrecovery.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 80.2 kB (9%)

Content Size

878.3 kB

After Optimization

798.0 kB

In fact, the total size of Irri.us main page is 878.3 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. 65% of websites need less resources to load. Javascripts take 746.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 78.4 kB

  • Original 97.9 kB
  • After minification 96.2 kB
  • After compression 19.5 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 78.4 kB or 80% of the original size.

Image Optimization

-44%

Potential reduce by 1.2 kB

  • Original 2.7 kB
  • After minification 1.5 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. Obviously, Irri needs image optimization as it can save up to 1.2 kB or 44% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 516 B

  • Original 746.9 kB
  • After minification 746.9 kB
  • After compression 746.3 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

-0%

Potential reduce by 123 B

  • Original 30.8 kB
  • After minification 30.8 kB
  • After compression 30.7 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. Irri.us has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 67 (92%)

Requests Now

73

After Optimization

6

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

Accessibility Review

irri.us accessibility score

100

Accessibility Issues

Best Practices

irri.us best practices score

92

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

Page has valid source maps

SEO Factors

irri.us SEO score

97

Search Engine Optimization Advices

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 Irri.us 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 Irri.us 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 data is detected on the main page of Irri. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: