Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

gregory.jp

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

Page Load Speed

9.5 sec in total

First Response

430 ms

Resources Loaded

8.6 sec

Page Rendered

460 ms

gregory.jp screenshot

About Website

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

米国カルフォルニア発のアウトドアブランド、GREGORY(グレゴリー)の公式オンラインストア。背負い心地の良さを追求したリュックやバックパック、ショルダーバッグなど、アウトドア、タウン、ビジネス、トラベルなど様々なシーンでの活躍するアイテムを展開。新作から限定アイテムまで、公式ならではの豊富な品揃え。

Visit gregory.jp

Key Findings

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

Performance Metrics

gregory.jp performance score

10

Measured Metrics

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%

Network Requests Diagram

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.

Page Optimization Overview & Recommendations

Page size can be reduced by 886.0 kB (12%)

Content Size

7.2 MB

After Optimization

6.3 MB

In fact, the total size of Gregory.jp main page is 7.2 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

-79%

Potential reduce by 317.3 kB

  • Original 400.6 kB
  • After minification 262.6 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 317.3 kB or 79% 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 Breakdown

Number of requests can be reduced by 37 (54%)

Requests Now

69

After Optimization

32

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 Review

gregory.jp accessibility score

59

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

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

Best Practices

gregory.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

gregory.jp SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

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

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

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: