Access maryshop.jp. ロッテグループ公式オンラインモール

maryshop.jp screenshot

1

Performance

Renders faster than
19% of other websites
85

Accessibility

Visual factors better than
that of 58% of websites
67

Best Practices

More advanced features
available than in
24% of websites
91

SEO

Google-friendlier than
70% of websites

First Response

553 ms

Resources Loaded

7.5 sec

Page Rendered

569 ms

maryshop.jp screenshot

About Website

Visit maryshop.jp now to see the best up-to-date Maryshop content for Japan and also check out these interesting facts you probably never knew about maryshop.jp

「お口の恋人」ロッテグループの直営オンラインモールです。ロッテの菓子・アイス、メリーチョコレートのギフト、銀座コージーコーナーのケーキと幅広いラインナップを取り揃えております。

Visit maryshop.jp

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value8.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value35.4 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value2,670 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value1.298

1/100

15%

TTI (Time to Interactive)

Value27.2 s

0/100

10%

maryshop.jp

553 ms

default.aspx

1698 ms

style.css

344 ms

jquery.js

1231 ms

common.js

706 ms

Our browser made a total of 173 requests to load all elements on the main page. We found that 88% of them (152 requests) were addressed to the original Maryshop.jp, 2% (3 requests) were made to Cm.g.doubleclick.net and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Maryshop.jp.

Content Size

5.6 MB

After Optimization

4.7 MB

In fact, the total size of Maryshop.jp main page is 5.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. 45% of websites need less resources to load. Images take 4.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 73.9 kB

Original 88.3 kB
After minification 82.7 kB
After compression 14.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 73.9 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 289.2 kB

Original 4.8 MB
After minification 4.5 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. Maryshop images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 268.6 kB

Original 403.7 kB
After minification 382.6 kB
After compression 135.0 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 268.6 kB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 219.9 kB

Original 256.4 kB
After minification 184.0 kB
After compression 36.5 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. Maryshop.jp needs all CSS files to be minified and compressed as it can save up to 219.9 kB or 86% of the original size.

Requests Now

165

After Optimization

118

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

Accessibility Issues

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

[aria-hidden="true"] elements contain focusable descendents

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Maryshop.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 Maryshop.jp 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

maryshop.jp

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