Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

gpn.jp

グリーン購入ネットワーク

Page Load Speed

7.5 sec in total

First Response

970 ms

Resources Loaded

6.4 sec

Page Rendered

179 ms

gpn.jp screenshot

About Website

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

環境配慮製品、サービスの優先的購入を進めるグリーン購入ネットワーク(GPN)

Visit gpn.jp

Key Findings

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

Performance Metrics

gpn.jp performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.176

68/100

15%

TTI (Time to Interactive)

Value11.8 s

17/100

10%

Network Requests Diagram

gpn.jp

970 ms

import.css

359 ms

jquery.min.js

23 ms

rollover.js

390 ms

minmax.js

385 ms

Our browser made a total of 115 requests to load all elements on the main page. We found that 79% of them (91 requests) were addressed to the original Gpn.jp, 9% (10 requests) were made to Static.xx.fbcdn.net and 8% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Gpn.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 629.1 kB (54%)

Content Size

1.2 MB

After Optimization

538.8 kB

In fact, the total size of Gpn.jp 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. 25% of websites need less resources to load. Javascripts take 773.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 20.7 kB

  • Original 27.0 kB
  • After minification 22.5 kB
  • After compression 6.4 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 4.5 kB, which is 17% 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 20.7 kB or 77% of the original size.

Image Optimization

-2%

Potential reduce by 6.2 kB

  • Original 301.1 kB
  • After minification 294.9 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. Gpn images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 546.1 kB

  • Original 773.3 kB
  • After minification 761.6 kB
  • After compression 227.2 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 546.1 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 56.1 kB

  • Original 66.4 kB
  • After minification 48.0 kB
  • After compression 10.3 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. Gpn.jp needs all CSS files to be minified and compressed as it can save up to 56.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (43%)

Requests Now

114

After Optimization

65

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

Accessibility Review

gpn.jp accessibility score

73

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

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

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

gpn.jp SEO score

87

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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