Show

Blog.jp blog.jp

好きなURLは早い者勝ち!お気に入りのURLでブログライフを始めよう。登録はカンタン、もちろん無料!ブログを始めるならライブドアブログ。

Need help with your SEO?
Online Status
Offline

Server IP address resolved: No
Http response code: None
Last Checked: 09/16/2019

Blog.jp receives about four hundred thousand unique visitors and one million pageviews per day. The estimated value of blog.jp is twenty million USD. Each unique visitor makes about 3.18 pageviews on average.

Over the time blog.jp has been ranked as high as 265 in the world, while most of its traffic comes from Japan, where it reached as high as 28 position.

It’s good for blog.jp that their server is also located in Japan, as that enables the majority of their visitors to benefit from a much faster page load time.

At the time of the last check (July 04, 2019) blog.jp has an expired wildcard SSL certificate (expired on October 06, 2019).

According to Google Safe Browsing, Google Safe Search and Symantec blog.jp is quite a safe domain.

Mobile-Friendly test indicates that blog.jp is well optimized for mobile and tablet devices.

Global Rank
524
Average Load Time
1.09sec
Links In Count
15,189
Website Value
$17.2 M
Overview
Last Updated: 10/16/2019
Overall result - "blog.jp" is SAFE.
We gather website safety and reputation data and compare it with available third-party sources so we calculate own safety and trustworthiness rate based on information that we get.
Norton Connect Safe
Last Updated: 01/12/2019
NCS "blog.jp" OK.

Norton ConnectSafe evaluates blog.jp for any unsafe and insecure content. The results are critical for families with young children.

Google Safe Search
Last Updated: 10/10/2016
GSS "blog.jp" OK.

SafeSearch is used as a parental control tool to filter out any inappropriate for your children search results on your devices: phones, tablets or personal computers.

Google Safe Browsing
Last Updated: 02/18/2019
Malware not found at "blog.jp".
"blog.jp" is not a phishing page.
"blog.jp" does not install unwanted software.
"blog.jp" does not contain harmfull applications.
Google Safe Browsing notifies when websites are compromised by malicious actors. These protections work across Google products and provide a safer online experience.
Site Advisor
Last Updated: 01/09/2019
SA "blog.jp" OK.

McAfee assesses blog.jp for a meaningful set of security threats. Featured dangers from annoying pop-ups to hidden Trojans, that can steal your identity, will be revealed. McAfee does not analyze blog.jp for mature or inappropriate content, only security checks are evaluated.

Web of Trust
Last Updated: 10/16/2019
WOT "blog.jp" UNKNOWN.

The WOT calculates reputation of the blog.jp. This reputation system receives ratings from users and information from third-party sources, assesses the blog.jp for safety features and confirms, whether blog.jp is suitable for children.

SSL Information
Domain *.blog.livedoor.com
Issuer GlobalSign Organization Validation CA - SHA256 - G2
Algorithm RSA-SHA256
Valid form 10/05/2018
Expiration 10/06/2019
Signed Certificate is not self signed
Additional Domains *.blog.livedoor.com
blog.livedoor.com
Server Location
Tokyo
Tokyo
Japan
ASN Information

ASN ID: 38631
ASN Title: LINE LINE Corporation, JP

Last Update: 05/29/2019

% [whois.apnic.net]
% Whois data copyright terms http://www.apnic.net/db/dbcopyright.html

% Information related to 'AS37888 - AS38911'

as-block: AS37888 - AS38911
descr: APNIC ASN block
remarks: These AS numbers are further assigned by APNIC
remarks: to APNIC members and end-users in the APNIC region
admin-c: HM20-AP
tech-c: HM20-AP
mnt-by: APNIC-HM
mnt-lower: APNIC-HM
last-modified: 2009-09-29T06:04:16Z
source: APNIC

role: APNIC Hostmaster
address: 6 Cordelia Street
address: South Brisbane
address: QLD 4101
country: AU
phone: +61 7 3858 3100
fax-no: +61 7 3858 3199
e-mail: helpdesk@apnic.net
admin-c: AMS11-AP
tech-c: AH256-AP
nic-hdl: HM20-AP
remarks: Administrator for APNIC
notify: hostmaster@apnic.net
mnt-by: MAINT-APNIC-AP
last-modified: 2013-10-23T04:06:51Z
source: APNIC

% Information related to 'AS38627 - AS38656'

as-block: AS38627 - AS38656
descr: JPNIC-2Byte-ASBLOCK-AP
descr: for assignment to JPNIC members
country: JP
admin-c: JNIC1-AP
tech-c: JNIC1-AP
remarks: Authoritative information regarding AS Number
remarks: assignments made from within this block can be
remarks: queried at whois.nic.ad.jp. To only display English output,
remarks: add '/e' at the end of command,
remarks: e.g. 'whois -h whois.nic.ad.jp xxx/e'.
mnt-by: APNIC-HM
mnt-lower: MAINT-JPNIC
last-modified: 2009-11-19T01:11:45Z
source: APNIC

role: Japan Network Information Center
address: Urbannet-Kanda Bldg 4F
address: 3-6-2 Uchi-Kanda
address: Chiyoda-ku, Tokyo 101-0047,Japan
country: JP
phone: +81-3-5297-2311
fax-no: +81-3-5297-2312
e-mail: hostmaster@nic.ad.jp
admin-c: JI13-AP
tech-c: JE53-AP
nic-hdl: JNIC1-AP
mnt-by: MAINT-JPNIC
last-modified: 2012-08-28T07:58:02Z
source: APNIC

% Information related to 'AS38631'

aut-num: AS38631
as-name: LINE
descr: LINE Corporation
import: from AS2914 100 accept ANY
import: from AS2516 100 accept ANY
import: from AS2497 100 accept ANY
import: from AS23576 100 accept ANY
export: to AS2914 announce AS38631
export: to AS2516 announce AS38631
export: to AS2497 announce AS38631
export: to AS23576 announce AS38631
country: JP
admin-c: JP00034420
tech-c: JP00034420
last-modified: 2015-07-16T23:01:27Z
source: JPNIC

% This query was served by the APNIC Whois Service version 1.88.15-46 (WHOIS-US4)

HTML Metatags
Title
blog.jp
The title is too short, it may not provide search engines and users with enough information to understand the relevancy of your page. You should try to keep the length of the title somewhere between at least 10 characters and 70 characters.
Description
好きなURLは早い者勝ち!お気に入りのURLでブログライフを始めよう。登録はカンタン、もちろん無料!ブログを始めるならライブドアブログ。
The description is too short. If a description is too short, the search engines may add text found elsewhere on the page. Note that search engines may show a different description from the one you have authored if they feel it may be more relevant to a user's search.
Encoding
UTF-8
You should always specify the encoding used for an HTML page. If you don't, you risk that characters in your content are incorrectly interpreted. This is not just an issue of human readability, increasingly machines need to understand your data too.
Language
ja Japanese
Identifying the language of your content allows you to automatically do a number of things, from changing the look and behavior of a page, to assisting search engines in extracting information. If part of the page uses text in a different language, you can add a language attribute with a different value to the element that surrounds that content.
Language Region
Not Found
Images
Attribute ALT
Success, no any <img> without defined ALT attribute. Alt text is helpful to end users if they have images disabled or if the image does not properly load.
As a general rule, search engines do not interpret the content of image files. The text provided in the <img alt> attribute enables the site owner to provide relevant information to the search engine and to the end user.
H1-H6 Tags Information

For search engines, <H> tags helps understand the structure of the text on a page better. For users, headings are like anchors in a wall of text, navigating them through the page and making it easier to digest. The <h1> tag reinforces the core keyword(s) found in the <title>, <description>, and the <body>. We recommend that the <h1> tag includes keywords that reflect the contents of the page and that it is not longer than 150 characters in length, but don’t overuse the tags and the keywords in them. Keep it readable for users.

H1
Line 170, ...<h1>どれも無料。ブログ作成後に変更も可能です。</h1>...
Your H1 introduces the topic your page is all about, just as a title tells a reader what a book is all about. Remove redundant H1 tags from the page source, so that only one H1 tag exists.
H2
The H2s are akin to book chapters, describing the main topics you’ll cover in sections of the article.
H3
Subsequent headers, H3s to H6s, serve as additional sub-headings within each section, just as a book chapter may be split up by multiple sub-topics.
H4
H5
H6
Iframes Information
iFrame
Line 138, ...<iframe src="//www.facebook.com/plugins/like.php?href=http%3A%2F%...
Since search engines consider the content in iframes to belong to another website, the best you can hope for is no effect on SEO. Iframes tend to neither help nor hurt your search engine ranking. For this reason, it’s best to refrain from using iframes on main pages that you want to rank high in search engine results. Instead, fill high-priority pages with useful, unique content and save iframes for other pages.
Code To Text Ratio
Code To Text Ratio
5.80 %
A good code to text ratio is anywhere from 25 to 70 percent. This percentage refers to the visible text ratio, as opposed to HTML elements, image tags and other non-visible information. This has become especially apparent since search engines, such as Google, released the Panda update which placed importance on content-driven sites.
Favicons

Favicons are the little piece of graphic that represents your brand on browser tabs, bookmark lists, search history, search ads and even search results. These files are placed in a file called favicon.ico and placed in the root directory of a website. There are no direct SEO effects of having favicons. However, there may be indirect benefits such as increased usability of site and bookmarks. It makes your website look more professional and help a users to remember your site while browsing through multiple URLs. If you want to get mentioned benefits you have to specify icons for different web browsers and sometimes even for different mobiles.

Default Favicon
default, favicon.ico
Backup icon for most desktop browsers (if no icon of the right size is found). Tag format <link rel="shortcut icon" href="path-to-16x16-icon.ico" type="image/x-icon" />
16x16 Optional Favicon
Standard icon for outdated browsers or small resolution hand held devices. Tag format <link rel="icon" type="image/png" sizes="16x16" href="path-to-16x16.png">
32x32 Optional Favicon
Standard for most desktop browsers. Tag format <link rel="icon" sizes="32x32" href="path-to-32x32.png">
96x96 Optional Favicon
Mostly used as GoogleTV icon. Tag format <link rel="icon" type="image/png" sizes="96x96" href="path-to-96x96.png">
Default Apple Icon
Backup icon for apple devices (if no icon of the right size is found). Preferrable size 60x60. Tag format <link rel="apple-touch-icon" sizes="72x72" href="path-to-small-icon.png">
180x180 Apple Icon
iPhone 6 plus icons. Tag format <link rel="apple-touch-icon" sizes="180x180" href="path-to-180x180.png">
152x152 Apple Icon
iPad, iPad mini icons. Tag format <link rel="apple-touch-icon" sizes="152x152" href="path-to-icon-152x152.png">
167x167 Apple Icon
iPad Pro icon. Tag format <link rel="apple-touch-icon" sizes="167x167" href="path-to-167x167.png">
Robots.txt Information

Robots.txt is a text file that website owners can create to tell search engine bots how to crawl and index pages on their site.

Robots File
Robots File Loaded successfully (/robots.txt)
You can have multiple lines of instructions to allow or disallow specific URLs and add multiple sitemaps. If you do not disallow a URL, then search engine bots assume that they are allowed to crawl it.
Disallow
39 record(s)
Other User-Agent
Not found
Default User-Agent
1 record(s)
Sitemap

A sitemap is an XML file where is provided information about each URL: when it was last updated, how often it changes, and how important it is in relation to other URLs in the site. Search engines crawling bots read this file to more efficiently and intelligently crawl your site and to find URLs that may be isolated from rest of the site's content.

Default Sitemap
Sitemap File Loaded successfully (/sitemap.xml)
Using a sitemap doesn't guarantee that all the items in your sitemap will be crawled and indexed, however, your site will benefit from having a sitemap.
WHOIS

[ 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] BLOG.JP

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

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

[登録年月日] 2003/03/01
[有効期限] 2020/03/31
[状態] Active
[最終更新] 2019/07/19 16:47:56 (JST)

Contact Information: [公開連絡窓口]
[名前] LINE株式会社
[Name] LINE Corporation
[Email] dl_livedoor_support@linecorp.com
[Web Page] https://contact-cc.line.me/livedoor/
[郵便番号] 812-0012
[住所] 福岡県福岡市博多区博多駅中央街8-1
JRJP博多ビル12F
LINE株式会社 livedoorお客様サポートセンター
[Postal Address] 1-1 Hakataekichuogai, Hakata-ku, Fukuoka-shi
12F JRJP Hakata Bldg.
LINE Corporation Livedoor Customer Support Center
[電話番号] 03-4589-3900
[FAX番号]

DNS Records
HostA RecordTTL
blog.jp203.104.150.138300
HostMX RecordPriorityTTL
HostNS RecordTTL
blog.jpns1.naver.jp3600
blog.jpns2.naver.jp3600
HostTXT RecordTTL

ns1.naver.jp
TTL: 3600
Email address: domain.linecorp.com
Serial: 2019040900
Refresh: 10800
Retry: 3600
Expire: 604800
Minimum: 3600

Errors
Line: 2 Column: - 141
".../fbml" xmlns:og="http://opengr..."
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..."
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..."
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..."
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..."
Line: 21 Column: 1 - 57
"...r Blog"> <meta http-equiv="Content-Style-Type" content="text/css"> <meta..."
Line: 22 Column: 1 - 65
"...ext/css"> <meta http-equiv="Content-Script-Type" content="text/javascript"> <meta..."
Line: 30 Column: 1 - 102
"..."ヘルプページ"> <link rel="alternate" media="handheld" type="application/xhtml+xml" href="http://blog.m.livedoor.com"> <lin..."
Line: 138 Column: 20 - 365
"...lass="fb"><iframe src="//www.facebook.com/plugins/like.php?href=http%3A%2F%2Fblog.livedoor.com%2Flp%2Fblogjp&amp;width=100&amp;height=21&amp;colorscheme=light&amp;layout=button_count&amp;action=like&amp;show_faces=false&amp;send=false" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:100px; height:21px;" allowTransparency="true"></ifra..."
Line: 138 Column: 20 - 365
"...lass="fb"><iframe src="//www.facebook.com/plugins/like.php?href=http%3A%2F%2Fblog.livedoor.com%2Flp%2Fblogjp&amp;width=100&amp;height=21&amp;colorscheme=light&amp;layout=button_count&amp;action=like&amp;show_faces=false&amp;send=false" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:100px; height:21px;" allowTransparency="true"></ifra..."
Line: 138 Column: 20 - 365
"...lass="fb"><iframe src="//www.facebook.com/plugins/like.php?href=http%3A%2F%2Fblog.livedoor.com%2Flp%2Fblogjp&amp;width=100&amp;height=21&amp;colorscheme=light&amp;layout=button_count&amp;action=like&amp;show_faces=false&amp;send=false" scrolling="no" frameborder="0" style="border:none; overflow:hidden; width:100px; height:21px;" allowTransparency="true"></ifra..."
Line: 162 Column: 25 - 86
"...l">http://<input type="textbox" class="subdomain" id="blogjp-subdomain">.blog...."
Line: 187 Column: 5 - 20
"... <dl> <dd class="new">blog.j..."
Warnings
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..."
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..."
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..."
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..."

Last tested: 05/26/2017

Desktop
Desktop Speed
63%
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 344.6KiB (77% reduction).

Compressing http://blog.jp/blog_portal/pc/css/blog_portal.css?v=20130718 could save 153.1KiB (86% reduction).
Compressing http://blog.jp/blog_portal/pc/js/app.js?v=20130416 could save 63.7KiB (77% reduction).
Compressing http://blog.jp/js/jquery-1.7.1.min.js could save 59.3KiB (64% reduction).
Compressing http://blog.jp/blog_portal/pc/js/handlebars-1.0.0.beta.6.js could save 36.2KiB (74% reduction).
Compressing http://blog.jp/js/jquery.jscrollpane.min.js could save 9.6KiB (67% reduction).
Compressing http://blog.jp/ could save 6.3KiB (63% reduction).
Compressing http://blog.jp/blog_portal/pc/js/jquery.easing.1.3.js could save 6KiB (75% reduction).
Compressing http://blog.jp/blog_portal/pc/css/blog_portal_lp_blogjp.css?v=20150618 could save 4.3KiB (74% reduction).
Compressing https://platform.twitter.com/js/button.fbaa419ee3b1f63d563b4dc1677c1aa4.js could save 2.8KiB (65% reduction).
Compressing http://blog.jp/blog_portal/pc/css/jscroll.css could save 2KiB (69% reduction).
Compressing http://blog.jp/js/jquery.mousewheel.js could save 1.4KiB (60% reduction).

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.jp/blog_portal/pc/css/jscroll.css (expiration not specified)
http://blog.jp/blog_portal/pc/img/lp/blogjp/bg_Heading.png (expiration not specified)
http://blog.jp/blog_portal/pc/img/lp/blogjp/bg_HeadingInner.png (expiration not specified)
http://blog.jp/blog_portal/pc/img/lp/blogjp/btn_submit.png (expiration not specified)
http://blog.jp/blog_portal/pc/img/lp/blogjp/btn_submit_disable.png (expiration not specified)
http://blog.jp/blog_portal/pc/img/lp/blogjp/icon_acquire.png (expiration not specified)
http://blog.jp/blog_portal/pc/img/lp/blogjp/icon_link.png (expiration not specified)
http://blog.jp/blog_portal/pc/img/lp/blogjp/icon_notacquire.png (expiration not specified)
http://blog.jp/blog_portal/pc/img/lp/blogjp/icon_search.gif (expiration not specified)
http://blog.jp/blog_portal/pc/img/lp/blogjp/icon_unacquired.png (expiration not specified)
http://blog.jp/blog_portal/pc/img/lp/blogjp/txt_Heading.png (expiration not specified)
http://blog.jp/blog_portal/pc/img/lp/welcome/bg_globalHeader.png (expiration not specified)
http://blog.jp/blog_portal/pc/js/handlebars-1.0.0.beta.6.js (expiration not specified)
http://blog.jp/blog_portal/pc/js/jquery.easing.1.3.js (expiration not specified)
http://blog.jp/js/analytics.js (expiration not specified)
http://blog.jp/js/jquery-1.7.1.min.js (expiration not specified)
http://blog.jp/js/jquery.jscrollpane.min.js (expiration not specified)
http://blog.jp/js/jquery.mousewheel.js (expiration not specified)
http://platform.twitter.com/widgets.js (30 minutes)
https://apis.google.com/js/plusone.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://cdn-ak.b.st-hatena.com/js/bookmark_button.js (6.4 hours)

Your page has 7 blocking script resources and 3 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://blog.jp/js/jquery-1.7.1.min.js
http://blog.jp/js/jquery.mousewheel.js
http://blog.jp/js/jquery.jscrollpane.min.js
http://blog.jp/blog_portal/pc/js/jquery.easing.1.3.js
http://blog.jp/blog_portal/pc/js/handlebars-1.0.0.beta.6.js
http://blog.jp/blog_portal/pc/js/app.js?v=20130416
http://blog.jp/js/analytics.js

Optimize CSS Delivery of the following:

http://blog.jp/blog_portal/pc/css/blog_portal.css?v=20130718
http://blog.jp/blog_portal/pc/css/jscroll.css
http://blog.jp/blog_portal/pc/css/blog_portal_lp_blogjp.css?v=20150618

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 41.7KiB (28% reduction).

Minifying http://blog.jp/blog_portal/pc/js/app.js?v=20130416 could save 22.4KiB (28% reduction).
Minifying http://blog.jp/blog_portal/pc/js/handlebars-1.0.0.beta.6.js could save 12KiB (25% reduction).
Minifying http://blog.jp/blog_portal/pc/js/jquery.easing.1.3.js could save 4.4KiB (55% reduction).
Minifying http://cdn-ak.b.st-hatena.com/js/bookmark_button.js could save 1.9KiB (22% reduction) after compression.
Minifying http://blog.jp/js/jquery.mousewheel.js could save 1.1KiB (46% reduction).

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 26KiB (15% reduction).

Minifying http://blog.jp/blog_portal/pc/css/blog_portal.css?v=20130718 could save 24.5KiB (14% reduction).
Minifying http://blog.jp/blog_portal/pc/css/blog_portal_lp_blogjp.css?v=20150618 could save 834B (15% reduction).
Minifying http://blog.jp/blog_portal/pc/css/jscroll.css could save 664B (23% reduction).

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 1.6KiB (16% reduction).

Minifying http://blog.jp/ could save 1.6KiB (16% reduction).

Desktop Resource Breakdown
Total Resources49
Number of Hosts13
Static Resources36
JavaScript Resources20
CSS Resources5

Last tested: 05/26/2017

Mobile
Mobile Usability
100%
Mobile Speed
60%
Your page has 3 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://blog.jp/js/jquery-1.7.1.min.js
http://blog.jp/blog_portal/lite/js/handlebars-1.0.rc.1.js
http://blog.jp/blog_portal/lite/js/app.js

Optimize CSS Delivery of the following:

http://blog.jp/blog_portal/lite/css/blog_portal.css?v=20130719
http://blog.jp/blog_portal/lite/css/lp_blogjp.css

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 208.4KiB (71% reduction).

Compressing http://blog.jp/blog_portal/lite/css/blog_portal.css?v=20130719 could save 80.9KiB (76% reduction).
Compressing http://blog.jp/js/jquery-1.7.1.min.js could save 59.3KiB (64% reduction).
Compressing http://blog.jp/blog_portal/lite/js/handlebars-1.0.rc.1.js could save 45.7KiB (75% reduction).
Compressing http://blog.jp/blog_portal/lite/js/app.js could save 10KiB (72% reduction).
Compressing http://blog.jp/blog_portal/lite/css/lp_blogjp.css could save 7.3KiB (76% reduction).
Compressing http://blog.jp/lite/ could save 4.2KiB (60% reduction).
Compressing http://blog.jp/blog_portal/lite/js/canvasSpinner.js could save 1.1KiB (59% reduction).

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.jp/blog_portal/lite/css/lp_blogjp.css (expiration not specified)
http://blog.jp/blog_portal/lite/img/lp/blogjp/bg_Heading.png (expiration not specified)
http://blog.jp/blog_portal/lite/img/lp/blogjp/btn.png (expiration not specified)
http://blog.jp/blog_portal/lite/img/lp/blogjp/icon_acquire.png (expiration not specified)
http://blog.jp/blog_portal/lite/img/lp/blogjp/icon_link.png (expiration not specified)
http://blog.jp/blog_portal/lite/img/lp/blogjp/icon_new.png (expiration not specified)
http://blog.jp/blog_portal/lite/img/lp/blogjp/icon_notacquire.png (expiration not specified)
http://blog.jp/blog_portal/lite/img/lp/blogjp/icon_unacquired.png (expiration not specified)
http://blog.jp/blog_portal/lite/img/lp/blogjp/txt_Heading.png (expiration not specified)
http://blog.jp/blog_portal/lite/js/app.js (expiration not specified)
http://blog.jp/blog_portal/lite/js/canvasSpinner.js (expiration not specified)
http://blog.jp/blog_portal/lite/js/handlebars-1.0.rc.1.js (expiration not specified)
http://blog.jp/js/jquery-1.7.1.min.js (expiration not specified)
http://platform.twitter.com/widgets.js (30 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

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 24.8KiB (33% reduction).

Minifying http://blog.jp/blog_portal/lite/js/handlebars-1.0.rc.1.js could save 19.6KiB (33% reduction).
Minifying http://blog.jp/blog_portal/lite/js/app.js could save 4.7KiB (35% reduction).
Minifying http://blog.jp/blog_portal/lite/js/canvasSpinner.js could save 528B (27% reduction).

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 16.4KiB (15% reduction).

Minifying http://blog.jp/blog_portal/lite/css/blog_portal.css?v=20130719 could save 11.9KiB (12% reduction).
Minifying http://blog.jp/blog_portal/lite/css/lp_blogjp.css could save 4.5KiB (48% reduction).

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 940B (14% reduction).

Minifying http://blog.jp/lite/ could save 940B (14% reduction).

Mobile Resource Breakdown
Total Resources26
Number of Hosts6
Static Resources18
JavaScript Resources8
CSS Resources2
www.blog.com
www.blog.net
www.blog.org
www.blog.info
www.blog.biz
www.blog.us
www.blog.mobi
www.log.jp
www.blog.jp
www.vlog.jp
www.bvlog.jp
www.vblog.jp
www.glog.jp
www.bglog.jp
www.gblog.jp
www.hlog.jp
www.bhlog.jp
www.hblog.jp
www.nlog.jp
www.bnlog.jp
www.nblog.jp
www.bog.jp
www.bpog.jp
www.blpog.jp
www.bplog.jp
www.boog.jp
www.bloog.jp
www.bolog.jp
www.bkog.jp
www.blkog.jp
www.bklog.jp
www.blg.jp
www.blig.jp
www.bloig.jp
www.bliog.jp
www.blkg.jp
www.blokg.jp
www.bllg.jp
www.blolg.jp
www.bllog.jp
www.blpg.jp
www.blopg.jp
www.blo.jp
www.blof.jp
www.blogf.jp
www.blofg.jp
www.blov.jp
www.blogv.jp
www.blovg.jp
www.blot.jp
www.blogt.jp
www.blotg.jp
www.blob.jp
www.blogb.jp
www.blobg.jp
www.bloy.jp
www.blogy.jp
www.bloyg.jp
www.bloh.jp
www.blogh.jp
www.blohg.jp