Tools & Wizards About Us
3636.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

3636.jp

激安コンタクトレンズ通販の価格比較といえば視力ポータル：みるみる.jp

Page Load Speed

5 sec in total

First Response

1000 ms

Resources Loaded

3.8 sec

Page Rendered

237 ms

3636.jp screenshot

About Website

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

コンタクトレンズ通販を価格比較！通信販売の使い捨てコンタクトが激安、乱視用コンタクトやカラーコンタクト通販の価格検索はここ。

Visit 3636.jp

Key Findings

We analyzed 3636.jp page load time and found that the first response time was 1000 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster. This domain responded with an error, which can significantly jeopardize 3636.jp rating and web reputation

Performance Metrics

3636.jp performance score

0

Network Requests Diagram

3636.jp

1000 ms

calendar.js

705 ms

calendar-en.js

387 ms

calendar-setup.js

408 ms

index.css

345 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 77% of them (43 requests) were addressed to the original 3636.jp, 11% (6 requests) were made to Medi-control.net and 5% (3 requests) were made to Optimizer.co.jp. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain 3636.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 173.9 kB (66%)

Content Size

265.2 kB

After Optimization

91.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 3636.jp main page is 265.2 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. 20% of websites need less resources to load. CSS take 91.0 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 38.7 kB

  • Original 47.7 kB
  • After minification 41.1 kB
  • After compression 9.0 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 6.6 kB, which is 14% 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 38.7 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 2.0 kB

  • Original 43.8 kB
  • After minification 41.8 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. 3636 images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 52.9 kB

  • Original 82.7 kB
  • After minification 59.4 kB
  • After compression 29.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 52.9 kB or 64% of the original size.

CSS Optimization

-88%

Potential reduce by 80.2 kB

  • Original 91.0 kB
  • After minification 67.7 kB
  • After compression 10.7 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. 3636.jp needs all CSS files to be minified and compressed as it can save up to 80.2 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (51%)

Requests Now

51

After Optimization

25

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

3636.jp

3636.jp

1000 ms

calendar.js

calendar.js

705 ms

calendar-en.js

calendar-en.js

387 ms

calendar-setup.js

calendar-setup.js

408 ms

index.css

index.css

345 ms

theme.css

theme.css

377 ms

scriptaculous.js

scriptaculous.js

574 ms

styles.css

styles.css

491 ms

mainer.css

mainer.css

546 ms

side.css

side.css

342 ms

ie6.css

ie6.css

359 ms

send.css

send.css

392 ms

favorite.gif

favorite.gif

906 ms

ybm16.gif

ybm16.gif

522 ms

clip_16_16_w.gif

clip_16_16_w.gif

678 ms

favorite_fox.gif

favorite_fox.gif

907 ms

hatena_entry.gif

hatena_entry.gif

907 ms

logo.gif

logo.gif

372 ms

logo_1192.gif

logo_1192.gif

674 ms

top_obj03.jpg

top_obj03.jpg

1075 ms

online_ttl.gif

online_ttl.gif

887 ms

calender.gif

calender.gif

828 ms

bg.gif

bg.gif

325 ms

head_bg.gif

head_bg.gif

341 ms

menu_1.gif

menu_1.gif

410 ms

menu_2.gif

menu_2.gif

584 ms

menu_3_1.gif

menu_3_1.gif

685 ms

rank_ubar_n.gif

rank_ubar_n.gif

698 ms

ar7.gif

ar7.gif

742 ms

search_bt.gif

search_bt.gif

740 ms

ranking_ttl.gif

ranking_ttl.gif

802 ms

no1.gif

no1.gif

969 ms

1.jpg

1.jpg

1038 ms

no2.gif

no2.gif

1036 ms

118.jpg

118.jpg

1075 ms

169.jpg

169.jpg

1105 ms

window_ttl.gif

window_ttl.gif

1169 ms

bar_top01.gif

bar_top01.gif

1299 ms

japan.gif

japan.gif

1391 ms

west.gif

west.gif

1412 ms

east.gif

east.gif

1427 ms

greeting.gif

greeting.gif

1509 ms

foot_logo.gif

foot_logo.gif

1510 ms

ajs.php

ajs.php

380 ms

dvd150x150.gif

dvd150x150.gif

408 ms

lg.php

lg.php

365 ms

cm_banner.gif

cm_banner.gif

1152 ms

wash_banner.gif

wash_banner.gif

1236 ms

sdmenu04.gif

sdmenu04.gif

1261 ms

rank_ubar_y.gif

rank_ubar_y.gif

1282 ms

sdmenu05.gif

sdmenu05.gif

1345 ms

ajs.php

ajs.php

396 ms

cc_468x60_4.gif

cc_468x60_4.gif

560 ms

lg.php

lg.php

196 ms

ga.js

ga.js

29 ms

__utm.gif

__utm.gif

12 ms

SEO Factors

3636.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

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

3636.jp

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