Tools & Wizards About Us
corich.co.jp screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

corich.co.jp

corich.co.jp

Page Load Speed

6.8 sec in total

First Response

531 ms

Resources Loaded

5.7 sec

Page Rendered

527 ms

corich.co.jp screenshot

About Website

Welcome to corich.co.jp homepage info - get ready to check Co Rich best content right away, or after learning these important things about corich.co.jp

こりっち(corich)株式会社は世界中の人々の笑顔と感動が溢れるwebサービスの提供を目指します。

Visit corich.co.jp

Key Findings

We analyzed Corich.co.jp page load time and found that the first response time was 531 ms and then it took 6.2 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

corich.co.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value9.6 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value910 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.16

73/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

corich.co.jp

531 ms

corich.co.jp

721 ms

js

72 ms

js

122 ms

bootstrap.css

355 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 76% of them (57 requests) were addressed to the original Corich.co.jp, 5% (4 requests) were made to Googletagmanager.com and 5% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Corich.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 306.8 kB (6%)

Content Size

5.3 MB

After Optimization

5.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Corich.co.jp main page is 5.3 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. 60% of websites need less resources to load. Images take 4.7 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 49.1 kB

  • Original 59.0 kB
  • After minification 45.1 kB
  • After compression 9.9 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 13.9 kB, which is 24% 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 49.1 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 93.9 kB

  • Original 4.7 MB
  • After minification 4.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. Co Rich images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 50.1 kB

  • Original 393.4 kB
  • After minification 392.5 kB
  • After compression 343.4 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 50.1 kB or 13% of the original size.

CSS Optimization

-64%

Potential reduce by 113.8 kB

  • Original 178.3 kB
  • After minification 178.1 kB
  • After compression 64.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. Corich.co.jp needs all CSS files to be minified and compressed as it can save up to 113.8 kB or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (49%)

Requests Now

65

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

corich.co.jp

corich.co.jp

531 ms

corich.co.jp

corich.co.jp

721 ms

js

js

72 ms

js

js

122 ms

bootstrap.css

bootstrap.css

355 ms

jquery.min.js

jquery.min.js

34 ms

bootstrap.min.js

bootstrap.min.js

535 ms

fakeLoader.min.js

fakeLoader.min.js

552 ms

offcanvas.js

offcanvas.js

553 ms

jquery.sticky.js

jquery.sticky.js

554 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

554 ms

isotope-org.js

isotope-org.js

560 ms

jquery.tile.js

jquery.tile.js

710 ms

wow.js

wow.js

728 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

730 ms

skippr.js

skippr.js

732 ms

t.min.js

t.min.js

731 ms

corich.js

corich.js

736 ms

api.js

api.js

43 ms

normalize.css

normalize.css

1318 ms

my-bootstrap.css

my-bootstrap.css

951 ms

fakeLoader.css

fakeLoader.css

906 ms

colorbox.css

colorbox.css

909 ms

bootstrap.offcanvas.min.css

bootstrap.offcanvas.min.css

950 ms

animate.css

animate.css

918 ms

skippr.css

skippr.css

1083 ms

css

css

41 ms

font-awesome.min.css

font-awesome.min.css

35 ms

style.min.css

style.min.css

1266 ms

styles.css

styles.css

1099 ms

css

css

57 ms

genericons.css

genericons.css

1127 ms

style.css

style.css

1128 ms

jquery.min.js

jquery.min.js

1475 ms

jquery-migrate.min.js

jquery-migrate.min.js

1280 ms

recaptcha__en.js

recaptcha__en.js

26 ms

analytics.js

analytics.js

26 ms

collect

collect

14 ms

js

js

36 ms

js

js

142 ms

main-logo03.png

main-logo03.png

203 ms

main-logo01.png

main-logo01.png

206 ms

main-logo02.png

main-logo02.png

203 ms

logo.png

logo.png

207 ms

white_wall_hash.png

white_wall_hash.png

554 ms

dotted02.png

dotted02.png

205 ms

stage_02.png

stage_02.png

1608 ms

twitter-700x480.png

twitter-700x480.png

1080 ms

avex.png

avex.png

1148 ms

parallax01_03.jpg

parallax01_03.jpg

1270 ms

ico_01.png

ico_01.png

399 ms

ico_02.png

ico_02.png

583 ms

ico_03.png

ico_03.png

731 ms

stage1.png

stage1.png

1666 ms

stdio_flocke-1024x998.jpg

stdio_flocke-1024x998.jpg

1085 ms

ours.png

ours.png

1447 ms

avex.jpg

avex.jpg

1617 ms

sakkuto.jpg

sakkuto.jpg

1327 ms

%E4%B8%89%E8%8F%B1.jpg

%E4%B8%89%E8%8F%B1.jpg

1805 ms

studio.jpg

studio.jpg

1686 ms

share_01.jpg

share_01.jpg

1631 ms

%E3%82%B7%E3%82%B9%E3%83%88%E3%83%AC.jpg

%E3%82%B7%E3%82%B9%E3%83%88%E3%83%AC.jpg

2839 ms

SR.jpg

SR.jpg

1802 ms

ico_04.png

ico_04.png

1807 ms

ico_05.png

ico_05.png

1847 ms

ico_06.png

ico_06.png

1863 ms

concept_bg01.png

concept_bg01.png

1980 ms

concept_bg02.png

concept_bg02.png

1983 ms

parallax02_02.jpg

parallax02_02.jpg

1989 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

72 ms

S6u9w4BMUTPHh6UVSwaPHA.ttf

S6u9w4BMUTPHh6UVSwaPHA.ttf

89 ms

S6uyw4BMUTPHjxAwWw.ttf

S6uyw4BMUTPHjxAwWw.ttf

101 ms

S6u9w4BMUTPHh7USSwaPHA.ttf

S6u9w4BMUTPHh7USSwaPHA.ttf

102 ms

S6u8w4BMUTPHh30AUi-v.ttf

S6u8w4BMUTPHh30AUi-v.ttf

101 ms

collect

collect

24 ms

Accessibility Review

corich.co.jp accessibility score

87

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.

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

corich.co.jp 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

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

corich.co.jp 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

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Corich.co.jp 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 Corich.co.jp 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

corich.co.jp

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