Hatenadiary.jp - SEO Checker

Your Website Score is

Similar Ranking

国联资源网_中国领先的B2B电子商务集群,高效的链商资源整合服务网络

ibicn.com

REVOLVE (リボルブ)で、有名デザイナーズブランドの洋服をショッピング

revolveclothing.co.jp

VOITURE AU MAROC - VOITURE OCCASION AU MAROC - ANNONCES MOTEUR.MA

moteur.ma

مكتبة نور - تحميل كتب PDF

noor-book.com

BEST WIFI BROADBAND & INTERNET SERVICE PROVIDER (ISP) IN INDIA | TIKONA INFINET PRIVATE LIMITED

tikona.in

DOWNLOAD--- SOFTWARE FOR WINDOWS - JALECO.COM

jaleco.com

نماشا - سرویس رایگان اشتراک ویدیو

namasha.com

Latest Sites

JUST A MOMENT...

hourlyminer.com

ピアノ教室ネット｜先生との出会いはここから。全国のピアノ教室から検索！

pnet.kawai.jp

ADAGIETTOピアノ教室|飯能|ピアノに興味がある皆さんへ|

adagiettopiano.com

ГЛАВНАЯ | UNIEX

uniex.biz

AHMADIMADO - TRUSTED DOGECOIN CLOUD MINING

ahmadimado.net

DOGESILVA LIMITED - HOME

dogesilva.com

FEEDOUGH | BUSINESS MODELS & STARTUP FEEDS

feedough.com

Top Technologies

Nginx

Web Servers

PHP

Programming Languages

Google Tag Manager

Tag Managers

Google Font API

Font Scripts

CloudFlare

CDN

jQuery

JavaScript Frameworks

Apache

Web Servers

Font Awesome

Font Scripts

WordPress

CMS

Twitter Bootstrap

Web Frameworks

31 hatenadiary.jp Last Updated: 8 months

Success 70% of passed verification steps

Warning 7% of total warning

Errors 23% of total errors, require fast action

Mobile

Performance Desktop Score 64%

Best Practices Desktop Score 77%

SEO Desktop Score 100%

Progressive Web App Desktop Score 31%

Performance Mobile Score 31%

Best Practices Mobile Score 77%

SEO Mobile Score 99%

Progressive Web App Mobile Score 33%

Page Authority Authority 0%

Domain Authority Domain Authority 0%

Moz Rank 0.0/10

Bounce Rate Rate 0%

Charset Encoding

Great, language/character encoding is specified: UTF-8

Title Tag 11 Characters

HATENA BLOG

Meta Description 144 Characters

Hatena Blog is an easy to use blog service that anyone can use for---. Write about your daily life and thoughts so you will never forget them.

Effective URL 22 Characters

https://hatenablog.com

Excerpt Page content

Hatena Blog 思いは言葉に。 ...

Keywords Cloud Density

hatena9 blog6 support3 はてなブログpro2 react2 はてなブログとは2 more2 calendar2 advent2 program2

Keyword Consistency Keyword density is one of the main terms in SEO

Keyword	Freq	Title	Desc	Domain	H1	H2
hatena	9
blog	6
support	3
はてなブログpro	2
react	2
はてなブログとは	2
more	2
calendar	2
advent	2
program	2

Google Preview Your look like this in google search result

HATENA BLOG

https://hatenablog.com

Hatena Blog is an easy to use blog service that anyone can use for---. Write about your daily life and thoughts so you will never forget them.

Robots.txt File Detected

http://hatenadiary.jp/robots.txt

Sitemap.xml File No Found

http://hatenadiary.jp/sitemap.xml

Page Size Code & Text Ratio

Document Size: ~68.02 KB

Code Size: ~41 KB

Text Size: ~27.01 KB Ratio: 39.72%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Desktop

Serve images in next-gen formats Potential savings of 469 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

User Timing marks and measures 6 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Reduce server response times (TTFB) Root document took 880 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 80 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Efficiently encode images Potential savings of 136 KB

Optimized images load faster and consume less cellular data

Reduce the impact of third-party code Third-party code blocked the main thread for 280 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 130 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

JavaScript execution time 1.0 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Defer offscreen images Potential savings of 662 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Properly size images Potential savings of 6 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 2.3 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 3.9 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoid enormous network payloads Total size was 3,292 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 2.3 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 0.8 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 3 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 16 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load

Avoids an excessive DOM size 545 elements

A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)

Minify JavaScript Potential savings of 40 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 0.8 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 107 requests • 3,292 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 59 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 150 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 4.4 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Page load is not fast enough on mobile networks Interactive on simulated mobile network at 22.1 s

A fast page load over a cellular network ensures a good mobile user experience

Estimated Input Latency 30 ms

Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy

Remove unused CSS Potential savings of 43 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Mobile

Reduce server response times (TTFB) Root document took 880 ms

Time To First Byte identifies the time at which your server sends a response

Eliminate render-blocking resources Potential savings of 600 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Efficiently encode images Potential savings of 125 KB

Optimized images load faster and consume less cellular data

Reduce the impact of third-party code Third-party code blocked the main thread for 2,130 ms

Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading

Total Blocking Time 1,640 ms

Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Reduce JavaScript execution time 5.0 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this

Server Backend Latencies 0 ms

Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance

Defer offscreen images Potential savings of 694 KB

Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive

Properly size images Potential savings of 4 KB

Serve images that are appropriately-sized to save cellular data and improve load time

Speed Index 9.2 s

Speed Index shows how quickly the contents of a page are visibly populated

First CPU Idle 7.2 s

First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).

Avoid enormous network payloads Total size was 3,123 KB

Large network payloads cost users real money and are highly correlated with long load times

Minimize main-thread work 9.0 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this

First Contentful Paint 2.7 s

First Contentful Paint marks the time at which the first text or image is painted

Includes front-end JavaScript libraries with known security vulnerabilities 3 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers

Avoid chaining critical requests 17 chains found

Avoids an excessive DOM size 545 elements

Minify JavaScript Potential savings of 40 KB

Minifying JavaScript files can reduce payload sizes and script parse time

First Meaningful Paint 2.9 s

First Meaningful Paint measures when the primary content of a page is visible

Keep request counts low and transfer sizes small 106 requests • 3,123 KB

To set budgets for the quantity and size of page resources, add a budget.json file

Serve static assets with an efficient cache policy 59 resources found

A long cache lifetime can speed up repeat visits to your page

Max Potential First Input Delay 530 ms

The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task

Time to Interactive 20.9 s

Time to interactive is the amount of time it takes for the page to become fully interactive

Network Round Trip Times 0 ms

Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance

Page load is not fast enough on mobile networks Interactive at 20.9 s

A fast page load over a cellular network ensures a good mobile user experience

First Contentful Paint (3G) 5475 ms

First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network

Estimated Input Latency 210 ms

Tap targets are not sized appropriately 92% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements

Document uses legible font sizes 99.07% legible text

Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px

Remove unused CSS Potential savings of 40 KB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity

Serve images in next-gen formats Potential savings of 444 KB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption

User Timing marks and measures 6 user timings

Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server

HTTP/1.1 200 OK
Server: nginx
Date: Wed, 18 Dec 2019 00:58:03 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Vary: Accept-Encoding
Cache-Control: private
Vary: User-Agent, X-Forwarded-Host, X-Device-Type
Content-Security-Policy-Report-Only: block-all-mixed-content; report-uri https://blog.hatena.ne.jp/api/csp_report
P3P: CP="OTI CUR OUR BUS STA"
X-Content-Type-Options: nosniff
X-Dispatch: Hatena::Epic::Web::Global::Index#index
X-Frame-Options: DENY
X-Page-Cache: hit
X-Revision: b4802d524e10fb642f184ab120cfeacc
X-XSS-Protection: 1
X-Runtime: 0.005481
X-Varnish: 372379380
Age: 0
Via: 1.1 varnish-v4
X-Cache: MISS
Content-Encoding: gzip

DNS Records DNS Resource Records associated with a hostname

View DNS Records

Type	Name	Value	Class	TTL
A	hatenadiary.jp	52.69.186.243	IN	59
A	hatenadiary.jp	13.112.159.226	IN	59
NS	hatenadiary.jp	ns-1771.awsdns-29.co.uk	IN	3532
NS	hatenadiary.jp	ns-916.awsdns-50.net	IN	3532
NS	hatenadiary.jp	ns-111.awsdns-13.com	IN	3532
NS	hatenadiary.jp	ns-1315.awsdns-36.org	IN	3532
MX	hatenadiary.jp	mailinbound.hatena.ne.jp	IN	3600
TXT	hatenadiary.jp	google-site-verification=ZGZV48H9tUW6jLCBuNX8kyeahGex-7g-iAG4PHpZoPY	IN	86400

Your Website Score is

Similar Ranking

Latest Sites

Top Technologies

31 hatenadiary.jp Last Updated: 8 months

Desktop

Mobile

Estimation Traffic and Earnings

Sign up for see all features and reviews about this site

Desktop

Mobile

Speed And Optimization Tips

Sign up for see all features and reviews about this site

Alexa Rank

0

Information Server

Comments