7.5 sec in total
970 ms
6.4 sec
179 ms
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.jpWe 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.
gpn.jp performance score
name
value
score
weighting
Value9.8 s
0/100
10%
Value15.4 s
0/100
25%
Value13.2 s
2/100
10%
Value140 ms
95/100
30%
Value0.176
68/100
15%
Value11.8 s
17/100
10%
970 ms
359 ms
23 ms
390 ms
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 size can be reduced by 294.6 kB (35%)
833.4 kB
538.8 kB
In fact, the total size of Gpn.jp main page is 833.4 kB. 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 438.8 kB which makes up the majority of the site volume.
Potential reduce by 20.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. 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.
Potential reduce by 6.2 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.
Potential reduce by 211.6 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 211.6 kB or 48% of the original size.
Potential reduce by 56.1 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.
Number of requests can be reduced by 49 (43%)
114
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.
gpn.jp
970 ms
import.css
359 ms
jquery.min.js
23 ms
rollover.js
390 ms
minmax.js
385 ms
members.js
395 ms
randam_banner.js
403 ms
runtime.js
34 ms
swiffy_menu.js
2468 ms
mt.js
922 ms
functions.js
757 ms
default.css
404 ms
module.css
398 ms
style.css
1052 ms
blog.css
753 ms
print.css
774 ms
bg_body.jpg
200 ms
logo.jpg
1073 ms
bg_bottom.jpg
708 ms
bg_search.jpg
351 ms
text_setsuden.gif
356 ms
bnr_300_sabameshi.jpg
765 ms
bnr_econet_300.gif
382 ms
bnr_300_g-law.jpg
592 ms
bnr_twitter.png
714 ms
bg_news.jpg
732 ms
bg_news_bottom.jpg
709 ms
ttl_news_gpn.jpg
921 ms
brn_past.jpg
1075 ms
btn_rss.jpg
1079 ms
ttl_news_member.jpg
1110 ms
icon_donut.gif
1082 ms
bnr_151_greenkounyu.gif
1140 ms
bnr_151_campaignmap.gif
1305 ms
csr2012_banner_orange_ja.gif
1457 ms
bnr_151_guideline.png
1476 ms
bg_area02.jpg
1478 ms
img_area02_1.jpg
1476 ms
img_area02_2.jpg
1491 ms
img_area02_7.jpg
1652 ms
img_area02_8.jpg
1838 ms
img_area02_6.jpg
1811 ms
img_area02_4.jpg
1833 ms
btn_net01.gif
1850 ms
btn_net02.gif
1887 ms
btn_net03.gif
2047 ms
btn_net04.gif
2183 ms
btn_net05.gif
2205 ms
btn_net06.gif
2216 ms
btn_net07.gif
2218 ms
btn_net08.gif
2216 ms
btn_net09.gif
2399 ms
btn_members.jpg
884 ms
btn_link.jpg
908 ms
btn_home.jpg
910 ms
btn_contact.jpg
954 ms
btn_sitemap.jpg
966 ms
btn_access.jpg
1263 ms
btn_english.jpg
1242 ms
navi_01.jpg
1257 ms
navi_02.jpg
1286 ms
navi_03.jpg
1401 ms
navi_04.jpg
1432 ms
navi_05.jpg
1583 ms
navi_06.jpg
1593 ms
img_banner.jpg
1679 ms
logo2.gif
1661 ms
btn_map.gif
1799 ms
infomart.gif
2513 ms
bnr_cardbox.jpg
2012 ms
bnr_fukkou.gif
1926 ms
ecoclub.gif
2164 ms
icon_arrow.gif
2493 ms
ecomark.gif
1982 ms
ga.js
10 ms
likebox.php
129 ms
__utm.gif
11 ms
hDvwL1_H7g-.css
286 ms
56WNbrUYLbL.css
355 ms
1kPfZUdGrka.js
492 ms
Yuj_Y8xNH2C.js
620 ms
Mpe38fuBVZ2.js
487 ms
n8qIhCw3vMx.js
487 ms
971111_485655594841769_1717906936_n.jpg
282 ms
188633_133008916773107_4562292_n.jpg
350 ms
10641300_305519009639069_7686308888459833692_n.jpg
504 ms
10509599_993211847433682_3432211686762288689_n.jpg
483 ms
185435_108083132627153_5213030_n.jpg
489 ms
10846112_10205776560716250_5612161869013465176_n.jpg
485 ms
940995_1531929587134716_7209574678830956578_n.jpg
486 ms
12794341_751618064940031_4040379710919301068_n.jpg
490 ms
526368_403486673084915_1208869714_n.jpg
551 ms
wL6VQj7Ab77.png
68 ms
s7jcwEQH7Sx.png
71 ms
VXcANLwwL5J.js
68 ms
AmlxWlqMvlv.js
70 ms
btn_members_o.jpg
182 ms
brn_past_o.jpg
201 ms
btn_rss_o.jpg
195 ms
btn_net01_o.gif
196 ms
btn_net02_o.gif
338 ms
btn_net03_o.gif
352 ms
btn_net04_o.gif
401 ms
btn_net05_o.gif
546 ms
btn_net06_o.gif
544 ms
btn_net07_o.gif
610 ms
btn_net08_o.gif
742 ms
btn_net09_o.gif
725 ms
btn_link_o.jpg
352 ms
btn_home_o.jpg
361 ms
btn_contact_o.jpg
372 ms
btn_sitemap_o.jpg
401 ms
btn_access_o.jpg
423 ms
btn_english_o.jpg
547 ms
btn_map_o.gif
710 ms
gpn.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Form elements do not have associated labels
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
gpn.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
gpn.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
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.
gpn.jp
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: