Access gregory.jp. グレゴリー(GREGORY)公式通販

name

value

score

weighting

FCP (First Contentful Paint)

Value8.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value26.4 s

0/100

25%

SI (Speed Index)

Value14.5 s

1/100

10%

TBT (Total Blocking Time)

Value2,140 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.244

51/100

15%

TTI (Time to Interactive)

Value27.8 s

0/100

10%

gregory.jp

430 ms

www.gregory.jp

870 ms

font-awesome.min.css

41 ms

jquery-ui.css

69 ms

jquery.mCustomScrollbar.css

359 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 80% of them (59 requests) were addressed to the original Gregory.jp, 5% (4 requests) were made to Google-analytics.com and 3% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain Gregory.jp.

Content Size

7.3 MB

After Optimization

6.3 MB

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

HTML Optimization

-85%

Potential reduce by 51.8 kB

Original 61.0 kB
After minification 55.4 kB
After compression 9.2 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 51.8 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 60.9 kB

Original 6.3 MB
After minification 6.2 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. GREGORY images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 350.7 kB

Original 433.9 kB
After minification 296.0 kB
After compression 83.2 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 350.7 kB or 81% of the original size.

CSS Optimization

-91%

Potential reduce by 456.0 kB

Original 501.4 kB
After minification 338.8 kB
After compression 45.4 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. Gregory.jp needs all CSS files to be minified and compressed as it can save up to 456.0 kB or 91% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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 keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

High

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

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

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 Gregory.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 Gregory.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

gregory.jp

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

グレゴリー(GREGORY)公式通販

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

gregory.jp

www.gregory.jp

font-awesome.min.css

jquery-ui.css

jquery.mCustomScrollbar.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

gregory.jp

www.gregory.jp

font-awesome.min.css

jquery-ui.css

jquery.mCustomScrollbar.css

owl.carousel.css

jquery.minimalect.css

cloudzoom.css

flexslider.css

validationEngine.jquery.css

style.css

jquery-1.11.3.min.js

jquery-ui.min.js

jquery.ui.touch-punch.min.js

imagesloaded.pkgd.min.js

footerFixed.js

jquery.backgroundSize.js

jquery.mCustomScrollbar.js

owl.carousel.js

jquery.flexslider.js

jquery.tile.js

jquery.validationEngine.js

jquery.validationEngine-ja.js

placeholder.js

common.js

headermenu.js

jquery.cookie.js

jquery.popup.js

jquery.google_analytics_ec.js

owl.carousel.css

owl.carousel.min.js

conversion.js

jquery.mousewheel.min.js

analytics.js

collect

collect

logo-sd430ca1ba7.png

1.jpg

3.jpg

44.jpg

dd4868c3c8ee27e8f651db8537f6c655.jpg

22.jpg

lifestyle.gif