6.1 sec in total
1.7 sec
4.2 sec
245 ms
Click here to check amazing Mary content for Japan. Otherwise, check out these important facts you probably never knew about mary.co.jp
日本を代表する高級チョコレートメーカーのメリーチョコレート公式サイト。メリーチョコレートにはチョコレートを始め、マロングラッセ、クッキー(焼き菓子)、ケーキ、その他洋菓子など魅力あふれるスイーツがいっぱいです。メリーチョコレートは全国各地の販売店でお求めください。
Visit mary.co.jpWe analyzed Mary.co.jp page load time and found that the first response time was 1.7 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
mary.co.jp performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value14.6 s
0/100
25%
Value19.6 s
0/100
10%
Value10,510 ms
0/100
30%
Value1.233
1/100
15%
Value20.0 s
2/100
10%
1672 ms
539 ms
367 ms
589 ms
595 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 99% of them (77 requests) were addressed to the original Mary.co.jp, 1% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Mary.co.jp.
Page size can be reduced by 93.4 kB (27%)
346.9 kB
253.5 kB
In fact, the total size of Mary.co.jp main page is 346.9 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 243.9 kB which makes up the majority of the site volume.
Potential reduce by 56.6 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 20.9 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 56.6 kB or 89% of the original size.
Potential reduce by 20.0 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. Mary images are well optimized though.
Potential reduce by 10.8 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.8 kB or 34% of the original size.
Potential reduce by 6.0 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. Mary.co.jp needs all CSS files to be minified and compressed as it can save up to 6.0 kB or 81% of the original size.
Number of requests can be reduced by 15 (19%)
77
62
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mary. 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.
mary.co.jp
1672 ms
common.js
539 ms
rollover.js
367 ms
swfobject.js
589 ms
global_2.css
595 ms
logo.jpg
180 ms
m_online_2.jpg
393 ms
m_top.gif
185 ms
m_mary_2.gif
202 ms
m_item_2.gif
358 ms
m_store_2.gif
359 ms
top_main.jpg
770 ms
bg.jpg
582 ms
top_con_bg.gif
451 ms
top_pick_body.gif
520 ms
top_what.jpg
521 ms
top_yaji.jpg
573 ms
top_omimai.jpg
481 ms
top_pickup.jpg
901 ms
toppick_img_whiteday2016.gif
541 ms
toppick_whiteday2016.gif
610 ms
toppick_m131122_2p.jpg
620 ms
toppick_senryu_2016_fin.gif
669 ms
toppick_m140130_1p.jpg
719 ms
toppick_m2014_tohato.gif
779 ms
toppick_recruit.jpg
806 ms
toppick_recruit.gif
817 ms
toppick_m35p.jpg
858 ms
toppick_m2015_starsweet.gif
898 ms
toppick_illust_2015.jpg
962 ms
toppick_illust_res_2015.gif
1001 ms
toppick_ff_2014.jpg
1014 ms
toppick_ff_2014.gif
949 ms
toppick_amor2016.gif
977 ms
toppick_m_ainoki2016.gif
979 ms
toppick_chocolasika.jpg
1046 ms
toppick_chocolawka.gif
1098 ms
toppick_salon.jpg
1108 ms
toppick_salon_choco.gif
1132 ms
toppick_m29p.jpg
1148 ms
toppick_m29.gif
1150 ms
toppick_m24p.jpg
1222 ms
toppick_m24.gif
1288 ms
ga.js
30 ms
top_gotolist_2015.gif
1295 ms
top_gotolist_2014.gif
1244 ms
top_gotolist_2013.gif
1250 ms
top_pick_foot.gif
1220 ms
top_banner_ff2014.jpg
1224 ms
top_banner10.jpg
1428 ms
top_banner17.jpg
1448 ms
top_banner1.jpg
1203 ms
cred_banner.jpg
1191 ms
top_banner15.jpg
1312 ms
top_banner140205.jpg
1158 ms
top_banner5.jpg
1196 ms
titlearea_05_off.png
1386 ms
top_banner16.jpg
1444 ms
top_banner9.jpg
1316 ms
top_banner131122.jpg
1251 ms
logo_on.jpg
191 ms
m_online_2_on.jpg
180 ms
m_top_on.gif
198 ms
m_mary_2_on.gif
184 ms
m_item_2_on.gif
200 ms
m_store_2_on.gif
180 ms
toppick_whiteday2016_on.gif
359 ms
toppick_senryu_2016_fin_on.gif
361 ms
toppick_m2014_tohato_on.gif
366 ms
toppick_recruit_on.gif
379 ms
toppick_m2015_starsweet_on.gif
392 ms
toppick_illust_res_2015_on.gif
395 ms
toppick_ff_2014_on.gif
535 ms
toppick_m_ainoki2016_on.gif
536 ms
toppick_chocolawka_on.gif
548 ms
toppick_salon_choco_on.gif
567 ms
toppick_m29_on.gif
588 ms
toppick_m24_on.gif
592 ms
mary.co.jp accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
mary.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
mary.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mary.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 Mary.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.
mary.co.jp
Open Graph description is not detected on the main page of Mary. 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: