Tools & Wizards About Us
capoo.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

capoo.jp

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

Page Load Speed

10 sec in total

First Response

499 ms

Resources Loaded

9.1 sec

Page Rendered

381 ms

capoo.jp screenshot

About Website

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

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

Visit capoo.jp

Key Findings

We analyzed Capoo.jp page load time and found that the first response time was 499 ms and then it took 9.5 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

capoo.jp performance score

0

Network Requests Diagram

capoo.jp

499 ms

lolipop.jp

1243 ms

default.css

328 ms

common.css

630 ms

background.css

473 ms

Our browser made a total of 135 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Capoo.jp, 53% (71 requests) were made to Lolipop.jp and 9% (12 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Lolipop.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 505.5 kB (39%)

Content Size

1.3 MB

After Optimization

784.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Capoo.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. 40% 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 142.9 kB

  • Original 167.6 kB
  • After minification 157.5 kB
  • After compression 24.7 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 142.9 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, Capoo 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

-47%

Potential reduce by 138.7 kB

  • Original 298.2 kB
  • After minification 297.4 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 138.7 kB or 47% 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. Capoo.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 Capoo. 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

capoo.jp

capoo.jp

499 ms

lolipop.jp

lolipop.jp

1243 ms

default.css

default.css

328 ms

common.css

common.css

630 ms

background.css

background.css

473 ms

text_m.css

text_m.css

473 ms

home.css

home.css

662 ms

lightbox.css

lightbox.css

505 ms

owl.carousel.css

owl.carousel.css

544 ms

jquery.min.js

jquery.min.js

70 ms

base.js

base.js

633 ms

lightbox.min.js

lightbox.min.js

481 ms

owl.carousel.min.js

owl.carousel.min.js

704 ms

home.js

home.js

585 ms

scrollReveal.min.js

scrollReveal.min.js

629 ms

pixel.js

pixel.js

1020 ms

mixpanel.js

mixpanel.js

654 ms

fbds.js

fbds.js

148 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

179 ms

bg_night.gif

bg_night.gif

180 ms

close.png

close.png

244 ms

loading.gif

loading.gif

271 ms

prev.png

prev.png

270 ms

next.png

next.png

293 ms

bg_content_side.png

bg_content_side.png

342 ms

bg_main_bottom.gif

bg_main_bottom.gif

338 ms

bg_main_1column.png

bg_main_1column.png

415 ms

bg_submenu_top.gif

bg_submenu_top.gif

426 ms

h2_home_title.png

h2_home_title.png

583 ms

megaphone.svg

megaphone.svg

450 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

507 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

511 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

735 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

583 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

728 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

741 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

745 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

1181 ms

h3_home_title.png

h3_home_title.png

1346 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

2202 ms

line_dot_11.gif

line_dot_11.gif

1907 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

2394 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

2070 ms

obj_home_feature_support.png

obj_home_feature_support.png

2592 ms

h3_home_functions.png

h3_home_functions.png

2289 ms

obj_home_functions_list.png

obj_home_functions_list.png

2872 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

2864 ms

btn_infomation_more.png

btn_infomation_more.png

2798 ms

line_dot_02.gif

line_dot_02.gif

2799 ms

badge_light.png

badge_light.png

184 ms

widgets.js

widgets.js

188 ms

icon_star.gif

icon_star.gif

2763 ms

btn_h_serch.png

btn_h_serch.png

2719 ms

line_dot_08.gif

line_dot_08.gif

2864 ms

dc.js

dc.js

91 ms

btn_pagetop.gif

btn_pagetop.gif

2848 ms

50 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

2839 ms

24 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

2974 ms

obj_header_banner_text.png

obj_header_banner_text.png

3031 ms

__utm.gif

__utm.gif

30 ms

__utm.gif

__utm.gif

14 ms

__utm.gif

__utm.gif

29 ms

__utm.gif

__utm.gif

31 ms

btn_header_order.png

btn_header_order.png

3147 ms

bg_header_simple.png

bg_header_simple.png

3362 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

2965 ms

obj_order_count_text.png

obj_order_count_text.png

2951 ms

obj_numbers.png

obj_numbers.png

2949 ms

menu_btn.png

menu_btn.png

3235 ms

menu_dot.gif

menu_dot.gif

3023 ms

arrow_menu.gif

arrow_menu.gif

2969 ms

obj_logo_ppb.png

obj_logo_ppb.png

2973 ms

pixel

pixel

151 ms

pixel

pixel

75 ms

Pug

Pug

88 ms

sync.ad-stir.com

sync.ad-stir.com

633 ms

sync

sync

68 ms

sync

sync

678 ms

is

is

1106 ms

headerstyle.min.css

headerstyle.min.css

155 ms

sd

sd

12 ms

pixel

pixel

21 ms

google

google

151 ms

tag.js

tag.js

49 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

42 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

2202 ms

obj_next_item_icon.png

obj_next_item_icon.png

2243 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

2437 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

2420 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

2539 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

2559 ms

tag

tag

35 ms

follow_button.6a78875565a912489e9aef879c881358.ja.html

follow_button.6a78875565a912489e9aef879c881358.ja.html

56 ms

jot

jot

101 ms

lolipop.jp

lolipop.jp

1263 ms

lolipop.jp

lolipop.jp

1484 ms

lolipop.jp

lolipop.jp

1795 ms

lolipop.jp

lolipop.jp

2052 ms

lolipop.jp

lolipop.jp

1602 ms

nr-768.min.js

nr-768.min.js

138 ms

roundtrip.js

roundtrip.js

123 ms

btn.png

btn.png

45 ms

conversion_async.js

conversion_async.js

54 ms

34 ms

logo201601.png

logo201601.png

77 ms

open_footer.png

open_footer.png

115 ms

close_footer.png

close_footer.png

142 ms

52 ms

conversion.js

conversion.js

1169 ms

42 ms

15936ac739

15936ac739

147 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

29 ms

out

out

12 ms

tr

tr

11 ms

out

out

6 ms

out

out

18 ms

out

out

17 ms

out

out

37 ms

out

out

37 ms

out

out

37 ms

out

out

36 ms

out

out

38 ms

out

out

39 ms

u.php

u.php

98 ms

23 ms

sd

sd

40 ms

sd

sd

41 ms

pixel

pixel

33 ms

sync

sync

27 ms

in

in

7 ms

377928.gif

377928.gif

6 ms

tap.php

tap.php

66 ms

in

in

5 ms

SEO Factors

capoo.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 Capoo.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 Capoo.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

capoo.jp

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