HOBBYLOG.JP ホビログ


hobbylog.jp website information.

hobbylog.jp domain name is registered by .JP top-level domain registry. See the other sites registred in .JP domain zone.

Following name servers are specified for hobbylog.jp domain:

  • ns04.ex-cloud.jp
  • ns03.ex-cloud.jp
  • ns01.atsrv.jp
  • ns02.atsrv.jp

According to Alexa traffic rank the highest website hobbylog.jp position was 25866 (in the world). The lowest Alexa rank position was 997424. Current position of hobbylog.jp in Alexa rank database is below 1 million.

Website hobbylog.jp Desktop speed measurement score (51/100) is better than the results of 24.87% of other sites shows that the page desktop performance can be improved.

hobbylog.jp Mobile usability score (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.

Mobile speed measurement score of hobbylog.jp (60/100) is better than the results of 54.7% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
Apr-26-2024 N/AN/A
Apr-25-2024 N/AN/A
Apr-24-2024 N/AN/A
Apr-23-2024 N/AN/A
Apr-22-2024 N/AN/A
Apr-21-2024 N/AN/A
Apr-20-2024 N/AN/A

Advertisement

hobbylog.jp Rank History

Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.



hobbylog.jp whois

WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.


hobbylog.jp server information

Servers Location

IP Address
203.104.130.159
Country
Japan
Region
Tokyo
City
Tokyo

hobbylog.jp desktop page speed rank

Last tested: 2016-11-22


Desktop Speed Bad
51/100

hobbylog.jp Desktop Speed Test Quick Summary


priority - 58 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://blogroll.livedoor.net/css/default2.css (expiration not specified)
http://blogroll.livedoor.net/js/blogroll.js (expiration not specified)
http://hobbylog.jp/settings/ad.js (expiration not specified)
http://hobbylog.jp/settings/header.js (expiration not specified)
http://hobbylog.sakura.ne.jp/azlink/json/bestsellers/videogames.js (expiration not specified)
http://hobbylog.sakura.ne.jp/azlink/json/new-releases/hobby/2189356051.js (expiration not specified)
http://hobbylog.sakura.ne.jp/azlink/json/new-releases/hobby/2189366051.js (expiration not specified)
http://hobbylog.sakura.ne.jp/azlink/json/new-releases/hobby/2189632051.js (expiration not specified)
http://hobbylog.sakura.ne.jp/azlink/tinywidget.min.js (expiration not specified)
http://xml.affiliate.rakuten.co.jp/widget/js/rakuten_widget.js (expiration not specified)
https://s3-ap-northeast-1.amazonaws.com/bandai.ima…01611/Liko_300x250.jpg (expiration not specified)
https://s3-ap-northeast-1.amazonaws.com/bandai.ima…kamenrider_300x250.jpg (expiration not specified)
http://blogroll.livedoor.net/42280/roll_data (10 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…9.html&_=1479769770011 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…5.html&_=1479769770014 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…8.html&_=1479769770017 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…3.html&_=1479769770020 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…2.html&_=1479769770023 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…7.html&_=1479769770026 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…0.html&_=1479769770029 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…4.html&_=1479769770032 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…4.html&_=1479769770035 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…0.html&_=1479769770038 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…3.html&_=1479769770043 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…0.html&_=1479769770046 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…6.html&_=1479769770049 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…6.html&_=1479769770052 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…8.html&_=1479769770055 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…7.html&_=1479769770058 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…5.html&_=1479769770061 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…4.html&_=1479769770064 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…8.html&_=1479769770067 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…7.html&_=1479769770070 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…0.html&_=1479769770073 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…8.html&_=1479769770076 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…7.html&_=1479769770079 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…8.html&_=1479769770082 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…4.html&_=1479769770085 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…0.html&_=1479769770088 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…9.html&_=1479769770091 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…8.html&_=1479769770094 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…5.html&_=1479769770097 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…9.html&_=1479769770100 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…6.html&_=1479769770103 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…5.html&_=1479769770106 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…0.html&_=1479769770109 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…5.html&_=1479769770112 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…7.html&_=1479769770115 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…7.html&_=1479769770118 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…2.html&_=1479769770121 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…9.html&_=1479769770124 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…9.html&_=1479769770127 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…5.html&_=1479769770130 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…0.html&_=1479769770133 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…7.html&_=1479769770136 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…4.html&_=1479769770139 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…9.html&_=1479769770142 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…6.html&_=1479769770145 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…5.html&_=1479769770148 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…9.html&_=1479769770151 (20 minutes)
http://jsoon.digitiminimi.com/twitter/count.json?c…5.html&_=1479769770154 (20 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…9.html&_=1479769770009 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…5.html&_=1479769770012 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…8.html&_=1479769770015 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…3.html&_=1479769770018 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…2.html&_=1479769770021 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…7.html&_=1479769770024 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…0.html&_=1479769770027 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…4.html&_=1479769770030 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…4.html&_=1479769770033 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…0.html&_=1479769770036 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…3.html&_=1479769770041 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…0.html&_=1479769770044 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…6.html&_=1479769770047 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…6.html&_=1479769770050 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…8.html&_=1479769770053 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…7.html&_=1479769770056 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…5.html&_=1479769770059 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…4.html&_=1479769770062 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…8.html&_=1479769770065 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…7.html&_=1479769770068 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…0.html&_=1479769770071 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…8.html&_=1479769770074 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…7.html&_=1479769770077 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…8.html&_=1479769770080 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…4.html&_=1479769770083 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…0.html&_=1479769770086 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…9.html&_=1479769770089 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…8.html&_=1479769770092 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…5.html&_=1479769770095 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…9.html&_=1479769770098 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…6.html&_=1479769770101 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…5.html&_=1479769770104 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…0.html&_=1479769770107 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…5.html&_=1479769770110 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…7.html&_=1479769770113 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…7.html&_=1479769770116 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…2.html&_=1479769770119 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…9.html&_=1479769770122 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…9.html&_=1479769770125 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…5.html&_=1479769770128 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…0.html&_=1479769770131 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…7.html&_=1479769770134 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…4.html&_=1479769770137 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…9.html&_=1479769770140 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…6.html&_=1479769770143 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…5.html&_=1479769770146 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…9.html&_=1479769770149 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…5.html&_=1479769770152 (30 minutes)
http://api.b.st-hatena.com/entry.count?callback=jQ…8.html&_=1479769770155 (30 minutes)
http://hobbylog.jp/jquery.bxslider/jquery.bxslider.css (60 minutes)
http://hobbylog.jp/jquery.bxslider/jquery.bxslider.min.js (60 minutes)
http://hobbylog.jp/jquery.sticky-kit.min.js (60 minutes)
http://hobbylog.jp/jquery.xdomainajax.js (60 minutes)
http://hobbylog.jp/popular_articles_with_image_plu…hobbylog.js?v=20130911 (60 minutes)
http://hobbylog.jp/template_6thgen2.css (60 minutes)
http://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)

priority - 18 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 177.6KiB (71% reduction).

Compressing http://parts.blog.livedoor.jp/js/jquery-1.7.1.min.js could save 59.3KiB (64% reduction).
Compressing http://xml.affiliate.rakuten.co.jp/widget/js/rakuten_widget.js could save 34.2KiB (83% reduction).
Compressing http://hobbylog.jp/jquery.bxslider/jquery.bxslider.min.js could save 13.9KiB (73% reduction).
Compressing http://parts.blog.livedoor.jp/plugin/popular_artic…e_plugin.js?v=20130911 could save 12KiB (78% reduction).
Compressing http://hobbylog.jp/popular_articles_with_image_plu…hobbylog.js?v=20130911 could save 11.9KiB (78% reduction).
Compressing http://blogroll.livedoor.net/js/blogroll.js could save 11.8KiB (78% reduction).
Compressing http://hobbylog.sakura.ne.jp/azlink/json/bestsellers/videogames.js could save 4KiB (75% reduction).
Compressing http://hobbylog.sakura.ne.jp/azlink/tinywidget.min.js could save 3.6KiB (61% reduction).
Compressing http://hobbylog.sakura.ne.jp/azlink/json/new-releases/hobby/2189366051.js could save 3.6KiB (78% reduction).
Compressing http://parts.blog.livedoor.jp/plugin/ldblog_calendar_plugin.js could save 3.4KiB (66% reduction).
Compressing http://hobbylog.sakura.ne.jp/azlink/json/new-releases/hobby/2189356051.js could save 3.2KiB (72% reduction).
Compressing http://hobbylog.sakura.ne.jp/azlink/json/new-releases/hobby/2189632051.js could save 3.1KiB (76% reduction).
Compressing http://parts.blog.livedoor.jp/js/c2.js could save 3.1KiB (65% reduction).
Compressing http://parts.blog.livedoor.jp/js/design.js could save 2.3KiB (64% reduction).
Compressing http://parts.blog.livedoor.jp/js/related_articles.js could save 2.1KiB (63% reduction).
Compressing http://parts.blog.livedoor.jp/js/recent_comments.js could save 1.5KiB (61% reduction).
Compressing http://hobbylog.jp/jquery.xdomainajax.js could save 1.4KiB (60% reduction).
Compressing http://parts.blog.livedoor.jp/js/smartphone.js?v=20131007 could save 1.1KiB (57% reduction).
Compressing http://hobbylog.jp/jquery.sticky-kit.min.js could save 1.1KiB (51% reduction).
Compressing http://blogroll.livedoor.net/css/default2.css could save 889B (69% reduction).

priority - 14 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 24 blocking script resources and 5 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://hobbylog.sakura.ne.jp./simaccess/access.php?referrer=
http://hobbylog.sakura.ne.jp/azlink/tinywidget.min.js
http://parts.blog.livedoor.jp/js/usr/import.js
http://parts.blog.livedoor.jp/js/jquery-1.7.1.min.js
http://parts.blog.livedoor.jp/js/design.js
http://ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js
http://hobbylog.jp/jquery.xdomainajax.js
http://hobbylog.jp/jquery.sticky-kit.min.js
http://hobbylog.sakura.ne.jp/azlink/tinywidget.min.js
http://hobbylog.jp/jquery.bxslider/jquery.min.js
http://hobbylog.jp/jquery.bxslider/jquery.bxslider.min.js
http://parts.blog.livedoor.jp/js/c2.js
http://parts.blog.livedoor.jp/js/smartphone.js?v=20131007
http://hobbylog.jp/settings/header.js
http://hobbylog.jp/settings/ad.js
http://xml.affiliate.rakuten.co.jp/widget/js/rakuten_widget.js
http://hobbylog.jp/popular_articles_with_image_plu…hobbylog.js?v=20130911
http://blogroll.livedoor.net/js/blogroll.js
http://xml.affiliate.rakuten.co.jp/widget/js/rakuten_widget.js
http://parts.blog.livedoor.jp/js/related_articles.js
http://xml.affiliate.rakuten.co.jp/widget/js/rakuten_widget.js
http://parts.blog.livedoor.jp/plugin/ldblog_calendar_plugin.js
http://parts.blog.livedoor.jp/js/recent_comments.js
http://parts.blog.livedoor.jp/plugin/popular_artic…e_plugin.js?v=20130911

Optimize CSS Delivery of the following:

http://parts.blog.livedoor.jp/css/template.css?v=20160701
http://hobbylog.jp/site.css?_=20161111164137
http://hobbylog.jp/template_6thgen2.css
http://blogroll.livedoor.net/css/default2.css
http://hobbylog.jp/jquery.bxslider/jquery.bxslider.css

priority - 6 Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.

The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.

Only about 52% of the final above-the-fold content could be rendered with the full HTML response.

priority - 4 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 39.4KiB (36% reduction).

Minifying http://xml.affiliate.rakuten.co.jp/widget/js/rakuten_widget.js could save 10.5KiB (26% reduction).
Minifying http://parts.blog.livedoor.jp/plugin/popular_artic…e_plugin.js?v=20130911 could save 8.3KiB (54% reduction).
Minifying http://hobbylog.jp/popular_articles_with_image_plu…hobbylog.js?v=20130911 could save 8.3KiB (54% reduction).
Minifying http://blogroll.livedoor.net/js/blogroll.js could save 5.1KiB (34% reduction).
Minifying http://parts.blog.livedoor.jp/plugin/ldblog_calendar_plugin.js could save 1.4KiB (28% reduction).
Minifying http://hobbylog.jp/jquery.xdomainajax.js could save 1.4KiB (60% reduction).
Minifying http://parts.blog.livedoor.jp/js/related_articles.js could save 1.1KiB (35% reduction).
Minifying http://parts.blog.livedoor.jp/js/c2.js could save 1KiB (22% reduction).
Minifying http://parts.blog.livedoor.jp/js/design.js could save 895B (25% reduction).
Minifying http://parts.blog.livedoor.jp/js/recent_comments.js could save 891B (35% reduction).
Minifying http://parts.blog.livedoor.jp/js/smartphone.js?v=20131007 could save 584B (29% reduction).

priority - 1 Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 13.5KiB (12% reduction).

Minifying http://hobbylog.jp/ could save 13.5KiB (12% reduction) after compression.

priority - 1 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 10.1KiB (12% reduction).

Compressing http://livedoor.blogimg.jp/hobby_log/imgs/e/6/e6bcadb2.jpg could save 8.5KiB (12% reduction).
Compressing http://livedoor.blogimg.jp/hobby_log/imgs/5/9/595d64fa.jpg could save 1.6KiB (18% reduction).

priority - 1 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 6.7KiB (32% reduction).

Minifying http://hobbylog.jp/site.css?_=20161111164137 could save 3.8KiB (39% reduction) after compression.
Minifying http://parts.blog.livedoor.jp/css/template.css?v=20160701 could save 1.7KiB (27% reduction) after compression.
Minifying http://hobbylog.jp/template_6thgen2.css could save 1.1KiB (22% reduction) after compression.

hobbylog.jp Desktop Resources

Total Resources243
Number of Hosts22
Static Resources179
JavaScript Resources172
CSS Resources5

hobbylog.jp Desktop Resource Breakdown

hobbylog.jp mobile page speed rank

Last tested: 2016-11-22


Mobile Speed Bad
60/100

hobbylog.jp Mobile Speed Test Quick Summary


priority - 40 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 15 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.

Remove render-blocking JavaScript:

http://parts.blog.livedoor.jp/js/lite2/common.js?v=20150425
http://parts.blog.livedoor.jp/js/lite2/main.js?v=20160909
http://parts.blog.livedoor.jp/js/jquery-1.11.1.min.js
http://parts.blog.livedoor.jp/js/jquery.cookie.min.js
http://parts.blog.livedoor.jp/js/micro_template.js
http://parts.blog.livedoor.jp/js/c2.js
http://hobbylog.jp/settings/lite2/ads.js
http://api.unthem.com/js/spad.js?zname=spad0020&re…id=6043769&_=457356910
https://js.ad-stir.com/js/adstir.js?20130527
http://ad.ad-stir.com/ad?app_id=MEDIA-759075f2&ad_…B5386789956A4130292009
http://spad.i-mobile.co.jp/script/adssp.js?20110215
http://spad.i-mobile.co.jp/script/adcore.js?20110201
http://spad.i-mobile.co.jp/script/adcore_sp.js?20110201
http://spad.i-mobile.co.jp/script/adcore_sp_inline-0.3.js?20110201
http://js.ad-stir.com/js/nativeapi.js

Optimize CSS Delivery of the following:

http://parts.blog.livedoor.jp/css/lite2/common.css?20161028
http://parts.blog.livedoor.jp/css/lite2/usr/matomeyellow.css?20160714

priority - 16 Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://hobbylog.jp/_/json/linelive_ranking.json (expiration not specified)
http://hobbylog.jp/_/json/ranking_category_min_426.json (expiration not specified)
http://hobbylog.jp/settings/lite2/ads.js (expiration not specified)
http://blogroll.livedoor.net/url/http://ameblo.jp/…entry-12221533828.html (2 minutes)
http://blogroll.livedoor.net/url/http://ameblo.jp/…entry-12221471802.html (2 minutes)
http://blogroll.livedoor.net/url/http://blog.lived…archives/52096635.html (2 minutes)
http://blogroll.livedoor.net/url/http://hobby.dengeki.com/news/291792/ (2 minutes)
http://blogroll.livedoor.net/url/http://hobby.dengeki.com/news/293512/ (2 minutes)
http://blogroll.livedoor.net/url/http://hobby.dengeki.com/news/294472/ (2 minutes)
http://blogroll.livedoor.net/url/http://hobby.dengeki.com/news/295038/ (2 minutes)
http://blogroll.livedoor.net/url/http://hobby.dengeki.com/reviews/295250/ (2 minutes)
http://blogroll.livedoor.net/url/http://idolmaster.jp/blog/?p=25014 (2 minutes)
http://blogroll.livedoor.net/url/http://lin.ee/1Ikoiuq (2 minutes)
http://blogroll.livedoor.net/url/http://www.medicomtoy.tv/blog/?p=34687 (2 minutes)
http://blogroll.livedoor.net/125734/roll_data (10 minutes)
https://cdn.syndication.twimg.com/widgets/followbu…screen_names=Hobby_Log (10 minutes)
http://js.ad-stir.com/js/nativeapi.js (15 minutes)
https://js.ad-stir.com/js/adstir.js?20130527 (15 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
http://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js (60 minutes)
http://t.blog.livedoor.jp/u.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)

priority - 11 Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 110.4KiB (66% reduction).

Compressing http://parts.blog.livedoor.jp/js/jquery-1.11.1.min.js could save 61.1KiB (65% reduction).
Compressing http://spad.i-mobile.co.jp/script/adcore_sp.js?20110201 could save 21KiB (65% reduction).
Compressing http://parts.blog.livedoor.jp/js/lite2/main.js?v=20160909 could save 13.6KiB (77% reduction).
Compressing http://parts.blog.livedoor.jp/js/lite2/common.js?v=20150425 could save 4.7KiB (63% reduction).
Compressing http://parts.blog.livedoor.jp/js/c2.js could save 3.1KiB (65% reduction).
Compressing https://platform.twitter.com/js/button.5546439b5d743401ca910708312f6e81.js could save 2.8KiB (65% reduction).
Compressing http://spad.i-mobile.co.jp/script/adcore_sp_inline-0.3.js?20110201 could save 2.3KiB (60% reduction).
Compressing http://parts.blog.livedoor.jp/js/jquery.cookie.min.js could save 1,021B (54% reduction).
Compressing http://parts.blog.livedoor.jp/js/micro_template.js could save 806B (54% reduction).

priority - 1 Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 10.4KiB (34% reduction).

Minifying http://parts.blog.livedoor.jp/js/lite2/main.js?v=20160909 could save 6.1KiB (35% reduction).
Minifying http://parts.blog.livedoor.jp/js/lite2/common.js?v=20150425 could save 2.5KiB (34% reduction).
Minifying http://parts.blog.livedoor.jp/js/c2.js could save 1KiB (22% reduction).
Minifying http://parts.blog.livedoor.jp/js/micro_template.js could save 866B (58% reduction).

priority - 0 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 3KiB (46% reduction).

Compressing http://parts.blog.livedoor.jp/img/cms_lite/common/icon/icon_forward.png could save 914B (82% reduction).
Compressing http://parts.blog.livedoor.jp/img/lite2/icon_new.png could save 891B (82% reduction).
Compressing http://blogroll.livedoor.net/img/blank.gif?channel…125734&_=1479769761075 could save 712B (88% reduction).
Compressing http://resize.blogsys.jp/c6428b20ed03437fe2d8f4127…/imgs/0/9/09efe0d0.jpg could save 516B (14% reduction).

priority - 0 Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 2.3KiB (14% reduction).

Minifying http://parts.blog.livedoor.jp/css/lite2/common.css?20161028 could save 2.3KiB (14% reduction) after compression.

hobbylog.jp Mobile Resources

Total Resources139
Number of Hosts28
Static Resources102
JavaScript Resources33
CSS Resources2

hobbylog.jp Mobile Resource Breakdown

hobbylog.jp mobile page usability

Last tested: 2016-11-22


Mobile Usability Good
99/100

hobbylog.jp Mobile Usability Test Quick Summary


priority - 0 Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://hobby.d…m/news/294472/" class="blogroll-link">『勇者王ガオガイガー』が「ス…による変形・合体を完全再現!</a> and 9 others are close to other tap targets.
The tap target <a href="http://nav.cx/2IS8fuK" class="blogroll_ad_livedoor2">スッキリ収納・おしゃれインテリア記事続々!</a> is close to 1 other tap targets.

hobbylog.jp similar domains

Similar domains:
www.hobbylog.com
www.hobbylog.net
www.hobbylog.org
www.hobbylog.info
www.hobbylog.biz
www.hobbylog.us
www.hobbylog.mobi
www.obbylog.jp
www.hobbylog.jp
www.bobbylog.jp
www.hbobbylog.jp
www.bhobbylog.jp
www.gobbylog.jp
www.hgobbylog.jp
www.ghobbylog.jp
www.yobbylog.jp
www.hyobbylog.jp
www.yhobbylog.jp
www.uobbylog.jp
www.huobbylog.jp
www.uhobbylog.jp
www.jobbylog.jp
www.hjobbylog.jp
www.jhobbylog.jp
www.nobbylog.jp
www.hnobbylog.jp
www.nhobbylog.jp
www.hbbylog.jp
www.hibbylog.jp
www.hoibbylog.jp
www.hiobbylog.jp
www.hkbbylog.jp
www.hokbbylog.jp
www.hkobbylog.jp
www.hlbbylog.jp
www.holbbylog.jp
www.hlobbylog.jp
www.hpbbylog.jp
www.hopbbylog.jp
www.hpobbylog.jp
www.hobylog.jp
www.hovbylog.jp
www.hobvbylog.jp
www.hovbbylog.jp
www.hogbylog.jp
www.hobgbylog.jp
www.hogbbylog.jp
www.hohbylog.jp
www.hobhbylog.jp
www.hohbbylog.jp
www.honbylog.jp
www.hobnbylog.jp
www.honbbylog.jp
www.hobvylog.jp
www.hobbvylog.jp
www.hobgylog.jp
www.hobbgylog.jp
www.hobhylog.jp
www.hobbhylog.jp
www.hobnylog.jp
www.hobbnylog.jp
www.hobblog.jp
www.hobbtlog.jp
www.hobbytlog.jp
www.hobbtylog.jp
www.hobbglog.jp
www.hobbyglog.jp
www.hobbhlog.jp
www.hobbyhlog.jp
www.hobbulog.jp
www.hobbyulog.jp
www.hobbuylog.jp
www.hobbyog.jp
www.hobbypog.jp
www.hobbylpog.jp
www.hobbyplog.jp
www.hobbyoog.jp
www.hobbyloog.jp
www.hobbyolog.jp
www.hobbykog.jp
www.hobbylkog.jp
www.hobbyklog.jp
www.hobbylg.jp
www.hobbylig.jp
www.hobbyloig.jp
www.hobbyliog.jp
www.hobbylkg.jp
www.hobbylokg.jp
www.hobbyllg.jp
www.hobbylolg.jp
www.hobbyllog.jp
www.hobbylpg.jp
www.hobbylopg.jp
www.hobbylo.jp
www.hobbylof.jp
www.hobbylogf.jp
www.hobbylofg.jp
www.hobbylov.jp
www.hobbylogv.jp
www.hobbylovg.jp
www.hobbylot.jp
www.hobbylogt.jp
www.hobbylotg.jp
www.hobbylob.jp
www.hobbylogb.jp
www.hobbylobg.jp
www.hobbyloy.jp
www.hobbylogy.jp
www.hobbyloyg.jp
www.hobbyloh.jp
www.hobbylogh.jp
www.hobbylohg.jp

hobbylog.jp Ping

Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.


hobbylog.jp TRACEROUTE

Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.