Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 54

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

gogotea.jp

午後の紅茶|ソフトドリンク・乳製品|キリン

Page Load Speed

25.8 sec in total

First Response

654 ms

Resources Loaded

23.9 sec

Page Rendered

1.3 sec

gogotea.jp screenshot

About Website

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

キリンビバレッジの午後の紅茶の商品を紹介しています。CMやメイキング動画も公開中。

Visit gogotea.jp

Key Findings

We analyzed Gogotea.jp page load time and found that the first response time was 654 ms and then it took 25.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

gogotea.jp performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value20.5 s

0/100

10%

TBT (Total Blocking Time)

Value910 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value1.008

3/100

15%

TTI (Time to Interactive)

Value26.5 s

1/100

10%

Network Requests Diagram

gogotea.jp

654 ms

index.html

1943 ms

common.css

1163 ms

modern.css

893 ms

base.css

469 ms

Our browser made a total of 349 requests to load all elements on the main page. We found that 0% of them (1 request) were addressed to the original Gogotea.jp, 75% (262 requests) were made to Kirin.co.jp and 6% (21 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.9 sec) relates to the external source Kirin.co.jp.

Page Optimization Overview & Recommendations

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

Content Size

11.6 MB

After Optimization

10.9 MB

In fact, the total size of Gogotea.jp main page is 11.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 11.1 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 56.9 kB

  • Original 73.7 kB
  • After minification 71.3 kB
  • After compression 16.7 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 56.9 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 324.8 kB

  • Original 11.1 MB
  • After minification 10.8 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. Gogotea images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 193.2 kB

  • Original 274.1 kB
  • After minification 253.2 kB
  • After compression 80.9 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 193.2 kB or 70% of the original size.

CSS Optimization

-84%

Potential reduce by 169.3 kB

  • Original 201.3 kB
  • After minification 190.5 kB
  • After compression 31.9 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. Gogotea.jp needs all CSS files to be minified and compressed as it can save up to 169.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 75 (22%)

Requests Now

339

After Optimization

264

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

Accessibility Review

gogotea.jp accessibility score

77

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

gogotea.jp best practices score

54

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

Serves images with low resolution

General

Impact

Issue

High

Registers an unload listener

Low

Detected JavaScript libraries

High

Uses deprecated APIs

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

gogotea.jp SEO score

82

Search Engine Optimization Advices

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 doesn't use 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 Gogotea.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 Gogotea.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 Gogotea. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: