Tools & Wizards About Us
tokyo-yotsuba.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tokyo-yotsuba.com

403 error - Forbidden

Page Load Speed

4.9 sec in total

First Response

1.2 sec

Resources Loaded

3.3 sec

Page Rendered

301 ms

tokyo-yotsuba.com screenshot

About Website

Click here to check amazing Tokyo Yotsuba content. Otherwise, check out these important facts you probably never knew about tokyo-yotsuba.com

究極の粗品専門店 東京四ツ葉工房は「日本国内栽培」で「安全」で「高品質」な「四ツ葉のクローバー」を幸せとともに、お届けしています

Visit tokyo-yotsuba.com

Key Findings

We analyzed Tokyo-yotsuba.com page load time and found that the first response time was 1.2 sec 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

tokyo-yotsuba.com performance score

0

Network Requests Diagram

tokyo-yotsuba.com

1225 ms

jquery.js

1133 ms

thickbox.js

559 ms

styles.css

362 ms

blog.css

164 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 92% of them (24 requests) were addressed to the original Tokyo-yotsuba.com, 8% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Tokyo-yotsuba.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 182.0 kB (27%)

Content Size

676.2 kB

After Optimization

494.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tokyo-yotsuba.com main page is 676.2 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. 25% of websites need less resources to load. Images take 496.1 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 12.7 kB

  • Original 16.2 kB
  • After minification 13.0 kB
  • After compression 3.5 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. This page needs HTML code to be minified as it can gain 3.3 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 12.7 kB or 78% of the original size.

Image Optimization

-9%

Potential reduce by 47.0 kB

  • Original 496.1 kB
  • After minification 449.1 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. Tokyo Yotsuba images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 92.7 kB

  • Original 129.0 kB
  • After minification 81.7 kB
  • After compression 36.3 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 92.7 kB or 72% of the original size.

CSS Optimization

-85%

Potential reduce by 29.5 kB

  • Original 34.8 kB
  • After minification 22.5 kB
  • After compression 5.3 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. Tokyo-yotsuba.com needs all CSS files to be minified and compressed as it can save up to 29.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (33%)

Requests Now

24

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tokyo Yotsuba. 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 CSS and as a result speed up the page load time.

Network Requests Diagram

tokyo-yotsuba.com

tokyo-yotsuba.com

1225 ms

jquery.js

jquery.js

1133 ms

thickbox.js

thickbox.js

559 ms

styles.css

styles.css

362 ms

blog.css

blog.css

164 ms

insyoku_b1.css

insyoku_b1.css

535 ms

thickbox.css

thickbox.css

157 ms

logo.gif

logo.gif

197 ms

header_main.jpg

header_main.jpg

647 ms

list_new.gif

list_new.gif

334 ms

oka_s.jpg

oka_s.jpg

1086 ms

oka3_s.jpg

oka3_s.jpg

1088 ms

oka2_s.jpg

oka2_s.jpg

748 ms

merry_s.jpg

merry_s.jpg

827 ms

velen_s.jpg

velen_s.jpg

1079 ms

arrow01.gif

arrow01.gif

811 ms

mother_s.jpg

mother_s.jpg

955 ms

ga.js

ga.js

39 ms

bg_body.jpg

bg_body.jpg

438 ms

body_bg-tw.gif

body_bg-tw.gif

450 ms

border01.gif

border01.gif

624 ms

border02.gif

border02.gif

593 ms

arrow02.gif

arrow02.gif

624 ms

btn_pagetop.gif

btn_pagetop.gif

730 ms

loadingAnimation.gif

loadingAnimation.gif

684 ms

__utm.gif

__utm.gif

13 ms

SEO Factors

tokyo-yotsuba.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tokyo-yotsuba.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tokyo-yotsuba.com 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

tokyo-yotsuba.com

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