Tools & Wizards About Us
eyeland.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

eyeland.co.jp

コンタクトレンズの通販なら【eyeland】 -メニコンプレミオをはじめ格安コンタクトの通販ショップ-

Page Load Speed

9.6 sec in total

First Response

634 ms

Resources Loaded

8.6 sec

Page Rendered

383 ms

eyeland.co.jp screenshot

About Website

Visit eyeland.co.jp now to see the best up-to-date Eyeland content and also check out these interesting facts you probably never knew about eyeland.co.jp

コンタクトの通販ならeyeland（アイランド）へお任せください。当店では、メニコンプレミオをはじめ人気の格安コンタクトレンズやカラーコンタクトを安心の国内発送でお届けする通販ショップです。

Visit eyeland.co.jp

Key Findings

We analyzed Eyeland.co.jp page load time and found that the first response time was 634 ms and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

eyeland.co.jp performance score

0

Network Requests Diagram

eyeland.co.jp

634 ms

m_sys_common.css

312 ms

import.css

308 ms

script.js

328 ms

jquery.min.js

501 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 78% of them (101 requests) were addressed to the original Eyeland.co.jp, 2% (3 requests) were made to Sync.fout.jp and 2% (2 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Eyeland.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 252.1 kB (14%)

Content Size

1.9 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 74.2 kB

  • Original 88.0 kB
  • After minification 79.3 kB
  • After compression 13.8 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 74.2 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 11.9 kB

  • Original 1.5 MB
  • After minification 1.5 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. Eyeland images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 139.9 kB

  • Original 232.7 kB
  • After minification 230.6 kB
  • After compression 92.8 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 139.9 kB or 60% of the original size.

CSS Optimization

-80%

Potential reduce by 26.2 kB

  • Original 32.8 kB
  • After minification 26.6 kB
  • After compression 6.6 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. Eyeland.co.jp needs all CSS files to be minified and compressed as it can save up to 26.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (45%)

Requests Now

127

After Optimization

70

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eyeland.co.jp

eyeland.co.jp

634 ms

m_sys_common.css

m_sys_common.css

312 ms

import.css

import.css

308 ms

script.js

script.js

328 ms

jquery.min.js

jquery.min.js

501 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

339 ms

jquery.bxslider.css

jquery.bxslider.css

361 ms

check_history.css

check_history.css

310 ms

pager.css

pager.css

311 ms

shopdetail.css

shopdetail.css

328 ms

ranking.css

ranking.css

382 ms

basket.css

basket.css

408 ms

security.css

security.css

552 ms

category_menu.css

category_menu.css

620 ms

topicpath.css

topicpath.css

671 ms

catalog.css

catalog.css

660 ms

npab_405x66.gif

npab_405x66.gif

760 ms

sp.gif

sp.gif

695 ms

count3.makeshop.jp

count3.makeshop.jp

702 ms

header_2.gif

header_2.gif

333 ms

header_0.jpg

header_0.jpg

660 ms

header_1a.gif

header_1a.gif

333 ms

header_1b.gif

header_1b.gif

337 ms

header_1c.gif

header_1c.gif

335 ms

header_1d.gif

header_1d.gif

338 ms

header_1e.gif

header_1e.gif

657 ms

header_1f.gif

header_1f.gif

652 ms

header_1g.gif

header_1g.gif

667 ms

header_1h.gif

header_1h.gif

678 ms

header_1i.gif

header_1i.gif

692 ms

kind_1day.gif

kind_1day.gif

957 ms

kind_2week.gif

kind_2week.gif

989 ms

1month.jpg

1month.jpg

1003 ms

kind_ranshi.gif

kind_ranshi.gif

1014 ms

kind_enkin.gif

kind_enkin.gif

1007 ms

kind_color.gif

kind_color.gif

1021 ms

recommendtitlebar.gif

recommendtitlebar.gif

1328 ms

slide1.jpg

slide1.jpg

1655 ms

slide2.jpg

slide2.jpg

1670 ms

slide3.jpg

slide3.jpg

1677 ms

slide4.jpg

slide4.jpg

1657 ms

slide5.jpg

slide5.jpg

1720 ms

slide6.jpg

slide6.jpg

1936 ms

slide7.jpg

slide7.jpg

2333 ms

slide8.jpg

slide8.jpg

2356 ms

slide9.jpg

slide9.jpg

2335 ms

login_1.gif

login_1.gif

2027 ms

sarch.gif

sarch.gif

2083 ms

dispolens.gif

dispolens.gif

2295 ms

leftmenu_1day.gif

leftmenu_1day.gif

2339 ms

leftmenu_2week.gif

leftmenu_2week.gif

2439 ms

leftmenu_1month.gif

leftmenu_1month.gif

2659 ms

dispolens-T.gif

dispolens-T.gif

2641 ms

leftmenu_1dayT.gif

leftmenu_1dayT.gif

2657 ms

leftmenu_2weekT.gif

leftmenu_2weekT.gif

2637 ms

is_show_gmo_header.html

is_show_gmo_header.html

879 ms

aq_tag_aos.js

aq_tag_aos.js

148 ms

394 ms

total.html

total.html

518 ms

ga.js

ga.js

7 ms

__utm.gif

__utm.gif

13 ms

EM34BYVZ46DUGEQNJE6A

EM34BYVZ46DUGEQNJE6A

128 ms

dispolens-B.gif

dispolens-B.gif

2371 ms

leftmenu_1dayB.gif

leftmenu_1dayB.gif

2474 ms

leftmenu_2weekB.gif

leftmenu_2weekB.gif

2645 ms

leftmenu_1monthB.gif

leftmenu_1monthB.gif

2638 ms

hard.gif

hard.gif

2643 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

866 ms

gmsync

gmsync

298 ms

segmentation.js

segmentation.js

8 ms

320 ms

cnt

cnt

352 ms

soft.gif

soft.gif

2364 ms

colorcontact.gif

colorcontact.gif

2372 ms

inforbar.jpg

inforbar.jpg

2454 ms

left_edge.gif

left_edge.gif

2617 ms

right_edge.gif

right_edge.gif

2634 ms

005001000001.jpg

005001000001.jpg

2942 ms

004005000002.jpg

004005000002.jpg

2970 ms

014002000004.jpg

014002000004.jpg

2872 ms

003003000001.jpg

003003000001.jpg

2776 ms

0030050000032.jpg

0030050000032.jpg

2809 ms

0000000003383.jpg

0000000003383.jpg

2998 ms

mk_main_p_line.gif

mk_main_p_line.gif

2941 ms

0000000003423.jpg

0000000003423.jpg

3213 ms

0000000003463.jpg

0000000003463.jpg

2991 ms

0000000003303.jpg

0000000003303.jpg

3043 ms

0000000003343.jpg

0000000003343.jpg

3080 ms

0030060000013.jpg

0030060000013.jpg

2641 ms

icon13.gif

icon13.gif

2910 ms

0030050000043.jpg

0030050000043.jpg

2940 ms

icon11.gif

icon11.gif

2948 ms

icon14.gif

icon14.gif

2881 ms

0030020000023.jpg

0030020000023.jpg

2761 ms

icon12.gif

icon12.gif

2739 ms

0040030000023.jpg

0040030000023.jpg

2868 ms

0040030000043.jpg

0040030000043.jpg

2949 ms

icon15.gif

icon15.gif

2959 ms

0040010000023.jpg

0040010000023.jpg

2869 ms

iconQ.gif

iconQ.gif

2735 ms

0050020000013.jpg

0050020000013.jpg

2754 ms

0040040000013.jpg

0040040000013.jpg

2861 ms

0150020000023.jpg

0150020000023.jpg

2949 ms

0030050000033.jpg

0030050000033.jpg

2924 ms

0030030000013.jpg

0030030000013.jpg

2845 ms

0040050000023.jpg

0040050000023.jpg

2738 ms

0140020000043.jpg

0140020000043.jpg

2771 ms

ranking_b.gif

ranking_b.gif

2898 ms

ranking_1.gif

ranking_1.gif

2916 ms

ranking_2.gif

ranking_2.gif

2966 ms

ranking_3.gif

ranking_3.gif

2896 ms

ranking_4.gif

ranking_4.gif

2807 ms

ranking_5.gif

ranking_5.gif

2768 ms

ranking_0.gif

ranking_0.gif

2594 ms

ttl_01.jpg

ttl_01.jpg

2485 ms

beacon.html

beacon.html

52 ms

bx_loader.gif

bx_loader.gif

168 ms

pixel

pixel

22 ms

cs

cs

310 ms

setuid

setuid

19 ms

Pug

Pug

22 ms

set

set

310 ms

tap.php

tap.php

6 ms

sync

sync

9 ms

pixel

pixel

14 ms

sync

sync

358 ms

sd

sd

25 ms

sync

sync

281 ms

mapuser

mapuser

149 ms

sync

sync

294 ms

SEO Factors

eyeland.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eyeland.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 Eyeland.co.jp main page’s claimed encoding is euc-jp. 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

eyeland.co.jp

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