Tools & Wizards About Us
kori.to screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

kori.to

【首の痛み専門整体】東京・渋谷のかたこり整体院 代々木上原駅徒歩3分 頭痛、寝違え、むち打ち、目の痛み

Page Load Speed

6 sec in total

First Response

586 ms

Resources Loaded

4.7 sec

Page Rendered

649 ms

kori.to screenshot

About Website

Welcome to kori.to homepage info - get ready to check Kori best content for Japan right away, or after learning these important things about kori.to

頭痛、寝違え、むち打ち、目の痛み、首の痛み全般、肩こりが得意。24時間ネットで楽々予約。15年で施術実績4万件超。１人治療院で完全個室。代々木上原駅から徒歩3分。地方からも多くご来院。【口コミ122件】地域No1の掲載数。痛み・コリを取るだけではなく『生活が楽になる整体院』です。

Visit kori.to

Key Findings

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

Performance Metrics

kori.to performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value7.0 s

33/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

kori.to

586 ms

kori.to

703 ms

style.css

180 ms

kata.js

355 ms

jquery-1.11.0.min.js

52 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 83% of them (69 requests) were addressed to the original Kori.to, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Kori.to.

Page Optimization Overview & Recommendations

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

Content Size

751.0 kB

After Optimization

706.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kori.to main page is 751.0 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. 30% of websites need less resources to load. Images take 599.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 39.3 kB

  • Original 52.5 kB
  • After minification 48.8 kB
  • After compression 13.2 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 39.3 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 43 B

  • Original 599.6 kB
  • After minification 599.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. Kori images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 313 B

  • Original 68.5 kB
  • After minification 68.5 kB
  • After compression 68.2 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

-17%

Potential reduce by 5.3 kB

  • Original 30.4 kB
  • After minification 30.3 kB
  • After compression 25.1 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. Kori.to needs all CSS files to be minified and compressed as it can save up to 5.3 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (38%)

Requests Now

77

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kori. 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

kori.to

kori.to

586 ms

kori.to

kori.to

703 ms

style.css

style.css

180 ms

kata.js

kata.js

355 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

52 ms

analytics.js

analytics.js

52 ms

colorbox.css

colorbox.css

532 ms

style.min.css

style.min.css

690 ms

screen.min.css

screen.min.css

694 ms

pagenavi-css.css

pagenavi-css.css

694 ms

jquery.min.js

jquery.min.js

863 ms

jquery-migrate.min.js

jquery-migrate.min.js

701 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

708 ms

jquery-colorbox-wrapper-min.js

jquery-colorbox-wrapper-min.js

860 ms

html5.js

html5.js

149 ms

css3-mediaqueries.js

css3-mediaqueries.js

147 ms

style_ie.css

style_ie.css

860 ms

mrliteLogger.js

mrliteLogger.js

1723 ms

519 ms

conversion.js

conversion.js

133 ms

front.min.js

front.min.js

894 ms

bj-lazy-load.min.js

bj-lazy-load.min.js

894 ms

script.js

script.js

1027 ms

wp-embed.min.js

wp-embed.min.js

1030 ms

sdk.js

sdk.js

37 ms

collect

collect

14 ms

sdk.js

sdk.js

8 ms

collect

collect

57 ms

js

js

88 ms

90 ms

style.css

style.css

184 ms

cal.cgi

cal.cgi

247 ms

rogo2017.png

rogo2017.png

178 ms

top2012_off.gif

top2012_off.gif

314 ms

menu001_off.gif

menu001_off.gif

315 ms

menu002_off.gif

menu002_off.gif

385 ms

menu003_off.gif

menu003_off.gif

354 ms

menu004_off.gif

menu004_off.gif

410 ms

menu005_off.gif

menu005_off.gif

484 ms

menu006_off.gif

menu006_off.gif

486 ms

menu-top2016.png

menu-top2016.png

719 ms

topm2013-1.gif

topm2013-1.gif

556 ms

card2018.png

card2018.png

760 ms

LINE.png

LINE.png

653 ms

side_menu17-01.png

side_menu17-01.png

656 ms

side_menu17-02.png

side_menu17-02.png

732 ms

side_menu17-03.png

side_menu17-03.png

992 ms

side_menu17-04.png

side_menu17-04.png

996 ms

side_menu17-05.png

side_menu17-05.png

897 ms

cnt.cgi

cnt.cgi

957 ms

cnt.cgi

cnt.cgi

1004 ms

cnt.cgi

cnt.cgi

1126 ms

cnt.cgi

cnt.cgi

1183 ms

no.gif

no.gif

1163 ms

side_menu17-06.png

side_menu17-06.png

1167 ms

side_menu17-07.png

side_menu17-07.png

1181 ms

side_menu17-08.png

side_menu17-08.png

1302 ms

s_seitai-001.jpg

s_seitai-001.jpg

1336 ms

s_seitai-002.jpg

s_seitai-002.jpg

1342 ms

s_seitai-003.jpg

s_seitai-003.jpg

1358 ms

s_seitai-006.jpg

s_seitai-006.jpg

1354 ms

s_seitai-008.jpg

s_seitai-008.jpg

1511 ms

s_seitai-010.jpg

s_seitai-010.jpg

1661 ms

s_seitai-011.jpg

s_seitai-011.jpg

1376 ms

side_menu02.gif

side_menu02.gif

1377 ms

footer01.gif

footer01.gif

1346 ms

style.css

style.css

1298 ms

footer02.gif

footer02.gif

1443 ms

btn_pagetop.png

btn_pagetop.png

1381 ms

titlebar.gif

titlebar.gif

1379 ms

sidebar.gif

sidebar.gif

1357 ms

side_menu_bg_hover.gif

side_menu_bg_hover.gif

1334 ms

s_footer1.png

s_footer1.png

1433 ms

s_footer2.png

s_footer2.png

1376 ms

s_footer3.png

s_footer3.png

1378 ms

sp_menu3.png

sp_menu3.png

1312 ms

sp_menu4.png

sp_menu4.png

1233 ms

sp_menu.png

sp_menu.png

1244 ms

42 ms

sp_menu_close.png

sp_menu_close.png

1181 ms

overlay.png

overlay.png

1186 ms

26 ms

topm2016.png

topm2016.png

516 ms

Accessibility Review

kori.to accessibility score

66

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.

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

kori.to best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

kori.to 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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kori.to can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Kori.to 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

kori.to

Open Graph description is not detected on the main page of Kori. 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: