8.1 sec in total
1.1 sec
6.7 sec
277 ms
Welcome to nextcommons.jp homepage info - get ready to check Ne Xt Commons best content right away, or after learning these important things about nextcommons.jp
国立情報学研究所が開発したNetCommons(ネットコモンズ)2.0に独自の機能を追加し、SaaS形式で提供するサービスです。NeXtCommons(ネクストコモンズ)なら、学校、市町村、中小企業などで情報発信と情報共有が簡単・安全に始められます。
Visit nextcommons.jpWe analyzed Nextcommons.jp page load time and found that the first response time was 1.1 sec and then it took 7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
nextcommons.jp performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value4.6 s
35/100
25%
Value5.3 s
58/100
10%
Value50 ms
100/100
30%
Value0.002
100/100
15%
Value5.5 s
70/100
10%
1110 ms
360 ms
343 ms
947 ms
361 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 97% of them (60 requests) were addressed to the original Nextcommons.jp, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Nextcommons.jp.
Page size can be reduced by 908.9 kB (53%)
1.7 MB
813.4 kB
In fact, the total size of Nextcommons.jp main page is 1.7 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. 30% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 59.6 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 59.6 kB or 84% of the original size.
Potential reduce by 843.5 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. Obviously, Ne Xt Commons needs image optimization as it can save up to 843.5 kB or 52% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 5.8 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 5.8 kB or 23% of the original size.
Number of requests can be reduced by 27 (44%)
61
34
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ne Xt Commons. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
nextcommons.jp
1110 ms
index.php
360 ms
lang_common.js
343 ms
index.php
947 ms
blank.gif
361 ms
setting_upperleft.gif
351 ms
setting_upper.gif
356 ms
setting_upperright.gif
361 ms
setting_left.gif
640 ms
setting_dot.gif
697 ms
setting_close.gif
700 ms
setting_right.gif
707 ms
setting_belowleft.gif
711 ms
setting_below.gif
994 ms
setting_belowright.gif
1044 ms
nextcommons.jp
1140 ms
nextcommons.jp
1136 ms
nextcommons.jp
1861 ms
nextcommons.jp
1612 ms
nextcommons.jp
1403 ms
nextcommons.jp
1461 ms
nextcommons.jp
1903 ms
nextcommons.jp
1555 ms
nextcommons.jp
1806 ms
rss.gif
1797 ms
body_top_left.gif
1901 ms
body_top.gif
1974 ms
body_top_right.gif
2158 ms
body_left.gif
2165 ms
nextcommons.jp
5195 ms
body_right.gif
2251 ms
body_bottom_left.gif
2288 ms
body_bottom.gif
2333 ms
body_bottom_right.gif
2499 ms
nextcommons.jp
2719 ms
nextcommons.jp
2637 ms
nextcommons.jp
2714 ms
ga.js
8 ms
nextcommons.jp
2847 ms
__utm.gif
14 ms
nextcommons.jp
2614 ms
nextcommons.jp
3013 ms
nextcommons.jp
3172 ms
nextcommons.jp
2817 ms
nextcommons.jp
3322 ms
nextcommons.jp
2711 ms
nextcommons.jp
2893 ms
nextcommons.jp
3078 ms
nextcommons.jp
3080 ms
nextcommons.jp
3430 ms
nextcommons.jp
3076 ms
nextcommons.jp
3431 ms
nextcommons.jp
3307 ms
nextcommons.jp
3103 ms
nextcommons.jp
3268 ms
nextcommons.jp
3156 ms
nextcommons.jp
3348 ms
nextcommons.jp
3268 ms
nextcommons.jp
3201 ms
nextcommons.jp
3072 ms
nextcommons.jp
3700 ms
nextcommons.jp
3352 ms
nextcommons.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.
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
nextcommons.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
nextcommons.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nextcommons.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 Nextcommons.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.
nextcommons.jp
Open Graph description is not detected on the main page of Ne Xt Commons. 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: