Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    86% of websites

  • 97

    SEO

    Google-friendlier than
    93% of websites

goope.jp

ホームページ作成・ホームページ制作サービス「グーペ」

Page Load Speed

25.2 sec in total

First Response

821 ms

Resources Loaded

18.6 sec

Page Rendered

5.7 sec

goope.jp screenshot

About Website

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

グーペなら、専門的な知識がなくてもビジネスに役立つホームページが最短1日で完成。PCやスマートフォンから好きなときにホームページの更新ができます。独自ドメイン・ネット予約・お問い合わせフォームなどの機能にも対応。

Visit goope.jp

Key Findings

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

Performance Metrics

goope.jp performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value5.5 s

54/100

10%

TBT (Total Blocking Time)

Value1,100 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

goope.jp

821 ms

reset.css

646 ms

style.css

715 ms

style_campaign.css

740 ms

thickbox.css

753 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 79% of them (77 requests) were addressed to the original Goope.jp, 6% (6 requests) were made to Cache.img.gmo.jp and 2% (2 requests) were made to Castanet.kiban.paperboy.co.jp. The less responsive or slowest element that took the longest time to load (9 sec) belongs to the original domain Goope.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 440.9 kB (10%)

Content Size

4.3 MB

After Optimization

3.9 MB

In fact, the total size of Goope.jp main page is 4.3 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. 60% of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 122.5 kB

  • Original 138.4 kB
  • After minification 120.5 kB
  • After compression 15.9 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 18.0 kB, which is 13% 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 122.5 kB or 89% of the original size.

Image Optimization

-0%

Potential reduce by 8.7 kB

  • Original 3.7 MB
  • After minification 3.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. Goope images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 191.0 kB

  • Original 290.9 kB
  • After minification 226.7 kB
  • After compression 99.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 191.0 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 118.7 kB

  • Original 140.3 kB
  • After minification 115.4 kB
  • After compression 21.6 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. Goope.jp needs all CSS files to be minified and compressed as it can save up to 118.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (42%)

Requests Now

96

After Optimization

56

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

Accessibility Review

goope.jp accessibility score

75

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

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

goope.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

goope.jp SEO score

97

Search Engine Optimization Advices

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 Goope.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 Goope.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 Goope. 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: