3.1 sec in total
700 ms
2.2 sec
151 ms
Welcome to standard-project.net homepage info - get ready to check Standard Project best content for Japan right away, or after learning these important things about standard-project.net
本サイトでは、環境やその問題、エコについて考えます。また、自分ができる環境問題への取り組みや対策、関連するサービスについてご案内します。
Visit standard-project.netWe analyzed Standard-project.net page load time and found that the first response time was 700 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
standard-project.net performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value4.6 s
35/100
25%
Value5.4 s
56/100
10%
Value260 ms
83/100
30%
Value0.03
100/100
15%
Value6.3 s
61/100
10%
700 ms
181 ms
608 ms
66 ms
419 ms
Our browser made a total of 38 requests to load all elements on the main page. We found that 45% of them (17 requests) were addressed to the original Standard-project.net, 18% (7 requests) were made to Apis.google.com and 5% (2 requests) were made to Twittell.net. The less responsive or slowest element that took the longest time to load (700 ms) belongs to the original domain Standard-project.net.
Page size can be reduced by 94.5 kB (55%)
172.6 kB
78.2 kB
In fact, the total size of Standard-project.net main page is 172.6 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. 40% of websites need less resources to load. Javascripts take 120.7 kB which makes up the majority of the site volume.
Potential reduce by 9.1 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 9.1 kB or 60% of the original size.
Potential reduce by 0 B
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. Standard Project images are well optimized though.
Potential reduce by 68.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 68.6 kB or 57% of the original size.
Potential reduce by 16.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. Standard-project.net needs all CSS files to be minified and compressed as it can save up to 16.8 kB or 85% of the original size.
Number of requests can be reduced by 16 (44%)
36
20
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Standard Project. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.
standard-project.net
700 ms
style.css
181 ms
jquery.js
608 ms
plusone.js
66 ms
jquery_table_hover.js
419 ms
jquery_mouse_over.js
426 ms
tweet100_3.js
546 ms
styles.css
215 ms
append.css
380 ms
cb=gapi.loaded_0
18 ms
eco_logo.gif
204 ms
bnr_efax.gif
416 ms
ico_pankuzu.gif
203 ms
ico_check_eco01.gif
204 ms
kankyo_img.png
380 ms
tweetthis100_3.png
193 ms
ttl_green.gif
363 ms
arrow.gif
372 ms
menu_ttl_green.gif
377 ms
menu_green.gif
409 ms
bg_footer.gif
544 ms
ga.js
21 ms
__utm.gif
21 ms
like.php
173 ms
tag.js
18 ms
cb=gapi.loaded_1
14 ms
fastbutton
73 ms
tag
11 ms
postmessageRelay
52 ms
cb=gapi.loaded_0
22 ms
cb=gapi.loaded_1
51 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
96 ms
api.js
59 ms
core:rpc:shindig.random:shindig.sha1.js
78 ms
2536007149-postmessagerelay.js
65 ms
vpc6VNjRPXV.js
287 ms
LVx-xkvaJ0b.png
323 ms
ya.js
327 ms
standard-project.net accessibility score
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
<frame> or <iframe> elements do not have a title
standard-project.net 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
standard-project.net SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Standard-project.net 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 Standard-project.net 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.
standard-project.net
Open Graph description is not detected on the main page of Standard Project. 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: