Tools & Wizards About Us
cocotte.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

cocotte.jp

ロリポップ！レンタルサーバー | 利用実績170万人突破！無料SSLあり

Page Load Speed

10.7 sec in total

First Response

997 ms

Resources Loaded

9.4 sec

Page Rendered

354 ms

cocotte.jp screenshot

About Website

Click here to check amazing Cocotte content for Japan. Otherwise, check out these important facts you probably never knew about cocotte.jp

ホームページ運営なら、ずっと使えるレンタルサーバー「ロリポップ！」簡単、無料SSL、充実サポート、高速性能で、初心者から商用サイトまで安心してご利用いただけます。WordPress、EC-CUBEもたったの60秒で設置可能。無料お試し10日間。

Visit cocotte.jp

Key Findings

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

Performance Metrics

cocotte.jp performance score

0

Network Requests Diagram

cocotte.jp

997 ms

lolipop.jp

1917 ms

default.css

329 ms

common.css

632 ms

background.css

501 ms

Our browser made a total of 134 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Cocotte.jp, 52% (70 requests) were made to Lolipop.jp and 8% (11 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Lolipop.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 469.0 kB (37%)

Content Size

1.3 MB

After Optimization

784.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 143.1 kB

  • Original 168.0 kB
  • After minification 157.8 kB
  • After compression 24.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. 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 143.1 kB or 85% of the original size.

Image Optimization

-18%

Potential reduce by 125.4 kB

  • Original 707.6 kB
  • After minification 582.1 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. Obviously, Cocotte needs image optimization as it can save up to 125.4 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-39%

Potential reduce by 102.0 kB

  • Original 261.5 kB
  • After minification 260.8 kB
  • After compression 159.5 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 102.0 kB or 39% of the original size.

CSS Optimization

-85%

Potential reduce by 98.4 kB

  • Original 116.5 kB
  • After minification 86.2 kB
  • After compression 18.0 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. Cocotte.jp needs all CSS files to be minified and compressed as it can save up to 98.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 64 (56%)

Requests Now

114

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cocotte.jp

cocotte.jp

997 ms

lolipop.jp

lolipop.jp

1917 ms

default.css

default.css

329 ms

common.css

common.css

632 ms

background.css

background.css

501 ms

text_m.css

text_m.css

500 ms

home.css

home.css

511 ms

lightbox.css

lightbox.css

515 ms

owl.carousel.css

owl.carousel.css

545 ms

jquery.min.js

jquery.min.js

63 ms

base.js

base.js

553 ms

lightbox.min.js

lightbox.min.js

554 ms

owl.carousel.min.js

owl.carousel.min.js

594 ms

home.js

home.js

594 ms

scrollReveal.min.js

scrollReveal.min.js

595 ms

pixel.js

pixel.js

628 ms

mixpanel.js

mixpanel.js

635 ms

fbds.js

fbds.js

112 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

229 ms

bg_night.gif

bg_night.gif

221 ms

loading.gif

loading.gif

277 ms

prev.png

prev.png

258 ms

next.png

next.png

278 ms

bg_content_side.png

bg_content_side.png

616 ms

bg_main_bottom.gif

bg_main_bottom.gif

641 ms

bg_main_1column.png

bg_main_1column.png

635 ms

bg_submenu_top.gif

bg_submenu_top.gif

642 ms

h2_home_title.png

h2_home_title.png

979 ms

megaphone.svg

megaphone.svg

649 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

774 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

802 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

811 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

815 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

832 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

1089 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

972 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

1653 ms

h3_home_title.png

h3_home_title.png

1314 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

1382 ms

line_dot_11.gif

line_dot_11.gif

1146 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

1359 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

1402 ms

obj_home_feature_support.png

obj_home_feature_support.png

1647 ms

h3_home_functions.png

h3_home_functions.png

1484 ms

obj_home_functions_list.png

obj_home_functions_list.png

1668 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

1574 ms

btn_infomation_more.png

btn_infomation_more.png

1574 ms

badge_light.png

badge_light.png

215 ms

widgets.js

widgets.js

200 ms

line_dot_02.gif

line_dot_02.gif

1598 ms

icon_star.gif

icon_star.gif

1678 ms

dc.js

dc.js

80 ms

btn_h_serch.png

btn_h_serch.png

1663 ms

line_dot_08.gif

line_dot_08.gif

1720 ms

btn_pagetop.gif

btn_pagetop.gif

1726 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

1889 ms

41 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

1868 ms

__utm.gif

__utm.gif

31 ms

__utm.gif

__utm.gif

33 ms

__utm.gif

__utm.gif

32 ms

__utm.gif

__utm.gif

61 ms

obj_header_banner_text.png

obj_header_banner_text.png

1911 ms

50 ms

btn_header_order.png

btn_header_order.png

1695 ms

bg_header_simple.png

bg_header_simple.png

1728 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

1608 ms

obj_order_count_text.png

obj_order_count_text.png

1637 ms

obj_numbers.png

obj_numbers.png

1663 ms

menu_btn.png

menu_btn.png

1807 ms

pixel

pixel

314 ms

menu_dot.gif

menu_dot.gif

1618 ms

arrow_menu.gif

arrow_menu.gif

1635 ms

obj_logo_ppb.png

obj_logo_ppb.png

1653 ms

pixel

pixel

49 ms

Pug

Pug

54 ms

sync.ad-stir.com

sync.ad-stir.com

665 ms

sync

sync

37 ms

sync

sync

1057 ms

is

is

1172 ms

headerstyle.min.css

headerstyle.min.css

215 ms

pixel

pixel

16 ms

google

google

168 ms

sd

sd

29 ms

tag.js

tag.js

205 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

30 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

1140 ms

obj_next_item_icon.png

obj_next_item_icon.png

1178 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

1399 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

1430 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

1427 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

1505 ms

follow_button.6a78875565a912489e9aef879c881358.ja.html

follow_button.6a78875565a912489e9aef879c881358.ja.html

46 ms

tag

tag

55 ms

jot

jot

108 ms

lolipop.jp

lolipop.jp

1284 ms

lolipop.jp

lolipop.jp

2026 ms

lolipop.jp

lolipop.jp

1431 ms

lolipop.jp

lolipop.jp

1588 ms

lolipop.jp

lolipop.jp

1594 ms

nr-768.min.js

nr-768.min.js

70 ms

roundtrip.js

roundtrip.js

67 ms

btn.png

btn.png

42 ms

conversion_async.js

conversion_async.js

48 ms

33 ms

logo201601.png

logo201601.png

72 ms

open_footer.png

open_footer.png

104 ms

close_footer.png

close_footer.png

125 ms

55 ms

conversion.js

conversion.js

1503 ms

15936ac739

15936ac739

112 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

146 ms

64 ms

out

out

13 ms

tr

tr

11 ms

46 ms

out

out

7 ms

out

out

16 ms

out

out

39 ms

out

out

40 ms

out

out

39 ms

out

out

38 ms

out

out

37 ms

out

out

38 ms

u.php

u.php

46 ms

sd

sd

38 ms

sd

sd

39 ms

27 ms

pixel

pixel

22 ms

sync

sync

16 ms

in

in

10 ms

tap.php

tap.php

26 ms

377928.gif

377928.gif

7 ms

in

in

6 ms

SEO Factors

cocotte.jp SEO score

0

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 Cocotte.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 Cocotte.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

cocotte.jp

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