BLOGCMS.JP ライブドアブログ|豊富な機能で無料ブログ作成

blogcms.jp Website Information

Daily Unique Visits: 4,382

Daily Page Views: 17,528

Income Per Day: $49

Estimated Value: $26,460

This website is located in Japan and is using following IP address 203.104.150.139. See the complete list of popular websites hosted in Japan.

blogcms.jp is registered under .JP top-level domain. Please check other sites in .JP zone.

Website blogcms.jp is using the following name servers:

  • ns1.naver.jp
  • ns2.naver.jp

and is probably hosted by LINE LINE Corporation, JP. See the full list of other websites hosted by LINE LINE Corporation, JP.

The highest website blogcms.jp position in Alexa rank database was 74060 and the lowest rank position was 286376. Current position of blogcms.jp in Alexa rank database is 286376.

Desktop speed score of blogcms.jp (35/100) is better than the results of 11.34% of other sites and shows that the page desktop performance can be improved.

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

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

Advertisement

blogcms.jp Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


blogcms.jp whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


[ JPRS database provides information on network administration. Its use is ]
[ restricted to network administration purposes. For further information, ]
[ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ]
[ at the end of command, e.g. 'whois -h whois.jprs.jp xxx/e'. ]

Domain Information: [ドメイン情報]
[Domain Name] BLOGCMS.JP

[登録者名] LINE株式会社
[Registrant] LINE Corporation

[Name Server] ns1.naver.jp
[Name Server] ns2.naver.jp
[Signing Key]

[登録年月日] 2008/12/01
[有効期限] 2021/12/31
[状態] Active
[最終更新] 2021/01/01 01:05:10 (JST)

Contact Information: [公開連絡窓口]
[名前] クラリベイト・アナリティクス・ジャパン株式会社
[Name] Clarivate Analytics (Japan) Co.,Ltd.
[Email] domain.jp@markmonitor.com
[Web Page]
[郵便番号] 107-6119
[住所] 東京都港区赤坂5丁目2番20号
赤坂パークビル19階
[Postal Address] Akasaka Park Building, 19F,
5-2-20, Akasaka,Minato-ku,Tokyo
[電話番号] 03-4589-3900
[FAX番号] 03-4589-3240

blogcms.jp server information

Servers Location

blogcms.jp desktop page speed rank

Last tested: 2016-06-13


Desktop Speed Bad
35/100

blogcms.jp Desktop Speed Test Quick Summary


priority - 153Optimize images

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

Optimize the following images to reduce their size by 1.5MiB (68% reduction).

Compressing and resizing http://blog.livedoor.com/blog_portal/lite/img/banner/select_6651747.png could save 277.3KiB (71% reduction).
Compressing and resizing http://blog.livedoor.com/blog_portal/lite/img/banner/select_6715510.png could save 243.3KiB (76% reduction).
Compressing and resizing http://blog.livedoor.com/blog_portal/lite/img/banner/select_6649150.png could save 220.3KiB (63% reduction).
Compressing and resizing http://blog.livedoor.com/blog_portal/lite/img/banner/select_6187500.png could save 157.3KiB (67% reduction).
Compressing and resizing http://blog.livedoor.jp/staff/portal_banner/lite_select_6864617.png could save 129.2KiB (66% reduction).
Compressing and resizing http://blog.livedoor.com/blog_portal/lite/img/banner/select_6665127.png could save 121.2KiB (64% reduction).
Compressing and resizing http://ecx.images-amazon.com/images/I/61H8t99OFHL.…2_BO1,204,203,200_.jpg could save 56.4KiB (86% reduction).
Compressing and resizing http://ecx.images-amazon.com/images/I/61lSPVbIOyL.…1_BO1,204,203,200_.jpg could save 55KiB (87% reduction).
Compressing and resizing http://ecx.images-amazon.com/images/I/51AEMGubyKL.…0_BO1,204,203,200_.jpg could save 44.3KiB (85% reduction).
Compressing and resizing http://ecx.images-amazon.com/images/I/51HPVLdVCcL.…0_BO1,204,203,200_.jpg could save 41.7KiB (86% reduction).
Compressing and resizing http://ecx.images-amazon.com/images/I/51NYN5PFMuL.…0_BO1,204,203,200_.jpg could save 35KiB (84% reduction).
Compressing and resizing http://blog.livedoor.com/blog_portal/lite/img/banner/select_5946944.png could save 32.8KiB (63% reduction).
Compressing and resizing http://ecx.images-amazon.com/images/I/51mtBdalCLL.…0_BO1,204,203,200_.jpg could save 28.6KiB (86% reduction).
Compressing and resizing http://blog.livedoor.com/blog_portal/lite/img/banner/select_6411595.png could save 23.8KiB (61% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface_7112257.png could save 1.8KiB (42% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface_7096403.png could save 1.6KiB (17% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface_7119425.png could save 1.6KiB (20% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface_7081062.png could save 1.5KiB (20% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface_7050896.png could save 1.2KiB (17% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface/newface_7202684.png could save 1.2KiB (29% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface_7050346.png could save 1.1KiB (20% reduction).
Losslessly compressing http://blog.livedoor.com/blog_portal/pc/img/noimgS.png could save 1.1KiB (62% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface_7083144.png could save 1.1KiB (11% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface_7181584.png could save 1.1KiB (18% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface_7086079.png could save 1.1KiB (18% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface/newface_7021375.png could save 940B (26% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface_7095001.png could save 940B (22% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface/newface_7193434.png could save 939B (23% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface_6836024.png could save 939B (21% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface_7095460.png could save 939B (24% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface_7146529.png could save 939B (23% reduction).
Losslessly compressing http://blog.livedoor.jp/staff/portal_banner/newface_7116853.png could save 936B (23% reduction).

priority - 24Leverage 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://blog.livedoor.com/blog_portal/lite/img/banner/select_5946944.png (expiration not specified)
http://blog.livedoor.com/blog_portal/lite/img/banner/select_6187500.png (expiration not specified)
http://blog.livedoor.com/blog_portal/lite/img/banner/select_6411595.png (expiration not specified)
http://blog.livedoor.com/blog_portal/lite/img/banner/select_6649150.png (expiration not specified)
http://blog.livedoor.com/blog_portal/lite/img/banner/select_6651747.png (expiration not specified)
http://blog.livedoor.com/blog_portal/lite/img/banner/select_6665127.png (expiration not specified)
http://blog.livedoor.com/blog_portal/lite/img/banner/select_6715510.png (expiration not specified)
http://blog.livedoor.com/blog_portal/pc/css/v2/main.css (expiration not specified)
http://blog.livedoor.com/blog_portal/pc/img/noimgS.png (expiration not specified)
http://blog.livedoor.com/blog_portal/pc/img/v2/sprite.png (expiration not specified)
http://blog.livedoor.com/js/analytics.js (expiration not specified)
http://blog.livedoor.com/js/jquery-1.7.1.min.js (expiration not specified)
http://blog.livedoor.com/js/jquery.jscrollpane.min.js (expiration not specified)
http://blog.livedoor.com/js/jquery.mousewheel.js (expiration not specified)
http://blog.livedoor.com/renewal_blog_portal/pc/js/header_image.js (expiration not specified)
http://blog.livedoor.com/renewal_blog_portal/pc/js/jquery.slides.min.js (expiration not specified)
http://connect.facebook.net/ja_JP/all.js (20 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
http://blog.livedoor.jp/staff/portal_banner/head_6918780.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/head_6946973.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/head_7017336.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/head_7050346.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/head_7053459.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/lite_select_6864617.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/lite_select_7048409.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface/newface_7021375.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface/newface_7174950.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface/newface_7193434.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface/newface_7202684.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_6797078.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_6836024.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_6968373.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7011626.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7014092.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7050346.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7050896.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7081062.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7083144.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7086079.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7095001.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7095460.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7096403.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7112257.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7116853.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7119425.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7137558.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7146529.png (60 minutes)
http://blog.livedoor.jp/staff/portal_banner/newface_7181584.png (60 minutes)
http://www.google-analytics.com/ga.js (2 hours)

priority - 14Enable 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 140.2KiB (70% reduction).

Compressing http://blog.livedoor.com/js/jquery-1.7.1.min.js could save 59.3KiB (64% reduction).
Compressing http://blog.livedoor.com/ could save 43.2KiB (77% reduction).
Compressing http://blog.livedoor.com/blog_portal/pc/css/v2/main.css could save 16.7KiB (79% reduction).
Compressing http://blog.livedoor.com/js/jquery.jscrollpane.min.js could save 9.6KiB (67% reduction).
Compressing http://blog.livedoor.com/renewal_blog_portal/pc/js/jquery.slides.min.js could save 8.5KiB (74% reduction).
Compressing http://blog.livedoor.com/renewal_blog_portal/pc/js/header_image.js could save 1.5KiB (64% reduction).
Compressing http://blog.livedoor.com/js/jquery.mousewheel.js could save 1.4KiB (60% reduction).

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

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

Remove render-blocking JavaScript:

http://blog.livedoor.com/js/jquery-1.7.1.min.js
http://blog.livedoor.com/js/jquery.mousewheel.js
http://blog.livedoor.com/js/jquery.jscrollpane.min.js
http://blog.livedoor.com/renewal_blog_portal/pc/js/jquery.slides.min.js
http://blog.livedoor.com/renewal_blog_portal/pc/js/header_image.js
http://blog.livedoor.com/js/analytics.js

Optimize CSS Delivery of the following:

http://blog.livedoor.com/blog_portal/pc/css/v2/main.css

priority - 1Minify 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 5.2KiB (25% reduction).

Minifying http://blog.livedoor.com/blog_portal/pc/css/v2/main.css could save 5.2KiB (25% reduction).

priority - 0Minify 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 3KiB (64% reduction).

Minifying http://blog.livedoor.com/renewal_blog_portal/pc/js/header_image.js could save 2KiB (83% reduction).
Minifying http://blog.livedoor.com/js/jquery.mousewheel.js could save 1.1KiB (46% reduction).

blogcms.jp Desktop Resource Breakdown

Total Resources97
Number of Hosts12
Static Resources87
JavaScript Resources11
CSS Resources1

blogcms.jp mobile page speed rank

Last tested: 2019-12-02


Mobile Speed Bad
31/100

blogcms.jp Mobile Speed Test Quick Summary


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

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

https://parts.blog.livedoor.jp/blog_portal/lite/css/v3/main.css?v=20190919

priority - 44Enable 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 434.3KiB (82% reduction).

Compressing https://parts.blog.livedoor.jp/blog_portal/lite/css/v3/main.css?v=20190919 could save 289KiB (90% reduction).
Compressing https://parts.blog.livedoor.jp/js/jquery-1.11.1.min.js could save 61.1KiB (65% reduction).
Compressing https://blog.livedoor.com/lite/ could save 42.7KiB (76% reduction).
Compressing https://parts.blog.livedoor.jp/blog_portal/lite/js/v3/main.js?v=201909021 could save 28.9KiB (76% reduction).
Compressing https://parts.blog.livedoor.jp/blog_portal/pc/js/v3/anime.min.js could save 8.2KiB (57% reduction).
Compressing https://blog.livedoor.com/blog_portal/lite/img/v3/common/logo.svg could save 3.3KiB (52% reduction).
Compressing https://blog.livedoor.com/blog_portal/lite/img/v3/common/twitter.svg could save 404B (46% reduction).
Compressing https://blog.livedoor.com/blog_portal/pc/img/v3/common/twitter.svg could save 402B (46% reduction).
Compressing https://blog.livedoor.com/blog_portal/lite/img/v3/common/facebook.svg could save 140B (30% reduction).
Compressing https://blog.livedoor.com/blog_portal/pc/img/v3/common/facebook.svg could save 138B (30% reduction).

priority - 43Avoid landing page redirects

Your page has 3 redirects. Redirects introduce additional delays before the page can be loaded.

Avoid landing page redirects for the following chain of redirected URLs.

http://blogcms.jp/
https://blogcms.jp/
https://blog.livedoor.com/
https://blog.livedoor.com/lite/

priority - 39Leverage 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:

https://blog.livedoor.com/blog_portal/lite/img/v3/common/facebook.svg (expiration not specified)
https://blog.livedoor.com/blog_portal/lite/img/v3/common/logo.svg (expiration not specified)
https://blog.livedoor.com/blog_portal/lite/img/v3/common/twitter.svg (expiration not specified)
https://blog.livedoor.com/blog_portal/pc/img/v3/common/facebook.svg (expiration not specified)
https://blog.livedoor.com/blog_portal/pc/img/v3/common/twitter.svg (expiration not specified)
https://blog.livedoor.com/blog_portal/pc/img/v3/in…ws/influencer_logo.png (expiration not specified)
https://blog.livedoor.com/blog_portal/pc/img/v3/top/info/banner.png (expiration not specified)
https://blog.livedoor.com/blog_portal/pc/img/v3/to…blog_reader_banner.png (expiration not specified)
https://common.blogimg.jp/stf/common/banner/20191122_icon.jpg (60 minutes)
https://common.blogimg.jp/stf/common/banner/20191127_icon.jpg (60 minutes)
https://common.blogimg.jp/stf/common/banner/20191129_icon.jpg (60 minutes)
https://common.blogimg.jp/stf/common/famous/20110411_reemuko.png (60 minutes)
https://common.blogimg.jp/stf/common/famous/20191031_koume_umihara.png (60 minutes)
https://common.blogimg.jp/stf/common/famous/lite_select_6651747.png (60 minutes)
https://common.blogimg.jp/stf/common/famous/lite_select_6683170.png (60 minutes)
https://common.blogimg.jp/stf/common/famous/lite_select_7331795.png (60 minutes)
https://common.blogimg.jp/stf/common/famous/lite_select_7542044_v2.png (60 minutes)
https://common.blogimg.jp/stf/common/famous/lite_select_7554525.png (60 minutes)
https://common.blogimg.jp/stf/common/famous/lite_select_7653654.png (60 minutes)
https://common.blogimg.jp/stf/common/famous/lite_select_7868235.png (60 minutes)
https://common.blogimg.jp/stf/common/famous/lite_select_7953661.png (60 minutes)
https://common.blogimg.jp/stf/common/header/20191120_kikakukiji.png (60 minutes)
https://common.blogimg.jp/stf/common/header/kikakukiji_20191122.png (60 minutes)
https://common.blogimg.jp/stf/common/header/kikakukiji_20191126.png (60 minutes)
https://common.blogimg.jp/stf/common/header/kikakukiji_20191127.png (60 minutes)
https://common.blogimg.jp/stf/common/header/kikakukiji_20191128.png (60 minutes)
https://common.blogimg.jp/stf/common/header/kikakukiji_20191128_1.png (60 minutes)
https://resize.blogsys.jp/0643718fe2642aa867944243…mgs/6/f/6f1f6689-s.png (60 minutes)
https://resize.blogsys.jp/191dba54d2e9783e685d1bd1…mgs/b/4/b4637b0c-s.jpg (60 minutes)
https://resize.blogsys.jp/22c869fdb62b3fa5d566de1f…mgs/1/f/1fe28b0a-s.jpg (60 minutes)
https://resize.blogsys.jp/248b80d9301af64b10642ecd…mgs/0/6/060aca75-s.jpg (60 minutes)
https://resize.blogsys.jp/2752dd88dc14736a3ee55736…/imgs/b/7/b799e61f.jpg (60 minutes)
https://resize.blogsys.jp/2a6c922993cf77595e2c4fff…mgs/2/2/22e43c83-s.png (60 minutes)
https://resize.blogsys.jp/2f833ff5c1530132d8f57575…mgs/4/6/465764f6-s.jpg (60 minutes)
https://resize.blogsys.jp/3e42d30058b76545ce178489…/imgs/4/7/47f0e377.jpg (60 minutes)
https://resize.blogsys.jp/469c4991b981a76f625062a7…/imgs/7/7/77be6895.png (60 minutes)
https://resize.blogsys.jp/47b44221cc555d288fc4a9ea…/imgs/c/d/cdfe871e.jpg (60 minutes)
https://resize.blogsys.jp/5303e646d9a31c2b870550da…/imgs/0/d/0db108ad.jpg (60 minutes)
https://resize.blogsys.jp/5442ae710116c65536167732…mgs/4/a/4aa9a5ee-s.jpg (60 minutes)
https://resize.blogsys.jp/55a61f208756d355cec455b5…mgs/0/5/05c1f14a-s.png (60 minutes)
https://resize.blogsys.jp/5899f42e26c68267f74236d2…mgs/b/9/b9a13f04-s.jpg (60 minutes)
https://resize.blogsys.jp/59d1a7f7179a3e9044b41e8e…mgs/2/9/298bd583-s.png (60 minutes)
https://resize.blogsys.jp/71518e4933519a1a1d4b4deb…mgs/e/8/e876ae08-s.png (60 minutes)
https://resize.blogsys.jp/7c85604e1e645b0c503dc151…mgs/f/9/f95a89a4-s.jpg (60 minutes)
https://resize.blogsys.jp/7de51173570d9cba2026aa53…/imgs/6/d/6d2f4cbd.jpg (60 minutes)
https://resize.blogsys.jp/a1b42512f10e36682bf5047d…mgs/c/3/c3c5b838-s.jpg (60 minutes)
https://resize.blogsys.jp/a4a4b2987fdd54217f8568f3…mgs/6/7/677c7f54-s.jpg (60 minutes)
https://resize.blogsys.jp/a6b10ba9fceeb07de272caa4…/imgs/0/4/04efa0f9.png (60 minutes)
https://resize.blogsys.jp/bd556df32e14c99fe6357c70…/imgs/e/a/eab83e06.jpg (60 minutes)
https://resize.blogsys.jp/d04ae8aebe8c97a1b4039b45…/imgs/c/5/c570266d.jpg (60 minutes)
https://resize.blogsys.jp/d77e8f866ee75082f332be22…mgs/5/3/53c3179b-s.jpg (60 minutes)
https://resize.blogsys.jp/e0e12c02914813dde9b1c341…mgs/5/c/5c8e9a65-s.png (60 minutes)
https://resize.blogsys.jp/efc5449695b1abfcd6e118a5…/imgs/e/6/e601b81c.jpg (60 minutes)
https://resize.blogsys.jp/f72d944157e2fc2006bd8d69…mgs/b/2/b2f6f8cd-s.jpg (60 minutes)
https://resize.blogsys.jp/fb45e067d64a7f9c18b82ff1…mgs/5/a/5a5f81e0-s.png (60 minutes)
https://d.line-scdn.net/n/_4/torimochi.js/public/v…table/min/torimochi.js (2.3 hours)

priority - 32Optimize images

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

Optimize the following images to reduce their size by 315KiB (25% reduction).

Compressing https://common.blogimg.jp/stf/common/famous/20191031_koume_umihara.png could save 45.3KiB (17% reduction).
Compressing https://common.blogimg.jp/stf/common/famous/lite_select_7542044_v2.png could save 28.8KiB (20% reduction).
Compressing https://common.blogimg.jp/stf/common/famous/20110411_reemuko.png could save 22.8KiB (15% reduction).
Compressing https://common.blogimg.jp/stf/common/famous/lite_select_7868235.png could save 21KiB (24% reduction).
Compressing https://resize.blogsys.jp/55a61f208756d355cec455b5…mgs/0/5/05c1f14a-s.png could save 20.5KiB (46% reduction).
Compressing https://common.blogimg.jp/stf/common/famous/lite_select_6683170.png could save 19.7KiB (18% reduction).
Compressing https://resize.blogsys.jp/71518e4933519a1a1d4b4deb…mgs/e/8/e876ae08-s.png could save 16.8KiB (49% reduction).
Compressing https://resize.blogsys.jp/fb45e067d64a7f9c18b82ff1…mgs/5/a/5a5f81e0-s.png could save 14.5KiB (47% reduction).
Compressing https://resize.blogsys.jp/59d1a7f7179a3e9044b41e8e…mgs/2/9/298bd583-s.png could save 14.1KiB (46% reduction).
Compressing https://common.blogimg.jp/stf/common/famous/lite_select_7554525.png could save 12.5KiB (14% reduction).
Compressing https://resize.blogsys.jp/2a6c922993cf77595e2c4fff…mgs/2/2/22e43c83-s.png could save 12.1KiB (47% reduction).
Compressing https://resize.blogsys.jp/e0e12c02914813dde9b1c341…mgs/5/c/5c8e9a65-s.png could save 11.1KiB (44% reduction).
Compressing https://blog.livedoor.com/blog_portal/pc/img/v3/top/info/banner.png could save 10.9KiB (22% reduction).
Compressing https://resize.blogsys.jp/22c869fdb62b3fa5d566de1f…mgs/1/f/1fe28b0a-s.jpg could save 7.6KiB (40% reduction).
Compressing https://resize.blogsys.jp/47b44221cc555d288fc4a9ea…/imgs/c/d/cdfe871e.jpg could save 7.4KiB (43% reduction).
Compressing https://resize.blogsys.jp/5442ae710116c65536167732…mgs/4/a/4aa9a5ee-s.jpg could save 5.4KiB (47% reduction).
Compressing https://resize.blogsys.jp/a4a4b2987fdd54217f8568f3…mgs/6/7/677c7f54-s.jpg could save 5.4KiB (48% reduction).
Compressing https://resize.blogsys.jp/bd556df32e14c99fe6357c70…/imgs/e/a/eab83e06.jpg could save 3.7KiB (46% reduction).
Compressing https://resize.blogsys.jp/a6b10ba9fceeb07de272caa4…/imgs/0/4/04efa0f9.png could save 3.4KiB (40% reduction).
Compressing https://resize.blogsys.jp/d04ae8aebe8c97a1b4039b45…/imgs/c/5/c570266d.jpg could save 3.2KiB (46% reduction).
Compressing https://resize.blogsys.jp/0643718fe2642aa867944243…mgs/6/f/6f1f6689-s.png could save 3KiB (41% reduction).
Compressing https://resize.blogsys.jp/a1b42512f10e36682bf5047d…mgs/c/3/c3c5b838-s.jpg could save 2.9KiB (40% reduction).
Compressing https://resize.blogsys.jp/7c85604e1e645b0c503dc151…mgs/f/9/f95a89a4-s.jpg could save 2.7KiB (43% reduction).
Compressing https://resize.blogsys.jp/5303e646d9a31c2b870550da…/imgs/0/d/0db108ad.jpg could save 2.6KiB (45% reduction).
Compressing https://resize.blogsys.jp/f72d944157e2fc2006bd8d69…mgs/b/2/b2f6f8cd-s.jpg could save 2.5KiB (45% reduction).
Compressing https://resize.blogsys.jp/469c4991b981a76f625062a7…/imgs/7/7/77be6895.png could save 2.5KiB (45% reduction).
Compressing https://resize.blogsys.jp/efc5449695b1abfcd6e118a5…/imgs/e/6/e601b81c.jpg could save 2.4KiB (45% reduction).
Compressing https://resize.blogsys.jp/2752dd88dc14736a3ee55736…/imgs/b/7/b799e61f.jpg could save 2.2KiB (46% reduction).
Compressing https://resize.blogsys.jp/3e42d30058b76545ce178489…/imgs/4/7/47f0e377.jpg could save 2.2KiB (41% reduction).
Compressing https://resize.blogsys.jp/191dba54d2e9783e685d1bd1…mgs/b/4/b4637b0c-s.jpg could save 1.9KiB (47% reduction).
Compressing https://resize.blogsys.jp/248b80d9301af64b10642ecd…mgs/0/6/060aca75-s.jpg could save 1.7KiB (45% reduction).
Compressing https://common.blogimg.jp/stf/common/banner/20191122_icon.jpg could save 856B (14% reduction).
Compressing https://common.blogimg.jp/stf/common/banner/20191129_icon.jpg could save 851B (13% reduction).
Compressing https://common.blogimg.jp/stf/common/banner/20191127_icon.jpg could save 685B (13% reduction).

priority - 9Minify 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 90.7KiB (29% reduction).

Minifying https://parts.blog.livedoor.jp/blog_portal/lite/css/v3/main.css?v=20190919 could save 90.7KiB (29% reduction).

priority - 1Minify 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 7.1KiB (13% reduction).

Minifying https://blog.livedoor.com/lite/ could save 7.1KiB (13% reduction).

blogcms.jp Mobile Resource Breakdown

Total Resources73
Number of Hosts9
Static Resources66
JavaScript Resources4
CSS Resources1

blogcms.jp mobile page usability

Last tested: 2019-12-02


Mobile Usability Good
98/100

blogcms.jp Mobile Usability Test Quick Summary


priority - 1Size 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://lin.ee/…7Z/ldbg/header">ライブドアブログ オブザイヤー 2019</a> is close to 1 other tap targets.

The tap target <div class="next"></div> and 5 others are close to other tap targets.

The tap target <a href="http://livedoo…s/4402487.html">「変態ごはん」レシピ必見!…グルメ漫画ブログ[li...</a> and 1 others are close to other tap targets.
The tap target <a href="https://www.am…ag=lvdrfree-22" class="link">とっておきの冷凍作りおき…青山 清美(金魚) (著)</a> and 1 others are close to other tap targets.
The tap target <a href="https://www.am…ag=lvdrfree-22" class="link">とっておきの冷凍作りおき…青山 清美(金魚) (著)</a> and 1 others are close to other tap targets.
The tap target <a href="https://www.am…ag=lvdrfree-22" class="link">とっておきの冷凍作りおき…青山 清美(金魚) (著)</a> and 1 others are close to other tap targets.
The tap target <a href="http://aoyama-kiyomi.blog.jp/">著者ブログ</a> and 1 others are close to other tap targets.
The tap target <a href="http://www.livedoor.com">livedoor</a> and 4 others are close to other tap targets.
The tap target <button type="button">閉じる</button> is close to 2 other tap targets.

blogcms.jp HTML validation

Errors

Duplicate attribute “xmlns:og”.

Line: 2 Column: - 141
".../fbml" xmlns:og="http://opengr..."

Attribute “xmlns:og” not allowed here.

Line: 2 Column: 16 - 209
"...TYPE html> <html lang="ja" xmlns:og="http://ogp.me/ns#" xmlns:mixi="http://mixi-platform.com/ns#" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:gr="http://gree.jp/ns"> <head..."

Attribute “xmlns:mixi” not allowed here.

Line: 2 Column: 16 - 209
"...TYPE html> <html lang="ja" xmlns:og="http://ogp.me/ns#" xmlns:mixi="http://mixi-platform.com/ns#" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:gr="http://gree.jp/ns"> <head..."

Attribute “xmlns:fb” not allowed here.

Line: 2 Column: 16 - 209
"...TYPE html> <html lang="ja" xmlns:og="http://ogp.me/ns#" xmlns:mixi="http://mixi-platform.com/ns#" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:gr="http://gree.jp/ns"> <head..."

Attribute “xmlns:gr” not allowed here.

Line: 2 Column: 16 - 209
"...TYPE html> <html lang="ja" xmlns:og="http://ogp.me/ns#" xmlns:mixi="http://mixi-platform.com/ns#" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:gr="http://gree.jp/ns"> <head..."

Bad value “Content-Style-Type” for attribute “http-equiv” on element “meta”.

Line: 21 Column: 1 - 57
"...r Blog"> <meta http-equiv="Content-Style-Type" content="text/css"> <meta..."

Bad value “Content-Script-Type” for attribute “http-equiv” on element “meta”.

Line: 22 Column: 1 - 65
"...ext/css"> <meta http-equiv="Content-Script-Type" content="text/javascript"> <meta..."

Bad value “handheld” for attribute “media” on element “link”: Deprecated media type “handheld”. For guidance, see the Media Types section in the current Media Queries specification.

Line: 33 Column: 1 - 102
"..."ヘルプページ"> <link rel="alternate" media="handheld" type="application/xhtml+xml" href="http://blog.m.livedoor.com"> <li..."

No space between attributes.

Line: 1012 Column: - 69
"...r-share-button"{count}>ツイート</a..."

Attribute “{count}” not allowed on element “a” at this point.

Line: 1012 Column: 5 - 76
"...</li> <li><a href="https://twitter.com/share" class="twitter-share-button"{count}>ツイート</..."

Warnings

Attribute with the local name “xmlns:og” is not serializable as XML 1.0.

Line: 2 Column: 16 - 209
"...TYPE html> <html lang="ja" xmlns:og="http://ogp.me/ns#" xmlns:mixi="http://mixi-platform.com/ns#" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:gr="http://gree.jp/ns"> <head..."

Attribute with the local name “xmlns:mixi” is not serializable as XML 1.0.

Line: 2 Column: 16 - 209
"...TYPE html> <html lang="ja" xmlns:og="http://ogp.me/ns#" xmlns:mixi="http://mixi-platform.com/ns#" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:gr="http://gree.jp/ns"> <head..."

Attribute with the local name “xmlns:fb” is not serializable as XML 1.0.

Line: 2 Column: 16 - 209
"...TYPE html> <html lang="ja" xmlns:og="http://ogp.me/ns#" xmlns:mixi="http://mixi-platform.com/ns#" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:gr="http://gree.jp/ns"> <head..."

Attribute with the local name “xmlns:gr” is not serializable as XML 1.0.

Line: 2 Column: 16 - 209
"...TYPE html> <html lang="ja" xmlns:og="http://ogp.me/ns#" xmlns:mixi="http://mixi-platform.com/ns#" xmlns:fb="http://www.facebook.com/2008/fbml" xmlns:og="http://opengraphprotocol.org/schema/" xmlns:gr="http://gree.jp/ns"> <head..."

The “contentinfo” role is unnecessary for element “footer”.

Line: 995 Column: 1 - 42
"...R-AREA--> <footer class="LyFoot" role="contentinfo"> <p cl..."

Attribute “{count}” is not serializable as XML 1.0.

Line: 1012 Column: 5 - 76
"...</li> <li><a href="https://twitter.com/share" class="twitter-share-button"{count}>ツイート</..."

blogcms.jp similar domains

Similar domains:
www.blogcms.com
www.blogcms.net
www.blogcms.org
www.blogcms.info
www.blogcms.biz
www.blogcms.us
www.blogcms.mobi
www.logcms.jp
www.blogcms.jp
www.vlogcms.jp
www.bvlogcms.jp
www.vblogcms.jp
www.glogcms.jp
www.bglogcms.jp
www.gblogcms.jp
www.hlogcms.jp
www.bhlogcms.jp
www.hblogcms.jp
www.nlogcms.jp
www.bnlogcms.jp
www.nblogcms.jp
www.bogcms.jp
www.bpogcms.jp
www.blpogcms.jp
www.bplogcms.jp
www.boogcms.jp
www.bloogcms.jp
www.bologcms.jp
www.bkogcms.jp
www.blkogcms.jp
www.bklogcms.jp
www.blgcms.jp
www.bligcms.jp
www.bloigcms.jp
www.bliogcms.jp
www.blkgcms.jp
www.blokgcms.jp
www.bllgcms.jp
www.blolgcms.jp
www.bllogcms.jp
www.blpgcms.jp
www.blopgcms.jp
www.blocms.jp
www.blofcms.jp
www.blogfcms.jp
www.blofgcms.jp
www.blovcms.jp
www.blogvcms.jp
www.blovgcms.jp
www.blotcms.jp
www.blogtcms.jp
www.blotgcms.jp
www.blobcms.jp
www.blogbcms.jp
www.blobgcms.jp
www.bloycms.jp
www.blogycms.jp
www.bloygcms.jp
www.blohcms.jp
www.bloghcms.jp
www.blohgcms.jp
www.blogms.jp
www.blogxms.jp
www.blogcxms.jp
www.blogxcms.jp
www.blogdms.jp
www.blogcdms.jp
www.blogdcms.jp
www.blogfms.jp
www.blogcfms.jp
www.blogvms.jp
www.blogcvms.jp
www.blogcs.jp
www.blogcns.jp
www.blogcmns.jp
www.blogcnms.jp
www.blogcjs.jp
www.blogcmjs.jp
www.blogcjms.jp
www.blogcks.jp
www.blogcmks.jp
www.blogckms.jp
www.blogcm.jp
www.blogcmw.jp
www.blogcmsw.jp
www.blogcmws.jp
www.blogcme.jp
www.blogcmse.jp
www.blogcmes.jp
www.blogcmd.jp
www.blogcmsd.jp
www.blogcmds.jp
www.blogcmz.jp
www.blogcmsz.jp
www.blogcmzs.jp
www.blogcmx.jp
www.blogcmsx.jp
www.blogcmxs.jp
www.blogcma.jp
www.blogcmsa.jp
www.blogcmas.jp

blogcms.jp Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


blogcms.jp TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.