Tools & Wizards About Us
blog.awake.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

blog.awake.co.jp

肌と心のストレス開放を目指す「ＡＷＡＫＥコミュニティ」 サイプレスオイルが香るパラダイスコールやエクスフォリザーなどアウェイク商品のブログクチコミもいっぱい！

Page Load Speed

4.2 sec in total

First Response

542 ms

Resources Loaded

3.4 sec

Page Rendered

238 ms

blog.awake.co.jp screenshot

About Website

Visit blog.awake.co.jp now to see the best up-to-date Blog Awake content for Japan and also check out these interesting facts you probably never knew about blog.awake.co.jp

ようこそ！日々のストレスを脱ぎ捨てるアウェイクの森へ 女性の肌と心のストレス開放を目指したブログコミュニティ。アウェイク商品のクチコミもいっぱい！

Visit blog.awake.co.jp

Key Findings

We analyzed Blog.awake.co.jp page load time and found that the first response time was 542 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

blog.awake.co.jp performance score

0

Network Requests Diagram

blog.awake.co.jp

542 ms

common.css

529 ms

DD_belatedPNG_0.0.8a.min.js

534 ms

354 ms

bg.jpg

1913 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 53% of them (8 requests) were addressed to the original Blog.awake.co.jp, 13% (2 requests) were made to Google-analytics.com and 13% (2 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Blog.awake.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.4 kB (8%)

Content Size

867.1 kB

After Optimization

798.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.awake.co.jp main page is 867.1 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 825.1 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 5.4 kB

  • Original 8.6 kB
  • After minification 8.3 kB
  • After compression 3.2 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 5.4 kB or 63% of the original size.

Image Optimization

-5%

Potential reduce by 41.5 kB

  • Original 825.1 kB
  • After minification 783.6 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Blog Awake images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 10.0 kB

  • Original 19.6 kB
  • After minification 19.0 kB
  • After compression 9.6 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 10.0 kB or 51% of the original size.

CSS Optimization

-84%

Potential reduce by 11.5 kB

  • Original 13.7 kB
  • After minification 10.3 kB
  • After compression 2.1 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Blog.awake.co.jp needs all CSS files to be minified and compressed as it can save up to 11.5 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (27%)

Requests Now

11

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Awake. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

blog.awake.co.jp

blog.awake.co.jp

542 ms

common.css

common.css

529 ms

DD_belatedPNG_0.0.8a.min.js

DD_belatedPNG_0.0.8a.min.js

534 ms

354 ms

bg.jpg

bg.jpg

1913 ms

white_bg.png

white_bg.png

752 ms

logo_close.png

logo_close.png

192 ms

bn_fb.jpg

bn_fb.jpg

528 ms

awake_online_banner.jpg

awake_online_banner.jpg

739 ms

urchin.js

urchin.js

8 ms

__utm.gif

__utm.gif

4 ms

pix

pix

155 ms

bl_track.cgi

bl_track.cgi

394 ms

pixel

pixel

24 ms

pixel

pixel

17 ms

SEO Factors

blog.awake.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.awake.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Blog.awake.co.jp main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

blog.awake.co.jp

Open Graph description is not detected on the main page of Blog Awake. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: