Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

gogo.gs

ガソリン価格比較サイト gogo.gs(ゴーゴージーエス)

Page Load Speed

1.9 sec in total

First Response

73 ms

Resources Loaded

1.6 sec

Page Rendered

205 ms

gogo.gs screenshot

About Website

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

ガソリン価格比較サイト gogo.gs は、ガソリン価格やガソリンスタンド情報を共有するサービスです。掲載情報は、全国のドライバーの皆さんやガソリンスタンドの方から寄せられた情報をリアルタイムに掲載しています。

Visit gogo.gs

Key Findings

We analyzed Gogo.gs page load time and found that the first response time was 73 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

gogo.gs performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value9.1 s

13/100

10%

TBT (Total Blocking Time)

Value1,810 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.14

79/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

gogo.gs

73 ms

master.css

16 ms

CountUp_EUC.js

27 ms

adsbygoogle.js

8 ms

jquery.js

112 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Gogo.gs, 29% (36 requests) were made to Cdn.gogo.gs and 11% (14 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (915 ms) relates to the external source Corism.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 504.0 kB (42%)

Content Size

1.2 MB

After Optimization

694.1 kB

In fact, the total size of Gogo.gs main page is 1.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. 75% 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. Javascripts take 705.9 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 105.3 kB

  • Original 142.8 kB
  • After minification 141.5 kB
  • After compression 37.6 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 105.3 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 9.3 kB

  • Original 301.8 kB
  • After minification 292.5 kB

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. Gogo images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 351.0 kB

  • Original 705.9 kB
  • After minification 689.0 kB
  • After compression 355.0 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 351.0 kB or 50% of the original size.

CSS Optimization

-81%

Potential reduce by 38.5 kB

  • Original 47.6 kB
  • After minification 35.6 kB
  • After compression 9.0 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. Gogo.gs needs all CSS files to be minified and compressed as it can save up to 38.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 83 (69%)

Requests Now

120

After Optimization

37

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

Accessibility Review

gogo.gs accessibility score

59

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

gogo.gs best practices score

83

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

Page has valid source maps

SEO Factors

gogo.gs SEO score

85

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gogo.gs can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Gogo.gs main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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