14.2 sec in total
337 ms
13.3 sec
537 ms
Visit green-japan.com now to see the best up-to-date Green Japan content for Japan and also check out these interesting facts you probably never knew about green-japan.com
登録すれば人事担当者から直接スカウトを受け取れます。企業とチャット形式でカジュアルにやり取りでき、全てがスマホで完結。隙間時間でキャリアチェンジを実現できます。
Visit green-japan.comWe analyzed Green-japan.com page load time and found that the first response time was 337 ms and then it took 13.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
green-japan.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value5.7 s
16/100
25%
Value9.2 s
13/100
10%
Value14,910 ms
0/100
30%
Value0.003
100/100
15%
Value32.0 s
0/100
10%
337 ms
1846 ms
773 ms
795 ms
94 ms
Our browser made a total of 147 requests to load all elements on the main page. We found that 5% of them (8 requests) were addressed to the original Green-japan.com, 61% (89 requests) were made to D3nqodvm1ngixa.cloudfront.net and 2% (3 requests) were made to Sync.fout.jp. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source D3nqodvm1ngixa.cloudfront.net.
Page size can be reduced by 3.1 MB (26%)
11.9 MB
8.8 MB
In fact, the total size of Green-japan.com main page is 11.9 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. 70% of websites need less resources to load. Images take 8.3 MB which makes up the majority of the site volume.
Potential reduce by 77.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. 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 77.7 kB or 78% of the original size.
Potential reduce by 117.7 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. Green Japan images are well optimized though.
Potential reduce by 733.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 733.2 kB or 62% of the original size.
Potential reduce by 2.2 MB
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. Green-japan.com needs all CSS files to be minified and compressed as it can save up to 2.2 MB or 91% of the original size.
Number of requests can be reduced by 64 (46%)
138
74
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Green Japan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
green-japan.com
337 ms
www.green-japan.com
1846 ms
common-dd40723a60239aaebb4f8c38cefdc52c.css
773 ms
contents-0241dc5c66ba5570f40d64bee4f4ef0e.css
795 ms
default-b730fb7a990cfbf1269014d44a4a208b.css
94 ms
footer-5325f2a81c3da933dadd54bf4e73677a.css
840 ms
layout-587ac8a41c62b4dfda794506b2f057f6.css
798 ms
common-6b9bb7bc82f9a4e8251a1a0ceae2cc73.css
807 ms
top-4511e179c1d2217d0605af75587c54fb.css
2434 ms
recommend-33a9f78384828041239feb61071719ed.css
1284 ms
jquery-ui-1.8.12.custom-50b80996e438cc99c1cbd6fb586795d1.css
963 ms
btn-f38ea17b73e56955d48cb385ff57ddfa.css
1575 ms
top-recommend-9e79f484f015bdad5eb89e6208150c92.css
1513 ms
material-design-lite-d25fdbc1c9b3c4b2d367e873188a431a.css
2639 ms
top-b807916646895c9e3ad2b27f3552f48f.css
1828 ms
application-69024a81e885510ef2843fec1d82e495.js
1448 ms
jquery.customSelect-ea6b4b0f47ab8b77feddebdecdc9446e.js
1636 ms
top-906b66258e777c4cc73f3e6518d33797.js
1853 ms
frontbackCarousel-2f963fbea77cb5b19126ec0f03faa946.js
2491 ms
jquery-ui-b484351a2e4608511dfb54e683a5ed38.js
1805 ms
favorite-8845da7e0d2745423a9eba66134c097c.js
1994 ms
intro.min-ed2a4b1a241fff9a6666048990e2694a.js
2163 ms
user_motivation-98152146ffb4801d2456f3b33cd71d39.js
2026 ms
material.min-0a45efdbb0de9dc5b6501042726207f8.js
3119 ms
jquery.touchwipe.min-2d672b2b6a4b7ad27ccf9a4257f6c955.js
2219 ms
ld.js
57 ms
tracker.js
82 ms
123.js
419 ms
common.png
194 ms
135723
87 ms
134985
86 ms
133485
86 ms
135793
292 ms
110916
381 ms
133982
310 ms
137591
365 ms
133046
312 ms
text_loading.gif
860 ms
126-6d01fddd3796d5b03a528430456c165d.gif
494 ms
1569-081ff9c69bf45e3ba1afa1530510daa5.gif
679 ms
75-9088ce327ec22bb1e60d28c2cfa4ff97.gif
507 ms
3493-be0ef99cee9494a9f145d213448355ae.gif
539 ms
3598-a9c5ee3a8c6f1fbfdaf1bb138e1e6070.gif
566 ms
2471-bd61b84da5a0e19ee110d560b78905ec.gif
686 ms
3722-619140c2c7bba24837689dcb52391a80.gif
735 ms
2574-fc68da5a20470da7cafb95b589cf325b.gif
736 ms
1980-7806838d3fb2f6dc0c6c08dae1e4683c.gif
742 ms
1324-09194272bad8fbbc7b4968c9fc250dcf.gif
892 ms
3553-4332f0f2a47830b18a8d1f2b81e1228a.gif
902 ms
1632-2112ef45f9f8a27fff9c00c034b537f0.gif
893 ms
top_bg.jpg
2086 ms
top_text-685538f4dd0a521e8ea2155d8721455a.png
1660 ms
common.png
1104 ms
tag.js
47 ms
segmentation.js
179 ms
gtm.js
94 ms
ct_tag.php
938 ms
search_hit_count
637 ms
event
65 ms
tag
32 ms
event
794 ms
analytics.js
52 ms
conversion_async.js
42 ms
46 ms
collect
9 ms
collect
67 ms
cnt
751 ms
38 ms
seo.php
1143 ms
log.php
799 ms
not_reply_message
191 ms
load_recommend_select_box
387 ms
1741 ms
fbds.js
349 ms
ya.js
723 ms
beacon.html
53 ms
g_loading.gif
1381 ms
i.js
69 ms
d509288a0d29439bb91a93a1974047cebe6d947b.1.js
125 ms
cnt
189 ms
2e51ab0b2854d9.js
620 ms
pixel
77 ms
cs
746 ms
Pug
84 ms
set
656 ms
sync
30 ms
sd
14 ms
sync
735 ms
tap.php
16 ms
30 ms
green_bigmining.js
65 ms
pb.js
929 ms
535 ms
sync
305 ms
mapuser
160 ms
sync
448 ms
e
29 ms
nr-885.min.js
37 ms
dis.aspx
701 ms
dmp
638 ms
gtm.js
106 ms
17 ms
1c874b5226
126 ms
137218
49 ms
check
399 ms
135719
1648 ms
135722
1276 ms
135841
33 ms
135842
1487 ms
135718
1700 ms
136688
33 ms
135947
642 ms
136685
1290 ms
136692
648 ms
135930
1259 ms
135931
2015 ms
136971
1282 ms
136951
1711 ms
136967
2629 ms
136691
1491 ms
135936
2227 ms
136687
2000 ms
135301
1706 ms
137119
4088 ms
135875
2434 ms
130435
2005 ms
130436
2774 ms
130444
2020 ms
134809
2243 ms
134805
2718 ms
134797
3553 ms
134807
2645 ms
134800
3052 ms
136460
2649 ms
136458
2907 ms
136461
3174 ms
130460
2779 ms
130454
4048 ms
129446
4683 ms
125704
4159 ms
107908
4423 ms
4954
4059 ms
icomoon.ttf
4027 ms
13 ms
18 ms
3079
3906 ms
90358
4155 ms
green-japan.com accessibility score
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
ARIA input fields do not have accessible names
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
Buttons do not have an accessible name
Links do not have a discernible name
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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>).
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.
green-japan.com 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
green-japan.com 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 Green-japan.com 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 Green-japan.com 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.
green-japan.com
Open Graph description is not detected on the main page of Green Japan. 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: