Tools & Wizards About Us
y-marche.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

y-marche.com

会員制宅配サービス「やっちゃば倶楽部」豊洲の生鮮や全国各地の名店の逸品を少しずつお取り寄せ。

Page Load Speed

3.6 sec in total

First Response

348 ms

Resources Loaded

3.1 sec

Page Rendered

225 ms

y-marche.com screenshot

About Website

Click here to check amazing Y Marche content for Japan. Otherwise, check out these important facts you probably never knew about y-marche.com

会員制宅配サービス「やっちゃば倶楽部」。豊洲の目利き衆が吟味した全国各地の旨いもんをお好きな組み合わせでお取り寄せいただけます。

Visit y-marche.com

Key Findings

We analyzed Y-marche.com page load time and found that the first response time was 348 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

y-marche.com performance score

0

Network Requests Diagram

y-marche.com

348 ms

www.y-marche.com

620 ms

base.css

590 ms

script.js

737 ms

flash.js

149 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 51.7 kB (20%)

Content Size

262.6 kB

After Optimization

210.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Y-marche.com main page is 262.6 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. 15% of websites need less resources to load. Images take 183.8 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 12.5 kB

  • Original 17.0 kB
  • After minification 11.4 kB
  • After compression 4.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 5.6 kB, which is 33% 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.5 kB or 73% of the original size.

Image Optimization

-4%

Potential reduce by 6.6 kB

  • Original 183.8 kB
  • After minification 177.2 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. Y Marche images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 26.8 kB

  • Original 54.3 kB
  • After minification 48.9 kB
  • After compression 27.4 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 26.8 kB or 49% of the original size.

CSS Optimization

-77%

Potential reduce by 5.8 kB

  • Original 7.5 kB
  • After minification 5.9 kB
  • After compression 1.7 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. Y-marche.com needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (26%)

Requests Now

23

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

y-marche.com

y-marche.com

348 ms

www.y-marche.com

www.y-marche.com

620 ms

base.css

base.css

590 ms

script.js

script.js

737 ms

flash.js

flash.js

149 ms

toptext.html

toptext.html

150 ms

bk.gif

bk.gif

151 ms

logo.gif

logo.gif

151 ms

renewal.png

renewal.png

1099 ms

catalogue.jpg

catalogue.jpg

734 ms

btnCatalogue.jpg

btnCatalogue.jpg

441 ms

btnMarche.jpg

btnMarche.jpg

587 ms

goyo2.jpg

goyo2.jpg

901 ms

goyo3.jpg

goyo3.jpg

753 ms

goyo4.jpg

goyo4.jpg

753 ms

goyo5.jpg

goyo5.jpg

734 ms

catalog.jpg

catalog.jpg

1618 ms

koe1.gif

koe1.gif

879 ms

koe3.gif

koe3.gif

880 ms

mark1.gif

mark1.gif

880 ms

f_logo.png

f_logo.png

881 ms

koe2.gif

koe2.gif

1008 ms

koe_mark.gif

koe_mark.gif

1008 ms

analytics.js

analytics.js

4 ms

collect

collect

15 ms

SEO Factors

y-marche.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Y-marche.com 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 Y-marche.com main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

y-marche.com

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