Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

gatsby.jp

GATSBY - ギャツビー|mandom

Page Load Speed

15.2 sec in total

First Response

1.4 sec

Resources Loaded

11.6 sec

Page Rendered

2.2 sec

gatsby.jp screenshot

About Website

Welcome to gatsby.jp homepage info - get ready to check GATSBY best content for Japan right away, or after learning these important things about gatsby.jp

GATSBY(ギャツビー)の公式ブランドサイト。商品情報やセルフテクニック、フェイス・ヘア・ボディケア情報などを紹介します。ギャツビーは男のカッコイイをサポート。

Visit gatsby.jp

Key Findings

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

Performance Metrics

gatsby.jp performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value34.8 s

0/100

25%

SI (Speed Index)

Value20.1 s

0/100

10%

TBT (Total Blocking Time)

Value740 ms

40/100

30%

CLS (Cumulative Layout Shift)

Value0.665

8/100

15%

TTI (Time to Interactive)

Value17.8 s

4/100

10%

Network Requests Diagram

www.gatsby.jp

1425 ms

gtm.js

66 ms

fancybox.css

17 ms

common.css

1267 ms

lity.css

735 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 69% of them (81 requests) were addressed to the original Gatsby.jp, 8% (9 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (5.9 sec) belongs to the original domain Gatsby.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 568.0 kB (6%)

Content Size

9.5 MB

After Optimization

9.0 MB

In fact, the total size of Gatsby.jp main page is 9.5 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. Only a small number of websites need less resources to load. Images take 8.8 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 45.1 kB

  • Original 53.9 kB
  • After minification 38.3 kB
  • After compression 8.8 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 15.6 kB, which is 29% 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 45.1 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 87.4 kB

  • Original 8.8 MB
  • After minification 8.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. GATSBY images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 334.6 kB

  • Original 569.2 kB
  • After minification 562.4 kB
  • After compression 234.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 334.6 kB or 59% of the original size.

CSS Optimization

-85%

Potential reduce by 100.9 kB

  • Original 118.6 kB
  • After minification 97.5 kB
  • After compression 17.7 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. Gatsby.jp needs all CSS files to be minified and compressed as it can save up to 100.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (33%)

Requests Now

108

After Optimization

72

The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GATSBY. 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 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

gatsby.jp accessibility score

92

Accessibility Issues

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.

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

Links do not have a discernible name

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

High

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

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

gatsby.jp SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

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 Gatsby.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 Gatsby.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 data is detected on the main page of GATSBY. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: