Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

getgoal.jp

HAYABUSA MAGAZINE:|ファッション・スニーカー・アート・海外ニュースを紹介するウェブマガジン

Page Load Speed

10.5 sec in total

First Response

2.8 sec

Resources Loaded

6.9 sec

Page Rendered

836 ms

getgoal.jp screenshot

About Website

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

ハヤブサマガジンは2005年にスタートした日本では知られていないファッション・スニーカー・アート・海外ニュースを紹介するウェブマガジン

Visit getgoal.jp

Key Findings

We analyzed Getgoal.jp page load time and found that the first response time was 2.8 sec and then it took 7.7 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

getgoal.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value1,210 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value16.5 s

5/100

10%

Network Requests Diagram

getgoal.jp

2826 ms

wp-emoji-release.min.js

1215 ms

colorbox.css

354 ms

style.css

1189 ms

visual-custom.css

349 ms

Our browser made a total of 148 requests to load all elements on the main page. We found that 32% of them (47 requests) were addressed to the original Getgoal.jp, 15% (22 requests) were made to B.hatena.ne.jp and 15% (22 requests) were made to Graph.facebook.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Getgoal.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 386.3 kB (16%)

Content Size

2.4 MB

After Optimization

2.1 MB

In fact, the total size of Getgoal.jp main page is 2.4 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. 80% 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 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 69.5 kB

  • Original 88.7 kB
  • After minification 88.5 kB
  • After compression 19.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 69.5 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 102.2 kB

  • Original 1.9 MB
  • After minification 1.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. Getgoal images are well optimized though.

JavaScript Optimization

-28%

Potential reduce by 74.4 kB

  • Original 265.5 kB
  • After minification 263.2 kB
  • After compression 191.1 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 74.4 kB or 28% of the original size.

CSS Optimization

-80%

Potential reduce by 140.3 kB

  • Original 175.1 kB
  • After minification 170.4 kB
  • After compression 34.8 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. Getgoal.jp needs all CSS files to be minified and compressed as it can save up to 140.3 kB or 80% of the original size.

Requests Breakdown

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

Requests Now

144

After Optimization

75

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

Accessibility Review

getgoal.jp accessibility score

78

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

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

getgoal.jp best practices score

67

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

getgoal.jp 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

Links do not have descriptive text

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