Tools & Wizards About Us
rinna.id screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

Page Load Speed

7.5 sec in total

First Response

716 ms

Resources Loaded

5.2 sec

Page Rendered

1.5 sec

rinna.id screenshot

About Website

Visit rinna.id now to see the best up-to-date Rinna content and also check out these interesting facts you probably never knew about rinna.id

Visit rinna.id

Key Findings

We analyzed Rinna.id page load time and found that the first response time was 716 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

rinna.id performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.4 s

1/100

10%

LCP (Largest Contentful Paint)

Value23.4 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value15.7 s

6/100

10%

Network Requests Diagram

rinna.co.jp

716 ms

js.cookie.min.js

68 ms

tpd6gyt.css

189 ms

animate.min.css

45 ms

slick.min.css

59 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Rinna.id, 5% (4 requests) were made to Cdnjs.cloudflare.com and 4% (3 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

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

Content Size

3.6 MB

After Optimization

3.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rinna.id main page is 3.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. 70% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 36.6 kB

  • Original 45.3 kB
  • After minification 36.7 kB
  • After compression 8.7 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 8.6 kB, which is 19% 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 36.6 kB or 81% of the original size.

Image Optimization

-6%

Potential reduce by 204.5 kB

  • Original 3.3 MB
  • After minification 3.1 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. Rinna images are well optimized though.

JavaScript Optimization

-47%

Potential reduce by 80.6 kB

  • Original 172.5 kB
  • After minification 136.1 kB
  • After compression 91.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 80.6 kB or 47% of the original size.

CSS Optimization

-10%

Potential reduce by 1.6 kB

  • Original 15.8 kB
  • After minification 15.8 kB
  • After compression 14.3 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. Rinna.id has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (40%)

Requests Now

78

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rinna. 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.

Network Requests Diagram

rinna.co.jp

rinna.co.jp

716 ms

js.cookie.min.js

js.cookie.min.js

68 ms

tpd6gyt.css

tpd6gyt.css

189 ms

animate.min.css

animate.min.css

45 ms

slick.min.css

slick.min.css

59 ms

style.css

style.css

348 ms

jquery.min.js

jquery.min.js

95 ms

wow.min.js

wow.min.js

52 ms

slick.js

slick.js

612 ms

paginathing.min.js

paginathing.min.js

612 ms

core.min.js

core.min.js

613 ms

home.js

home.js

612 ms

gtm.js

gtm.js

62 ms

logo_rinna_c.svg

logo_rinna_c.svg

540 ms

logo_rinna_w.svg

logo_rinna_w.svg

599 ms

nav_philosophy.png

nav_philosophy.png

620 ms

nav_company.png

nav_company.png

796 ms

nav_officersmessage.png

nav_officersmessage.png

796 ms

nav_rd.png

nav_rd.png

796 ms

nav_responsible-ai.png

nav_responsible-ai.png

1105 ms

icon_fb.svg

icon_fb.svg

764 ms

icon_in.svg

icon_in.svg

790 ms

247584019fd1f8a3c14ac9130ef37ca51dcc927c.jpg

247584019fd1f8a3c14ac9130ef37ca51dcc927c.jpg

1451 ms

sasara.png

sasara.png

1479 ms

service_slider02.png

service_slider02.png

1305 ms

service_slider03.png

service_slider03.png

1307 ms

service_slider04.png

service_slider04.png

1141 ms

service_slider05.png

service_slider05.png

1578 ms

service_slider06.png

service_slider06.png

1313 ms

service_slider07.png

service_slider07.png

1478 ms

service_logo01.png

service_logo01.png

1482 ms

service_logo03.png

service_logo03.png

1486 ms

service_logo04.png

service_logo04.png

1621 ms

service_logo05.png

service_logo05.png

1648 ms

service_logo06.png

service_logo06.png

1649 ms

service_logo07.png

service_logo07.png

1651 ms

api_img.svg

api_img.svg

1665 ms

ill_about01.svg

ill_about01.svg

1941 ms

ill_about02.svg

ill_about02.svg

2185 ms

ill_about03.svg

ill_about03.svg

2009 ms

ill_about04.svg

ill_about04.svg

2030 ms

chatbot.svg

chatbot.svg

2200 ms

js

js

57 ms

analytics.js

analytics.js

232 ms

lpl_1074.js

lpl_1074.js

936 ms

uh.js

uh.js

751 ms

bat.js

bat.js

27 ms

js

js

79 ms

ytag.js

ytag.js

780 ms

p.css

p.css

31 ms

css2

css2

147 ms

collect

collect

125 ms

site-catch.svg

site-catch.svg

1408 ms

bg_gradient.svg

bg_gradient.svg

1596 ms

kv_bg01.svg

kv_bg01.svg

1693 ms

kv_bg02.svg

kv_bg02.svg

1694 ms

kv_img01.png

kv_img01.png

2024 ms

kv_title_pc.svg

kv_title_pc.svg

1705 ms

kv_gradient.svg

kv_gradient.svg

1773 ms

collect

collect

57 ms

arrow_green.svg

arrow_green.svg

1777 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75vY0rw_mMI.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75vY0rw_mMI.ttf

1909 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75vY0rw_mMI.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75vY0rw_mMI.ttf

2845 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75vY0rw_mMI.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75vY0rw_mMI.ttf

2205 ms

d

d

12 ms

d

d

31 ms

icon_section_title.svg

icon_section_title.svg

1750 ms

service_bg_p.svg

service_bg_p.svg

1740 ms

service_bkg.png

service_bkg.png

1595 ms

icon_external.svg

icon_external.svg

1705 ms

api_bkg.png

api_bkg.png

1703 ms

about_bg_mono.svg

about_bg_mono.svg

1731 ms

about_bg_color.svg

about_bg_color.svg

1741 ms

40 ms

dot.svg

dot.svg

1450 ms

recruit_bg.svg

recruit_bg.svg

1520 ms

32 ms

recruit_bg_lead.svg

recruit_bg_lead.svg

1365 ms

recruit_img.svg

recruit_img.svg

1401 ms

contact_img.svg

contact_img.svg

1425 ms

icon_location_w.svg

icon_location_w.svg

1297 ms

icon_external_w.svg

icon_external_w.svg

1262 ms

ico_prev.png

ico_prev.png

1353 ms

ico_next.png

ico_next.png

1364 ms

Accessibility Review

rinna.id accessibility score

86

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

Best Practices

rinna.id 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

SEO Factors

rinna.id SEO score

89

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

    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 Rinna.id 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 Rinna.id 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

rinna.id

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