Tools & Wizards About Us
tokyo-lasik-center.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tokyo-lasik-center.com

Page Load Speed

6.7 sec in total

First Response

540 ms

Resources Loaded

5.8 sec

Page Rendered

349 ms

tokyo-lasik-center.com screenshot

About Website

Click here to check amazing Tokyo Lasik Center content. Otherwise, check out these important facts you probably never knew about tokyo-lasik-center.com

レーシック（LASIK）、レーシック手術は吉野眼科レーシックセンターは、最先端の近視乱視矯正手術レーシック、フェイキックIOLを眼科専門医が安全性と確実性を最優先にして行う眼科施設です。レーシック、レーシック手術は吉野眼科レーシックセンター。

Visit tokyo-lasik-center.com

Key Findings

We analyzed Tokyo-lasik-center.com page load time and found that the first response time was 540 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

tokyo-lasik-center.com performance score

0

Network Requests Diagram

tokyo-lasik-center.com

540 ms

www.tokyo-lasik-center.com

957 ms

jquery.min.js

32 ms

rollover.js

335 ms

smoothScroll.js

512 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 82% of them (84 requests) were addressed to the original Tokyo-lasik-center.com, 10% (10 requests) were made to Static.xx.fbcdn.net and 6% (6 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Tokyo-lasik-center.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 79.8 kB (8%)

Content Size

1.1 MB

After Optimization

979.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-71%

Potential reduce by 15.5 kB

  • Original 21.8 kB
  • After minification 20.4 kB
  • After compression 6.3 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 15.5 kB or 71% of the original size.

Image Optimization

-2%

Potential reduce by 19.7 kB

  • Original 978.0 kB
  • After minification 958.3 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. Tokyo Lasik Center images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 26.9 kB

  • Original 37.8 kB
  • After minification 32.7 kB
  • After compression 10.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 26.9 kB or 71% of the original size.

CSS Optimization

-80%

Potential reduce by 17.6 kB

  • Original 22.2 kB
  • After minification 16.7 kB
  • After compression 4.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. Tokyo-lasik-center.com needs all CSS files to be minified and compressed as it can save up to 17.6 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

100

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

tokyo-lasik-center.com

tokyo-lasik-center.com

540 ms

www.tokyo-lasik-center.com

www.tokyo-lasik-center.com

957 ms

jquery.min.js

jquery.min.js

32 ms

rollover.js

rollover.js

335 ms

smoothScroll.js

smoothScroll.js

512 ms

common.js

common.js

336 ms

jquery.cookie.js

jquery.cookie.js

354 ms

fontSize.js

fontSize.js

543 ms

jquery.cycle.all.min.js

jquery.cycle.all.min.js

1046 ms

import.css

import.css

512 ms

top.css

top.css

537 ms

title.js

title.js

544 ms

href.js

href.js

674 ms

jquery.tinyscrollbar.min.js

jquery.tinyscrollbar.min.js

842 ms

reset.css

reset.css

177 ms

clear.css

clear.css

178 ms

marginpadding.css

marginpadding.css

178 ms

base.css

base.css

339 ms

ic_arrow.gif

ic_arrow.gif

235 ms

bg_txt_change.gif

bg_txt_change.gif

236 ms

btn_txt_change.gif

btn_txt_change.gif

252 ms

hdr_logo.gif

hdr_logo.gif

232 ms

hdr_tel.gif

hdr_tel.gif

334 ms

bg_main.jpg

bg_main.jpg

249 ms

main.jpg

main.jpg

1329 ms

main2.jpg

main2.jpg

1118 ms

main3.jpg

main3.jpg

1396 ms

main4.jpg

main4.jpg

1497 ms

bg_nav.jpg

bg_nav.jpg

347 ms

nav_01.jpg

nav_01.jpg

491 ms

nav_02_off.jpg

nav_02_off.jpg

698 ms

nav_03_off.jpg

nav_03_off.jpg

829 ms

nav_04_off.jpg

nav_04_off.jpg

875 ms

nav_05_off.jpg

nav_05_off.jpg

1007 ms

nav_06_off.jpg

nav_06_off.jpg

1051 ms

side_nav01_01_off.jpg

side_nav01_01_off.jpg

1333 ms

side_nav01_02_off.jpg

side_nav01_02_off.jpg

1393 ms

side_nav01_03_off.jpg

side_nav01_03_off.jpg

1295 ms

side_nav01_04_off.jpg

side_nav01_04_off.jpg

1470 ms

side_nav01_05_off.gif

side_nav01_05_off.gif

1483 ms

side_nav01_06_off.gif

side_nav01_06_off.gif

1492 ms

side_nav01_07_off.gif

side_nav01_07_off.gif

1559 ms

bg_sidebox01.gif

bg_sidebox01.gif

1568 ms

btn_side01_off.gif

btn_side01_off.gif

1647 ms

btn_side02_off.gif

btn_side02_off.gif

1649 ms

safety-lasik_off.jpg

safety-lasik_off.jpg

1652 ms

bg_infobox.gif

bg_infobox.gif

1655 ms

tit_info.gif

tit_info.gif

1733 ms

bg-scrollbar-thumb-y.png

bg-scrollbar-thumb-y.png

1742 ms

bg-scrollbar-trackend-y.png

bg-scrollbar-trackend-y.png

1822 ms

txt_01.gif

txt_01.gif

1816 ms

img_01.jpg

img_01.jpg

1818 ms

img_03.gif

img_03.gif

1822 ms

letters_off.jpg

letters_off.jpg

2063 ms

txt_02.gif

txt_02.gif

1710 ms

img_04.jpg

img_04.jpg

1775 ms

txt_03_off.gif

txt_03_off.gif

1766 ms

hatena_01_off.gif

hatena_01_off.gif

1776 ms

likebox.php

likebox.php

222 ms

hatena_02_off.gif

hatena_02_off.gif

1767 ms

img_05.jpg

img_05.jpg

2157 ms

side_nav02_tit.jpg

side_nav02_tit.jpg

1825 ms

hDvwL1_H7g-.css

hDvwL1_H7g-.css

302 ms

56WNbrUYLbL.css

56WNbrUYLbL.css

373 ms

1kPfZUdGrka.js

1kPfZUdGrka.js

509 ms

Yuj_Y8xNH2C.js

Yuj_Y8xNH2C.js

704 ms

Mpe38fuBVZ2.js

Mpe38fuBVZ2.js

507 ms

n8qIhCw3vMx.js

n8qIhCw3vMx.js

507 ms

side_nav02_01_off.gif

side_nav02_01_off.gif

1684 ms

side_nav02_02_off.gif

side_nav02_02_off.gif

1479 ms

side_nav02_03_off.gif

side_nav02_03_off.gif

1364 ms

side_nav02_04_off.gif

side_nav02_04_off.gif

1417 ms

side_nav02_05_off.gif

side_nav02_05_off.gif

1338 ms

side_nav02_06_off.gif

side_nav02_06_off.gif

1320 ms

side_nav02_07_off.gif

side_nav02_07_off.gif

1256 ms

529009_370842632936228_865516050_n.jpg

529009_370842632936228_865516050_n.jpg

497 ms

523398_610741235613032_522192602_n.png

523398_610741235613032_522192602_n.png

894 ms

1514592_812801752128696_4034716623580103703_n.jpg

1514592_812801752128696_4034716623580103703_n.jpg

696 ms

227114_1233484430000709_8170494197186478640_n.jpg

227114_1233484430000709_8170494197186478640_n.jpg

755 ms

556526_184288798372470_1178909262_n.jpg

556526_184288798372470_1178909262_n.jpg

770 ms

11937_259265484213626_18351004_n.jpg

11937_259265484213626_18351004_n.jpg

779 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

108 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

106 ms

btn_sidemail.jpg

btn_sidemail.jpg

1261 ms

tit_side_taiken.gif

tit_side_taiken.gif

1152 ms

img_side_taiken.jpg

img_side_taiken.jpg

1195 ms

tit_side_guide.gif

tit_side_guide.gif

1153 ms

img_side_guide.jpg

img_side_guide.jpg

1143 ms

btn_side_guide_off.jpg

btn_side_guide_off.jpg

1185 ms

ic_arrow_info.gif

ic_arrow_info.gif

1177 ms

bg_subbox.gif

bg_subbox.gif

1208 ms

img_02.jpg

img_02.jpg

1730 ms

bg_sidebox02.gif

bg_sidebox02.gif

1143 ms

bg_footer.jpg

bg_footer.jpg

1177 ms

bg_ftrinner.gif

bg_ftrinner.gif

1182 ms

ic_arrow_ftr01.gif

ic_arrow_ftr01.gif

1189 ms

ic_arrow_ftr02.gif

ic_arrow_ftr02.gif

1216 ms

ic_arrow_ftr03.gif

ic_arrow_ftr03.gif

1225 ms

bg_sidebox01_top.gif

bg_sidebox01_top.gif

1196 ms

bg_sidebox01_btm.gif

bg_sidebox01_btm.gif

1290 ms

VXcANLwwL5J.js

VXcANLwwL5J.js

72 ms

AmlxWlqMvlv.js

AmlxWlqMvlv.js

149 ms

SEO Factors

tokyo-lasik-center.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokyo-lasik-center.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Tokyo-lasik-center.com main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

tokyo-lasik-center.com

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