Access ginnomori.jp. 銀の森公式オンラインショップ

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value32.8 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value1,770 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value1.025

2/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

ginnomori.jp

536 ms

ginnomori.jp

945 ms

fs_style.css

1406 ms

fs_theme.css

1589 ms

fs_original.css

2102 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 3% of them (4 requests) were addressed to the original Ginnomori.jp, 80% (94 requests) were made to Ginnomori.itembox.design and 6% (7 requests) were made to Scontent-iad3-1.cdninstagram.com. The less responsive or slowest element that took the longest time to load (5.3 sec) relates to the external source Ginnomori.itembox.design.

Content Size

13.7 MB

After Optimization

13.0 MB

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

HTML Optimization

-83%

Potential reduce by 102.6 kB

Original 123.0 kB
After minification 111.5 kB
After compression 20.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 102.6 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 639.4 kB

Original 13.3 MB
After minification 12.7 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. Ginnomori images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 36.4 kB

Original 255.0 kB
After minification 254.9 kB
After compression 218.6 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 36.4 kB or 14% of the original size.

CSS Optimization

-7%

Potential reduce by 4.7 kB

Original 70.8 kB
After minification 70.8 kB
After compression 66.1 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. Ginnomori.jp has all CSS files already compressed.

Requests Now

114

After Optimization

101

The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ginnomori. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 5 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

button, link, and menuitem elements do not have accessible names.

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

Definition list items are not wrapped in <dl> elements

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.

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Requests the notification permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links are not crawlable

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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

UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ginnomori.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 Ginnomori.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

ginnomori.jp

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

Report Summary

Performance

Accessibility

Best Practices

SEO

銀の森公式オンラインショップ

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

ginnomori.jp

ginnomori.jp

fs_style.css

fs_theme.css

fs_original.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

ginnomori.jp

ginnomori.jp

fs_style.css

fs_theme.css

fs_original.css

webstore-vg.js

spnav.css

jquery.min.js

spnav.js

js

all.css

webstore.js

city_728_90.png

234_60_n.png

logo.svg

megamenu-inner-patisserie.png

megamenu-inner-mikuriya.png

megamenu-inner-okudo.png

megamenu-inner-kalitelemon.png

megamenu-inner-gosechie.png

megamenu-inner-morinoshokutaku.png

megamenu-inner-guide.png

megamenu-inner-shipping-payment.png

megamenu-inner-faq.png

megamenu-inner-form.png

pc_btn_icon1.svg

pc_btn_icon2.svg

brand01.png

brand02.png

brand03.png

brand04.png

brand05.png

brand06.png

cate1-1.png

cate1-2.png

cate1-3.png

cate1-4.png

cate1-5.png

cate1-6.png

cate1-7.png

cate2-1.png

cate2-2.png

cate2-3.png