Tools & Wizards About Us
coocan.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

coocan.jp

@niftyホームページサービス - ホームページ作成なら@niftyホームページサービスで！

Page Load Speed

5.4 sec in total

First Response

556 ms

Resources Loaded

4.8 sec

Page Rendered

124 ms

coocan.jp screenshot

About Website

Welcome to coocan.jp homepage info - get ready to check Coocan best content for Japan right away, or after learning these important things about coocan.jp

ホームページ作成なら『@niftyホームページサービス』@niftyが提供する大容量ホームページサービスです。充実のマニュアルでホームページはもちろん、CGIやブログ、wikiなど初めての方でも簡単に始められます。

Visit coocan.jp

Key Findings

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

Performance Metrics

coocan.jp performance score

0

Network Requests Diagram

coocan.jp

556 ms

lacoocan.nifty.com

565 ms

homepage.nifty.com

939 ms

style.css

1028 ms

jquery.lightbox-0.5.css

348 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Coocan.jp, 82% (51 requests) were made to Homepage.nifty.com and 3% (2 requests) were made to Tag.nifty.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Homepage.nifty.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 718.4 kB (55%)

Content Size

1.3 MB

After Optimization

587.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Coocan.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. 20% of websites need less resources to load. CSS take 523.1 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 10.4 kB

  • Original 14.9 kB
  • After minification 13.8 kB
  • After compression 4.5 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 10.4 kB or 70% of the original size.

Image Optimization

-7%

Potential reduce by 28.8 kB

  • Original 396.5 kB
  • After minification 367.7 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. Coocan images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 253.2 kB

  • Original 371.5 kB
  • After minification 333.6 kB
  • After compression 118.3 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 253.2 kB or 68% of the original size.

CSS Optimization

-81%

Potential reduce by 425.9 kB

  • Original 523.1 kB
  • After minification 501.6 kB
  • After compression 97.2 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. Coocan.jp needs all CSS files to be minified and compressed as it can save up to 425.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (44%)

Requests Now

57

After Optimization

32

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

coocan.jp

coocan.jp

556 ms

lacoocan.nifty.com

lacoocan.nifty.com

565 ms

homepage.nifty.com

homepage.nifty.com

939 ms

style.css

style.css

1028 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

348 ms

jquery-1.4.2.min.js

jquery-1.4.2.min.js

1209 ms

base.js

base.js

360 ms

jquery.lightbox-0.5.js

jquery.lightbox-0.5.js

916 ms

capture.js

capture.js

519 ms

htaccess.js

htaccess.js

1332 ms

ad.cgi

ad.cgi

845 ms

ad.cgi

ad.cgi

616 ms

_nif_tag.js

_nif_tag.js

549 ms

conversion.js

conversion.js

65 ms

556 ms

nifty_logo.gif

nifty_logo.gif

207 ms

homepageservice_logo.gif

homepageservice_logo.gif

346 ms

usermenu_login.jpg

usermenu_login.jpg

175 ms

usermenu_help.jpg

usermenu_help.jpg

173 ms

top_text.gif

top_text.gif

367 ms

type_1.gif

type_1.gif

205 ms

type_2.gif

type_2.gif

343 ms

type_3.gif

type_3.gif

347 ms

btn_moushikomi_top.gif

btn_moushikomi_top.gif

358 ms

bbs.gif

bbs.gif

754 ms

basic-hosting.gif

basic-hosting.gif

689 ms

gotop.gif

gotop.gif

518 ms

foot_toroku.gif

foot_toroku.gif

518 ms

bn12_728_90.jpg

bn12_728_90.jpg

708 ms

line_tate01.gif

line_tate01.gif

541 ms

mainmenu_bg.jpg

mainmenu_bg.jpg

679 ms

menu_03_01.jpg

menu_03_01.jpg

681 ms

menu_01_02.jpg

menu_01_02.jpg

906 ms

menu_01_03.jpg

menu_01_03.jpg

849 ms

menu_01_04.jpg

menu_01_04.jpg

852 ms

menu_01_05.jpg

menu_01_05.jpg

853 ms

menu_01_06.jpg

menu_01_06.jpg

886 ms

contents_bg.gif

contents_bg.gif

932 ms

contents_arrow.gif

contents_arrow.gif

1019 ms

contents_h_img.gif

contents_h_img.gif

1025 ms

btn_apply02.gif

btn_apply02.gif

1026 ms

usermenu_bg.jpg

usermenu_bg.jpg

1064 ms

sidemenu_bg.jpg

sidemenu_bg.jpg

1272 ms

contents_menu_head.jpg

contents_menu_head.jpg

1121 ms

sidemenu_ol_bg.jpg

sidemenu_ol_bg.jpg

1189 ms

sidemenu_icon.gif

sidemenu_icon.gif

1197 ms

3col_bordered_upper.gif

3col_bordered_upper.gif

1198 ms

3col_bordered_lower.gif

3col_bordered_lower.gif

1242 ms

rc12_200_200.jpg

rc12_200_200.jpg

1677 ms

contents_f_img.gif

contents_f_img.gif

1350 ms

icon_arrow_up.gif

icon_arrow_up.gif

1358 ms

ga.js

ga.js

150 ms

foot_h_img.gif

foot_h_img.gif

1215 ms

foot_f_img.gif

foot_f_img.gif

1262 ms

__utm.gif

__utm.gif

73 ms

_nif_tag.gif

_nif_tag.gif

191 ms

238 ms

usermenu_login_on.jpg

usermenu_login_on.jpg

1442 ms

usermenu_help_on.jpg

usermenu_help_on.jpg

1335 ms

btn_moushikomi_top_on.gif

btn_moushikomi_top_on.gif

1391 ms

207 ms

134 ms

SEO Factors

coocan.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 Coocan.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 Coocan.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

coocan.jp

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