Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

blog.monoco.jp

MONOCO(モノコ) | お買い物に、“ストーリー”を。

Page Load Speed

7.7 sec in total

First Response

450 ms

Resources Loaded

4.6 sec

Page Rendered

2.7 sec

blog.monoco.jp screenshot

About Website

Welcome to blog.monoco.jp homepage info - get ready to check Blog MONOCO best content for Japan right away, or after learning these important things about blog.monoco.jp

MONOCOは、検索エンジンもSNSも教えてくれない「魅力的な商品」に出逢えるショッピングサイト。スタッフが3週間以上使い、満足できたものだけを発信。今日も、あなたのお買い物に“ストーリー”を!

Visit blog.monoco.jp

Key Findings

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

Performance Metrics

blog.monoco.jp performance score

0

Network Requests Diagram

blog.monoco.jp

450 ms

pre_tumblelog.js

13 ms

reset.css

29 ms

jquery.min.js

35 ms

cufon-yui.js

30 ms

Our browser made a total of 150 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Blog.monoco.jp, 21% (31 requests) were made to 40.media.tumblr.com and 17% (25 requests) were made to 41.media.tumblr.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source 40.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 573.9 kB (13%)

Content Size

4.6 MB

After Optimization

4.0 MB

In fact, the total size of Blog.monoco.jp main page is 4.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 124.3 kB

  • Original 159.7 kB
  • After minification 153.9 kB
  • After compression 35.4 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 124.3 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 103.8 kB

  • Original 3.9 MB
  • After minification 3.8 MB

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 MONOCO images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 345.2 kB

  • Original 551.9 kB
  • After minification 551.9 kB
  • After compression 206.7 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 345.2 kB or 63% of the original size.

CSS Optimization

-50%

Potential reduce by 641 B

  • Original 1.3 kB
  • After minification 1.3 kB
  • After compression 651 B

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.monoco.jp needs all CSS files to be minified and compressed as it can save up to 641 B or 50% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (25%)

Requests Now

149

After Optimization

112

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

SEO Factors

blog.monoco.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.monoco.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Blog.monoco.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 data is detected on the main page of Blog MONOCO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: