Tools & Wizards About Us

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

rinavis.com

宅配クリーニングならリナビス【公式】｜おせっかいな宅配クリーニング

Page Load Speed

15.1 sec in total

First Response

361 ms

Resources Loaded

12.2 sec

Page Rendered

2.5 sec

About Website

Click here to check amazing Rinavis content for Japan. Otherwise, check out these important facts you probably never knew about rinavis.com

宅配クリーニングのリナビスは次回利用意向度97％以上のサービスです。送料無料・保管無料・シミ抜き無料を含む6つのサービスが無料で、創業から60年の歴史と、熟練職人（田舎のおせっかいなおっちゃんおばちゃん）が生み出す高品質な宅配クリーニングサービス。リナビスは株式会社リナビスが運営する宅配クリーニングサービス。

Visit rinavis.com

Key Findings

We analyzed Rinavis.com page load time and found that the first response time was 361 ms and then it took 14.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

rinavis.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value13.6 s

2/100

10%

TBT (Total Blocking Time)

Value7,770 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.102

89/100

15%

TTI (Time to Interactive)

Value31.6 s

0/100

10%

Network Requests Diagram

rinavis.com

361 ms

rinavis.com

1011 ms

fs_style.css

1473 ms

fs_original.css

2182 ms

webstore-vg.js

371 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 12% of them (13 requests) were addressed to the original Rinavis.com, 76% (84 requests) were made to Cleaners.itembox.design and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source Cleaners.itembox.design.

Page Optimization Overview & Recommendations

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

Content Size

5.0 MB

After Optimization

3.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rinavis.com main page is 5.0 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. Only a small number of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 178.6 kB

  • Original 204.7 kB
  • After minification 145.2 kB
  • After compression 26.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 59.5 kB, which is 29% 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 178.6 kB or 87% of the original size.

Image Optimization

-22%

Potential reduce by 982.0 kB

  • Original 4.5 MB
  • After minification 3.6 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, Rinavis needs image optimization as it can save up to 982.0 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-17%

Potential reduce by 36.9 kB

  • Original 223.5 kB
  • After minification 223.3 kB
  • After compression 186.6 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 36.9 kB or 17% of the original size.

CSS Optimization

-9%

Potential reduce by 4.6 kB

  • Original 51.1 kB
  • After minification 51.0 kB
  • After compression 46.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. Rinavis.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (33%)

Requests Now

105

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

rinavis.com accessibility score

71

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

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

rinavis.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

rinavis.com SEO score

92

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

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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rinavis.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Rinavis.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 data is detected on the main page of Rinavis. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: