Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

sakelog.jp

黒糖焼酎を徹底解説&飲み方、飲んでみたレビュー黒糖焼酎飲んべえ!! –

Page Load Speed

6 sec in total

First Response

503 ms

Resources Loaded

5.2 sec

Page Rendered

282 ms

sakelog.jp screenshot

About Website

Click here to check amazing Sakelog content. Otherwise, check out these important facts you probably never knew about sakelog.jp

黒糖焼酎とは何か?味は甘い?その歴史からオススメの銘柄、飲み方まで徹底解説。 黒糖焼酎は、鹿児島県の南部の奄美群島の特産品でサトウキビから造られる黒糖を原料とする本格焼酎です。酒税法によってこの地域だけに製造が認められていることから、「奄美黒糖焼酎」と呼ばれることもあります。 また、2020年時点で奄美群島内にある23場の蔵元が16社の納税企業名(共同瓶詰め専門の2社を含む)で製造、出荷を行ってい...

Visit sakelog.jp

Key Findings

We analyzed Sakelog.jp page load time and found that the first response time was 503 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

sakelog.jp performance score

0

Network Requests Diagram

sakelog.jp

503 ms

www.sakelog.com

576 ms

default.css

326 ms

header.css

345 ms

footer.css

348 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Sakelog.jp, 42% (52 requests) were made to Sakelog.com and 8% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Sakelog.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 217.4 kB (23%)

Content Size

930.5 kB

After Optimization

713.1 kB

In fact, the total size of Sakelog.jp main page is 930.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 641.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 29.8 kB

  • Original 38.9 kB
  • After minification 36.9 kB
  • After compression 9.1 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 29.8 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 17.6 kB

  • Original 641.3 kB
  • After minification 623.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. Sakelog images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 115.6 kB

  • Original 187.0 kB
  • After minification 140.4 kB
  • After compression 71.5 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 115.6 kB or 62% of the original size.

CSS Optimization

-86%

Potential reduce by 54.4 kB

  • Original 63.4 kB
  • After minification 53.7 kB
  • After compression 8.9 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. Sakelog.jp needs all CSS files to be minified and compressed as it can save up to 54.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (52%)

Requests Now

120

After Optimization

58

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

SEO Factors

sakelog.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 Sakelog.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 Sakelog.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

Open Graph description is not detected on the main page of Sakelog. 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: