Show

Hateblo.jp はてなブログ

はてなブログは、無料でしっかり書けるブログサービスです。日々の生活から感じたこと、考えたことを書き残しましょう。

Need help with your SEO?
Online Status
Offline

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

Hateblo.jp receives about one hundred thousand unique visitors and two hundred thousand pageviews per day. The estimated value of hateblo.jp is two million USD. Each unique visitor makes about 1.36 pageviews on average.

Over the time hateblo.jp has been ranked as high as 1,220 in the world, while most of its traffic comes from Japan, where it reached as high as 285 position.

It’s good for hateblo.jp that their hosting company AMAZON-02 - Amazon.com, Inc., US server is also located in Japan, as that enables the majority of their visitors to benefit from a much faster page load time. See the list of other websites hosted by AMAZON-02 - Amazon.com, Inc., US.

Hateblo.jp is registered under .JP top-level domain. Check other websites in .JP zone.

At the time of the last check (November 12, 2019) hateblo.jp has an invalid SSL certificate.

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

Mobile-Friendly test indicates that hateblo.jp is well optimized for mobile and tablet devices, however website page loading time could be improved.

Global Rank
4,343
Average Load Time
1.42sec
Links In Count
7,050
Website Value
$2.1 M
Overview
Last Updated: 11/12/2019
Overall result - "hateblo.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 "hateblo.jp" OK.

Norton ConnectSafe evaluates hateblo.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 "hateblo.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: 01/09/2019
Malware not found at "hateblo.jp".
"hateblo.jp" is not a phishing page.
"hateblo.jp" does not install unwanted software.
"hateblo.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 "hateblo.jp" OK.

McAfee assesses hateblo.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 hateblo.jp for mature or inappropriate content, only security checks are evaluated.

Web of Trust
Last Updated: 11/12/2019
WOT "hateblo.jp" UNKNOWN.

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

SSL Information
WARNING! Certificate download error. Previous scan results are shown below.
Domain Unknown
Issuer Organization Unknown
Issuer Unknown
Algorithm Unknown
Valid form Unknown
Expiration Unknown
Signed No information
Additional Domains
Server Location
Tokyo
Tokyo
Japan
ASN Information

ASN ID: 16509
ASN Title: AMAZON-02 - Amazon.com, Inc., US

Last Update: 05/30/2019

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

ASNumber: 16509
ASName: AMAZON-02
ASHandle: AS16509
RegDate: 2000-05-03
Updated: 2012-03-02
Ref: https://rdap.arin.net/registry/autnum/16509

OrgName: Amazon.com, Inc.
OrgId: AMAZON-4
Address: 1918 8th Ave
City: SEATTLE
StateProv: WA
PostalCode: 98101-1244
Country: US
RegDate: 1995-01-23
Updated: 2017-01-28
Ref: https://rdap.arin.net/registry/entity/AMAZON-4

OrgAbuseHandle: AEA8-ARIN
OrgAbuseName: Amazon EC2 Abuse
OrgAbusePhone: +1-206-266-4064
OrgAbuseEmail: abuse@amazonaws.com
OrgAbuseRef: https://rdap.arin.net/registry/entity/AEA8-ARIN

OrgTechHandle: ANO24-ARIN
OrgTechName: Amazon EC2 Network Operations
OrgTechPhone: +1-206-266-4064
OrgTechEmail: amzn-noc-contact@amazon.com
OrgTechRef: https://rdap.arin.net/registry/entity/ANO24-ARIN

RTechHandle: AC6-ORG-ARIN
RTechName: Amazon-com Incorporated
RTechPhone: +1-206-266-2187
RTechEmail: ipmanagement@amazon.com
RTechRef: https://rdap.arin.net/registry/entity/AC6-ORG-ARIN

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#

HTML Metatags
Title
はてなブログ
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
はてなブログは、無料でしっかり書けるブログサービスです。日々の生活から感じたこと、考えたことを書き残しましょう。
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
Line 1250, ...<img src="https://aff.gnavi.co.jp/images/track/cer.jpg?cid=704bae...
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 147, ...<h1> <a href="https://hatenablog.com/"> ...
Your H1 introduces the topic your page is all about, just as a title tells a reader what a book is all about.
H2
5 H2 tag(s).
The H2s are akin to book chapters, describing the main topics you’ll cover in sections of the article.
H3
5 H3 tag(s).
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
5 H4 tag(s).
H5
H6
Iframes Information
iFrame
Line 140, ...<iframe id="globalheader" height="37" frameborder="0" allowtransp...
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.99 %
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
Line 67, https://cdn.blog.st-hatena.com/images/favicon.ico?version=3fb866e995c13b5fc24055535557cd7c5c1f78a3&env=production
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
Line 71, https://cdn.blog.st-hatena.com/images/touch-icon-ipad-retina.png?version=3a65594036f7199cde7fc99eb86f965d42c0bc47&env=production
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
5 record(s)
Other User-Agent
1 record(s)
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 failed Loaded (/sitemap.xml)
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] HATEBLO.JP

[登録者名] 株式会社はてな
[Registrant] Hatena Co., Ltd.

[Name Server] ns-77.awsdns-09.com
[Name Server] ns-1705.awsdns-21.co.uk
[Name Server] ns-1491.awsdns-58.org
[Name Server] ns-786.awsdns-34.net
[Signing Key]

[登録年月日] 2011/10/17
[有効期限] 2019/10/31
[状態] Active
[最終更新] 2018/11/01 01:05:13 (JST)

Contact Information: [公開連絡窓口]
[名前] Whois情報公開代行サービス by バリュードメイン
[Name] Whois Privacy Protection Service by VALUE-DOMAIN
[Email] whoisproxy@value-domain.com
[Web Page] https://www.value-domain.com/
[郵便番号] 530-0011
[住所] 大阪府大阪市北区大深町3-1
グランフロント大阪 タワーB 23階
[Postal Address]
[電話番号] 06-7634-2727
[FAX番号] 06-6374-0121

DNS Records
HostA RecordTTL
hateblo.jp13.112.159.22660
hateblo.jp52.69.186.24360
HostMX RecordPriorityTTL
hateblo.jpmailinbound.hatena.ne.jp103600
HostNS RecordTTL
hateblo.jpns-1491.awsdns-58.org3600
hateblo.jpns-1705.awsdns-21.co.uk3600
hateblo.jpns-77.awsdns-09.com3600
hateblo.jpns-786.awsdns-34.net3600
HostTXT RecordTTL
hateblo.jpgoogle-site-verification=MsMUlK1_6JrS8pKVmT7i_VjAD9a0GpO3zPG2fVsnEzQ86400

ns-77.awsdns-09.com
TTL: 900
Email address: awsdns-hostmaster.amazon.com
Serial: 1
Refresh: 7200
Retry: 900
Expire: 1209600
Minimum: 86400

Errors
Line: 126 Column: 3 - 81
"... > <iframe id="globalheader" height="37" frameborder="0" allowTransparency="true"></ifra..."
Line: 126 Column: 3 - 81
"... > <iframe id="globalheader" height="37" frameborder="0" allowTransparency="true"></ifra..."
Line: 965 Column: 7 - 41
"...s"> <h3 class="footer-address-heading">アプリでいつ..."
Line: 971 Column: 101 - 190
"...="_blank"><img src="/images/banner/google-play-badge.png" height="40px" alt="Get it on Google Play"></a> ..."
Line: 989 Column: 1 - 9
"...plicit" } </script> <scri..."
Line: 1044 Column: 5 - 149
"... <img src="http://aff.gnavi.co.jp/images/track/cer.jpg?cid=704bae354439d53a25ff20a52efda2ff040459438717ea7e1828277439987832" style="display:none"> </b..."
Warnings
Line: 412 Column: 9 - 46
"... <section class="serviceTop-promotion"> ..."
Line: 898 Column: 5 - 56
"...ion> <section class="serviceTop-socialAccount-secondary"> ..."

Last tested: 06/13/2016

Desktop
Desktop Speed
66%
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 189.2KiB (33% reduction).

Losslessly compressing http://cdn.image.st-hatena.com/image/square/a54188…7%2F20160607160525.jpg could save 29.8KiB (40% reduction).
Losslessly compressing http://cdn.image.st-hatena.com/image/square/2adf4e…2%2F20160602190253.jpg could save 27.6KiB (40% reduction).
Losslessly compressing http://cdn.image.st-hatena.com/image/square/949607…2%2F20160612154656.jpg could save 24KiB (25% reduction).
Losslessly compressing http://cdn.image.st-hatena.com/image/square/42ba9a…7%2F20160607232755.jpg could save 19KiB (31% reduction).
Losslessly compressing http://cdn.image.st-hatena.com/image/square/868064…4%2F20160604152426.jpg could save 11KiB (35% reduction).
Compressing and resizing http://hatenablog.com/images/banner/blog-staffblog-banner.gif could save 4.6KiB (17% reduction).
Losslessly compressing https://static.xx.fbcdn.net/rsrc.php/v2/yl/r/exzGWwKEETI.png could save 4.5KiB (36% reduction).
Compressing and resizing http://hatenablog.com/images/banner/blog-blog-banner.gif could save 4.2KiB (39% reduction).
Losslessly compressing http://hatenablog.com/images/banner/google-play-banner-45-en.png could save 3.8KiB (48% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/ho/holdupdownn/profile.gif could save 3.4KiB (80% reduction).
Losslessly compressing http://hatenablog.com/images/banner/banner-ios-app-v3.jpg could save 3.1KiB (11% reduction).
Losslessly compressing http://cdn.mogile.archive.st-hatena.com/v1/image/h…297787643747682600.gif could save 3KiB (13% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/ni/nishimurazill/profile.gif could save 2.9KiB (77% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/go/goryokyoki/profile.gif could save 2.9KiB (77% reduction).
Losslessly compressing http://cdn.image.st-hatena.com/image/square/f8fb5b…297787643751636513.gif could save 2.7KiB (40% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/ci/citmb/profile.gif could save 2.6KiB (76% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/ak/akisan0413/profile.gif could save 2.6KiB (76% reduction).
Losslessly compressing http://cdn.image.st-hatena.com/image/scale/34c1192…297797187731478486.png could save 2.5KiB (11% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/wa/waspossible/profile.gif could save 2.3KiB (73% reduction).
Compressing and resizing http://hatenablog.com/images/circle/official-circl…imation-and-comics.gif could save 2.1KiB (78% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/mo/moi_moi/profile.gif could save 1.9KiB (74% reduction).
Losslessly compressing http://hatenablog.com/images/banner/pro_banner3_rectangle.gif could save 1.8KiB (16% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/ca/canon321/profile.gif could save 1.7KiB (81% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/kp/kpw/profile.gif could save 1.7KiB (81% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/sa/sapporance/profile.gif could save 1.7KiB (81% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/ty/tyorontyo/profile.gif could save 1.7KiB (81% reduction).
Compressing and resizing http://hatenablog.com/images/circle/official-circle-icon/sports.gif could save 1.6KiB (55% reduction).
Losslessly compressing http://cdn.image.st-hatena.com/image/square/a0df1a…42146.png%3F1464585733 could save 1.6KiB (17% reduction).
Compressing and resizing http://hatenablog.com/images/circle/official-circle-icon/entertainment.gif could save 1.6KiB (70% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/so/soranaka004/profile.gif could save 1.6KiB (69% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/im/imacky/profile.gif could save 1.4KiB (62% reduction).
Compressing and resizing http://hatenablog.com/images/circle/official-circle-icon/showbiz.gif could save 1.4KiB (62% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/ne/neverdespair7/profile.gif could save 1.3KiB (62% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/Mc/McG/profile.gif could save 1.1KiB (66% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/na/namakero4/profile.gif could save 1KiB (56% reduction).
Losslessly compressing http://hatenablog.com/images/banner/Download_on_th…Badge_US-UK_135x40.png could save 1,022B (43% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/ji/jinsan77/profile.gif could save 1,001B (57% reduction).
Losslessly compressing http://cdn.image.st-hatena.com/image/square/e8857d…2%2F20160602232958.jpg could save 937B (15% reduction).
Losslessly compressing http://blog.hatena.ne.jp/images/header/dropdown@2x…05794004781e6a9eccee97 could save 909B (77% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/fr/fridayusao/profile.gif could save 756B (49% reduction).
Losslessly compressing http://cdn1.www.st-hatena.com/users/j5/j50/profile.gif could save 643B (21% reduction).
Losslessly compressing http://cdn1.www.st-hatena.com/users/lu/lucky--happy--smile/profile.gif could save 619B (16% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/ni/niko_97/profile.gif could save 578B (53% reduction).
Losslessly compressing http://cdn1.www.st-hatena.com/users/ic/ichi3000/profile.gif could save 540B (22% reduction).
Compressing and resizing http://cdn1.www.st-hatena.com/users/na/natokinu/profile.gif could save 533B (57% reduction).

Your page has 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.Optimize CSS Delivery of the following:

https://blog.st-hatena.com/css/service.css?version…05794004781e6a9eccee97
https://fonts.googleapis.com/css?family=Open+Sans:300,400italic,400,600

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://cdn7.www.st-hatena.com/js/jquery-1.9.1.min.js (expiration not specified)
http://cdn7.www.st-hatena.com/js/jquery/jquery-ui.1.10.0.custom.min.js (expiration not specified)
http://cdn7.www.st-hatena.com/js/jquery/jquery.flot.0.8.3.js (expiration not specified)
http://cdn7.www.st-hatena.com/js/jquery/jquery.flot.time.0.8.3.js (expiration not specified)
http://hatenablog.com/images/banner/Download_on_th…Badge_US-UK_135x40.png (expiration not specified)
http://hatenablog.com/images/banner/banner-ios-app-v3.jpg (expiration not specified)
http://hatenablog.com/images/banner/blog-blog-banner.gif (expiration not specified)
http://hatenablog.com/images/banner/blog-staffblog-banner.gif (expiration not specified)
http://hatenablog.com/images/banner/google-play-banner-45-en.png (expiration not specified)
http://hatenablog.com/images/banner/pro_banner3_rectangle.gif (expiration not specified)
http://hatenablog.com/images/circle/official-circl…imation-and-comics.gif (expiration not specified)
http://hatenablog.com/images/circle/official-circle-icon/entertainment.gif (expiration not specified)
http://hatenablog.com/images/circle/official-circle-icon/showbiz.gif (expiration not specified)
http://hatenablog.com/images/circle/official-circle-icon/sports.gif (expiration not specified)
http://hatenablog.com/images/top/top-logo@2x.png (expiration not specified)
https://s.hatena.ne.jp/js/HatenaStar.js (expiration not specified)
http://www.googletagservices.com/tag/js/gpt.js (15 minutes)
http://connect.facebook.net/ja_JP/sdk.js (20 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
https://apis.google.com/js/platform.js (30 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
http://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://pagead2.googlesyndication.com/pagead/show_ads.js (60 minutes)
https://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://cdn1.www.st-hatena.com/users/ko/komeko7575/profile.gif (7.7 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.9KiB (31% reduction).

Minifying http://cdn7.www.st-hatena.com/js/jquery/jquery.flot.0.8.3.js could save 12.5KiB (47% reduction) after compression.
Minifying https://s.hatena.ne.jp/js/HatenaStar.js could save 7.2KiB (22% reduction) after compression.
Minifying http://d-cache.microad.jp/js/blade_track_jp.js could save 1.9KiB (23% reduction).
Minifying https://b.st-hatena.com/js/bookmark_button.js could save 1.9KiB (23% reduction) after compression.
Minifying http://cdn7.www.st-hatena.com/js/jquery/jquery.flot.time.0.8.3.js could save 1.4KiB (40% reduction) after 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 5.9KiB (69% reduction).

Compressing http://d-cache.microad.jp/js/blade_track_jp.js could save 5.9KiB (69% reduction).

Desktop Resource Breakdown
Total Resources177
Number of Hosts39
Static Resources137
JavaScript Resources39
CSS Resources9

Last tested: 12/03/2017

Mobile
Mobile Usability
99%
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 <div id="abgc" class="abgc">Ads byGoogle</div> is close to 1 other tap targets final.
The tap target <a href="http://program…atenablog.com/">雑な話</a> and 3 others are close to other tap targets.
The tap target <a href="http://mileage…p/entry/micard">【審査時間2分】京都鉄道博物…ントキャンペーンが結構ある。</a> and 1 others are close to other tap targets.

Mobile Speed
59%
Your page has 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.Optimize CSS Delivery of the following:

https://cdn.blog.st-hatena.com/css/service.css?ver…f8441e6&env=production
https://fonts.googleapis.com/css?family=Noto+Sans:400,400i,700,700i

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 212.3KiB (61% reduction).

Compressing https://cdn.image.st-hatena.com/image/square/09c62…8%2F20171128135229.jpg could save 49.9KiB (81% reduction).
Compressing https://cdn.image.st-hatena.com/image/square/0dba0…1%2F20171201090329.jpg could save 48.9KiB (77% reduction).
Compressing https://cdn.image.st-hatena.com/image/square/cbdb4…7%2F20171107174633.jpg could save 39.8KiB (80% reduction).
Compressing https://cdn.image.st-hatena.com/image/square/cd921…3%2F20171203094225.jpg could save 26.9KiB (74% reduction).
Compressing https://cdn.image.st-hatena.com/image/square/50fcb…7%2F20171127210235.png could save 13.8KiB (36% reduction).
Compressing https://cdn.image.st-hatena.com/image/square/e422a…0%2F20171130224003.jpg could save 8.9KiB (40% reduction).
Compressing https://cdn.image.st-hatena.com/image/square/4c258…0%2F20171130174832.jpg could save 8.4KiB (33% reduction).
Compressing http://aff.gnavi.co.jp/images/track/cer.jpg?cid=70…17ea7e1828277439987832 could save 7.2KiB (68% reduction).
Compressing https://cdn.image.st-hatena.com/image/square/f37e0…seo-del-desierto26.jpg could save 5.7KiB (27% reduction).
Compressing https://cdn.image.st-hatena.com/image/square/bdf71…9%2F20161129145733.jpg could save 2.7KiB (17% 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://cdn7.www.st-hatena.com/js/jquery/jquery-ui.1.10.0.custom.min.js (expiration not specified)
http://hatenablog.com/images/banner/Download_on_th…Badge_US-UK_135x40.svg (expiration not specified)
http://hatenablog.com/images/banner/google-play-badge.png (expiration not specified)
https://s.hatena.ne.jp/js/HatenaStar.js (expiration not specified)
https://www.google.com/recaptcha/api.js (5 minutes)
https://syndication.twitter.com/settings (10 minutes)
https://www.googletagmanager.com/gtm.js?id=GTM-P4CXTW (15 minutes)
https://www.googletagservices.com/tag/js/gpt.js (15 minutes)
http://connect.facebook.net/ja_JP/sdk.js (20 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
https://apis.google.com/js/platform.js (30 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
http://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
https://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 23KiB (32% reduction).

Minifying https://cdn.blog.st-hatena.com/js/external/jquery.flot.js?version=0.8.3 could save 12.5KiB (47% reduction) after compression.
Minifying https://s.hatena.ne.jp/js/HatenaStar.js could save 7.2KiB (22% reduction) after compression.
Minifying https://cdn-ak.b.st-hatena.com/js/bookmark_button.js could save 1.9KiB (22% reduction) after compression.
Minifying https://cdn.blog.st-hatena.com/js/external/jquery.….time.js?version=0.8.3 could save 1.4KiB (40% reduction) after compression.

Mobile Resource Breakdown
Total Resources92
Number of Hosts29
Static Resources66
JavaScript Resources35
CSS Resources4
www.hateblo.com
www.hateblo.net
www.hateblo.org
www.hateblo.info
www.hateblo.biz
www.hateblo.us
www.hateblo.mobi
www.ateblo.jp
www.hateblo.jp
www.bateblo.jp
www.hbateblo.jp
www.bhateblo.jp
www.gateblo.jp
www.hgateblo.jp
www.ghateblo.jp
www.yateblo.jp
www.hyateblo.jp
www.yhateblo.jp
www.uateblo.jp
www.huateblo.jp
www.uhateblo.jp
www.jateblo.jp
www.hjateblo.jp
www.jhateblo.jp
www.nateblo.jp
www.hnateblo.jp
www.nhateblo.jp
www.hteblo.jp
www.hqteblo.jp
www.haqteblo.jp
www.hqateblo.jp
www.hwteblo.jp
www.hawteblo.jp
www.hwateblo.jp
www.hsteblo.jp
www.hasteblo.jp
www.hsateblo.jp
www.hzteblo.jp
www.hazteblo.jp
www.hzateblo.jp
www.haeblo.jp
www.hareblo.jp
www.hatreblo.jp
www.harteblo.jp
www.hafeblo.jp
www.hatfeblo.jp
www.hafteblo.jp
www.hageblo.jp
www.hatgeblo.jp
www.hagteblo.jp
www.hayeblo.jp
www.hatyeblo.jp
www.hayteblo.jp
www.hatblo.jp
www.hatwblo.jp
www.hatewblo.jp
www.hatweblo.jp
www.hatsblo.jp
www.hatesblo.jp
www.hatseblo.jp
www.hatdblo.jp
www.hatedblo.jp
www.hatdeblo.jp
www.hatrblo.jp
www.haterblo.jp
www.hatelo.jp
www.hatevlo.jp
www.hatebvlo.jp
www.hatevblo.jp
www.hateglo.jp
www.hatebglo.jp
www.hategblo.jp
www.hatehlo.jp
www.hatebhlo.jp
www.hatehblo.jp
www.hatenlo.jp
www.hatebnlo.jp
www.hatenblo.jp
www.hatebo.jp
www.hatebpo.jp
www.hateblpo.jp
www.hatebplo.jp
www.hateboo.jp
www.hatebloo.jp
www.hatebolo.jp
www.hatebko.jp
www.hateblko.jp
www.hatebklo.jp
www.hatebl.jp
www.hatebli.jp
www.hatebloi.jp
www.hateblio.jp
www.hateblk.jp
www.hateblok.jp
www.hatebll.jp
www.hateblol.jp
www.hatebllo.jp
www.hateblp.jp
www.hateblop.jp