Tools & Wizards About Us
hotcom-web.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hotcom-web.com

WordPressが使える無料HPスペース│freeweb

Page Load Speed

9.2 sec in total

First Response

1.8 sec

Resources Loaded

7 sec

Page Rendered

349 ms

hotcom-web.com screenshot

About Website

Welcome to hotcom-web.com homepage info - get ready to check Hotcom Web best content for Japan right away, or after learning these important things about hotcom-web.com

自由度の高い無料HPスペース。CGI／SSIの使えるフリースペース。しかも料金無料です。

Visit hotcom-web.com

Key Findings

We analyzed Hotcom-web.com page load time and found that the first response time was 1.8 sec and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

hotcom-web.com performance score

0

Network Requests Diagram

hotcom-web.com

1812 ms

common.css

369 ms

loader.js

380 ms

login_out.js

397 ms

tbyk.js

404 ms

Our browser made a total of 167 requests to load all elements on the main page. We found that 66% of them (110 requests) were addressed to the original Hotcom-web.com, 4% (7 requests) were made to Apis.google.com and 4% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Hotcom-web.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 678.7 kB (41%)

Content Size

1.7 MB

After Optimization

995.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hotcom-web.com main page is 1.7 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. 70% of websites need less resources to load. Images take 757.5 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 62.8 kB

  • Original 73.2 kB
  • After minification 43.2 kB
  • After compression 10.3 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 30.0 kB, which is 41% 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 62.8 kB or 86% of the original size.

Image Optimization

-5%

Potential reduce by 36.8 kB

  • Original 757.5 kB
  • After minification 720.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. Hotcom Web images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 445.1 kB

  • Original 687.9 kB
  • After minification 620.0 kB
  • After compression 242.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 445.1 kB or 65% of the original size.

CSS Optimization

-86%

Potential reduce by 133.9 kB

  • Original 155.9 kB
  • After minification 108.3 kB
  • After compression 22.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. Hotcom-web.com needs all CSS files to be minified and compressed as it can save up to 133.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 83 (52%)

Requests Now

160

After Optimization

77

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hotcom-web.com

hotcom-web.com

1812 ms

common.css

common.css

369 ms

loader.js

loader.js

380 ms

login_out.js

login_out.js

397 ms

tbyk.js

tbyk.js

404 ms

adsbygoogle.js

adsbygoogle.js

5 ms

query_renderer.js

query_renderer.js

14 ms

js

js

25 ms

query_renderer.js

query_renderer.js

65 ms

js

js

159 ms

base.css

base.css

185 ms

modules_layout.css

modules_layout.css

373 ms

modules_common.css

modules_common.css

231 ms

modules_common_add.css

modules_common_add.css

222 ms

jRound.css

jRound.css

237 ms

button.css

button.css

363 ms

li-scroller.css

li-scroller.css

379 ms

curl.css

curl.css

415 ms

jquery-ui-1.8.13.custom.css

jquery-ui-1.8.13.custom.css

431 ms

jquery.treeview.css

jquery.treeview.css

434 ms

jquery.fileinput.css

jquery.fileinput.css

543 ms

jquery.rating.css

jquery.rating.css

552 ms

tipsy.css

tipsy.css

564 ms

jquery.ui.selectmenu.css

jquery.ui.selectmenu.css

609 ms

onloadSetup.js

onloadSetup.js

612 ms

plusone.js

plusone.js

56 ms

poweredby_999999.gif

poweredby_999999.gif

14 ms

area_gnavi_logo_on.jpg

area_gnavi_logo_on.jpg

363 ms

area_gnavi_news.jpg

area_gnavi_news.jpg

184 ms

area_gnavi_feature.jpg

area_gnavi_feature.jpg

401 ms

area_gnavi_policy.jpg

area_gnavi_policy.jpg

392 ms

area_gnavi_inquiry.jpg

area_gnavi_inquiry.jpg

377 ms

area_gnavi_company.jpg

area_gnavi_company.jpg

218 ms

campaign110808.png

campaign110808.png

918 ms

appeal2.png

appeal2.png

619 ms

icon_perl58.jpg

icon_perl58.jpg

546 ms

icon_PHP53.png

icon_PHP53.png

566 ms

icon_MySQL55.png

icon_MySQL55.png

588 ms

catch_about.jpg

catch_about.jpg

802 ms

about.jpg

about.jpg

727 ms

croooober.png

croooober.png

1505 ms

ad_banner_royal.jpg

ad_banner_royal.jpg

1370 ms

ad_banner_freeweb.gif

ad_banner_freeweb.gif

821 ms

catch_premium.png

catch_premium.png

908 ms

premium.png

premium.png

1203 ms

catch_forum.png

catch_forum.png

1020 ms

forum.png

forum.png

1089 ms

catch_WP.jpg

catch_WP.jpg

1100 ms

WPbanner.jpg

WPbanner.jpg

1221 ms

whats.jpg

whats.jpg

1271 ms

forjs.css

forjs.css

1283 ms

jquery.js

jquery.js

1619 ms

jquery.cookie.js

jquery.cookie.js

1423 ms

jquery-ui-1.8.13.custom.min.js

jquery-ui-1.8.13.custom.min.js

2028 ms

jquery-ui_setup.js

jquery-ui_setup.js

1470 ms

jquery.rollover.js

jquery.rollover.js

1563 ms

jquery.rollover_setup.js

jquery.rollover_setup.js

1632 ms

jquery.easing.js

jquery.easing.js

1652 ms

jquery.bodyScroller.js

jquery.bodyScroller.js

1687 ms

windowopen.js

windowopen.js

1758 ms

jquery.timers-1.2.js

jquery.timers-1.2.js

1819 ms

jRound.js

jRound.js

1822 ms

colHeightAdjuster.js

colHeightAdjuster.js

1830 ms

jquery.li-scroller.1.0.js

jquery.li-scroller.1.0.js

1703 ms

jquery.li-scroller_setup.js

jquery.li-scroller_setup.js

1746 ms

jcurl.js

jcurl.js

1668 ms

ga.js

ga.js

1658 ms

jquery.socialbutton.js

jquery.socialbutton.js

1640 ms

jquery.socialbutton_setup.js

jquery.socialbutton_setup.js

1674 ms

jquery.treeview.js

jquery.treeview.js

1616 ms

jquery.treeview_setup.js

jquery.treeview_setup.js

1666 ms

jquery.placeholder.js

jquery.placeholder.js

1626 ms

jquery.fileinput.min.js

jquery.fileinput.min.js

1617 ms

setup.js

setup.js

1490 ms

jquery.rating.pack.js

jquery.rating.pack.js

1461 ms

jquery.tipsy.js

jquery.tipsy.js

1536 ms

jquery.ui.selectmenu.js

jquery.ui.selectmenu.js

1493 ms

yuga.js

yuga.js

1484 ms

jquery.carouFredSel.js

jquery.carouFredSel.js

1413 ms

ga.js

ga.js

30 ms

__utm.gif

__utm.gif

12 ms

area_loginBarBG.gif

area_loginBarBG.gif

325 ms

login_out.php

login_out.php

297 ms

area_topImg_background.jpg

area_topImg_background.jpg

1107 ms

tbyk.php

tbyk.php

296 ms

ca-pub-1049370767361411.js

ca-pub-1049370767361411.js

51 ms

zrt_lookup.html

zrt_lookup.html

34 ms

show_ads_impl.js

show_ads_impl.js

50 ms

branding.css

branding.css

20 ms

branding.css

branding.css

13 ms

tbyk.php

tbyk.php

373 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

240 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

239 ms

area_gnavi_news_on.jpg

area_gnavi_news_on.jpg

307 ms

area_gnavi_feature_on.jpg

area_gnavi_feature_on.jpg

315 ms

area_gnavi_policy_on.jpg

area_gnavi_policy_on.jpg

307 ms

area_gnavi_inquiry_on.jpg

area_gnavi_inquiry_on.jpg

313 ms

area_gnavi_company_on.jpg

area_gnavi_company_on.jpg

518 ms

campaign110808_on.png

campaign110808_on.png

671 ms

premium_on.png

premium_on.png

682 ms

forum_on.png

forum_on.png

528 ms

adsbygoogle.js

adsbygoogle.js

153 ms

query_renderer.js

query_renderer.js

145 ms

js

js

144 ms

mL.jpg

mL.jpg

517 ms

mL_appeal.jpg

mL_appeal.jpg

655 ms

adsbygoogle.js

adsbygoogle.js

143 ms

mR.jpg

mR.jpg

703 ms

mR_appeal.jpg

mR_appeal.jpg

705 ms

bR.jpg

bR.jpg

838 ms

bR_appeal.jpg

bR_appeal.jpg

837 ms

bL.jpg

bL.jpg

833 ms

bL_appeal.jpg

bL_appeal.jpg

888 ms

tL.jpg

tL.jpg

890 ms

tL_appeal.jpg

tL_appeal.jpg

990 ms

fastbutton

fastbutton

231 ms

widgets.js

widgets.js

116 ms

button-only.gif

button-only.gif

355 ms

bookmark_button.js

bookmark_button.js

430 ms

favorite.pl

favorite.pl

355 ms

share

share

431 ms

ads

ads

305 ms

ads

ads

238 ms

tR.jpg

tR.jpg

926 ms

tR_appeal.jpg

tR_appeal.jpg

925 ms

ui-bg_highlight-soft_70_f78d1d_1x100.png

ui-bg_highlight-soft_70_f78d1d_1x100.png

990 ms

ui-bg_inset-soft_25_000000_1x100.png

ui-bg_inset-soft_25_000000_1x100.png

990 ms

getuserimg.php

getuserimg.php

1018 ms

getuserimg.php

getuserimg.php

1098 ms

getuserimg.php

getuserimg.php

1152 ms

getuserimg.php

getuserimg.php

1129 ms

getuserimg.php

getuserimg.php

1623 ms

getuserimg.php

getuserimg.php

1249 ms

getuserimg.php

getuserimg.php

1275 ms

getuserimg.php

getuserimg.php

1311 ms

getuserimg.php

getuserimg.php

1347 ms

getuserimg.php

getuserimg.php

1379 ms

js

js

104 ms

query_renderer.js

query_renderer.js

34 ms

like.php

like.php

166 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

188 ms

postmessageRelay

postmessageRelay

86 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

31 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

29 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

132 ms

api.js

api.js

55 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

110 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

94 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

517 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

581 ms

15122106571364463425

15122106571364463425

87 ms

abg.js

abg.js

86 ms

m_js_controller.js

m_js_controller.js

94 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

131 ms

2546827883854070751

2546827883854070751

56 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

68 ms

s

s

39 ms

x_button_blue2.png

x_button_blue2.png

53 ms

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js

25 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

47 ms

239 ms

btn_iine_20.png

btn_iine_20.png

341 ms

jot

jot

81 ms

reset.css

reset.css

5 ms

entry-button.css

entry-button.css

5 ms

button-counter.gif

button-counter.gif

3 ms

print.css

print.css

204 ms

SEO Factors

hotcom-web.com 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 Hotcom-web.com 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 Hotcom-web.com 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

hotcom-web.com

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