4.4 sec in total
557 ms
3.4 sec
393 ms
Click here to check amazing Jeenet content. Otherwise, check out these important facts you probably never knew about jeenet.jp
Visit jeenet.jpWe analyzed Jeenet.jp page load time and found that the first response time was 557 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
jeenet.jp performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value6.3 s
10/100
25%
Value11.7 s
4/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value6.3 s
61/100
10%
557 ms
171 ms
334 ms
346 ms
25 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 39% of them (39 requests) were addressed to the original Jeenet.jp, 20% (20 requests) were made to Apis.google.com and 14% (14 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Jeenet.jp.
Page size can be reduced by 340.2 kB (41%)
821.1 kB
480.9 kB
In fact, the total size of Jeenet.jp main page is 821.1 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 361.8 kB 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 83% of the original size.
Potential reduce by 2.6 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. Jeenet images are well optimized though.
Potential reduce by 147.3 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 147.3 kB or 64% of the original size.
Potential reduce by 112.7 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. Jeenet.jp needs all CSS files to be minified and compressed as it can save up to 112.7 kB or 83% of the original size.
Number of requests can be reduced by 39 (41%)
96
57
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jeenet. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
jeenet.jp
557 ms
wp-emoji-release.min.js
171 ms
child-pages-shortcode.min.css
334 ms
style.css
346 ms
css
25 ms
responsive.css
344 ms
jquery.js
513 ms
jquery-migrate.min.js
349 ms
child-pages-shortcode.min.js
347 ms
jsn-script.js
497 ms
phplist.css
511 ms
platform.js
36 ms
plugins.js
761 ms
global.js
516 ms
wp-embed.min.js
518 ms
style.css
322 ms
sdk.js
75 ms
header_bg.jpg
336 ms
hiroba_logo.png
447 ms
main_s_img620.jpg
827 ms
jsn_logo.png
818 ms
nav_link_line.gif
335 ms
main_bn01.jpg
1145 ms
main_btn.jpg
627 ms
main_link01.jpg
446 ms
main_link02.jpg
637 ms
main_link03.jpg
638 ms
main_link04.jpg
825 ms
top_bn03.jpg
1119 ms
UVGP2015.jpg
824 ms
uvgp_interview02-300x89.jpg
1117 ms
news_subtitle.jpg
1118 ms
houdokyoku.jpg
1118 ms
METI1201_01_banner-150x150.jpg
1111 ms
link_icon_w.jpg
1207 ms
icon_twitter.jpg
1492 ms
hiroba_logo.jpg
1217 ms
logo_f02.jpg
1216 ms
widgets.js
59 ms
icon_link.jpg
1161 ms
footer_link_s.gif
2090 ms
ga.js
29 ms
_Incapsula_Resource
1233 ms
__utm.gif
99 ms
206 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
211 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
213 ms
cb=gapi.loaded_0
216 ms
cb=gapi.loaded_1
284 ms
fastbutton
341 ms
fastbutton
512 ms
fastbutton
510 ms
fastbutton
505 ms
fastbutton
504 ms
fastbutton
498 ms
fastbutton
497 ms
fastbutton
652 ms
fastbutton
616 ms
fastbutton
781 ms
fastbutton
630 ms
fastbutton
779 ms
xd_arbiter.php
149 ms
xd_arbiter.php
436 ms
syndication
632 ms
497577464546078720
655 ms
like.php
307 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
163 ms
postmessageRelay
521 ms
like.php
304 ms
rs=AGLTcCOETyu-Ugw4aZJoE538Nh1AB_7WNg
216 ms
like.php
362 ms
like.php
368 ms
like.php
477 ms
like.php
373 ms
like.php
376 ms
like.php
369 ms
like.php
369 ms
like.php
367 ms
like.php
399 ms
like.php
360 ms
wy1X4hBW7e7.js
505 ms
LVx-xkvaJ0b.png
511 ms
like.php
322 ms
cb=gapi.loaded_0
102 ms
cb=gapi.loaded_1
124 ms
grlryt2bdKIyfMSOhzd1eA.woff
236 ms
3193398744-postmessagerelay.js
42 ms
rpc:shindig_random.js
69 ms
proxy.jpg
84 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
10 ms
cb=gapi.loaded_0
9 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
6 ms
4PlTdwcV_normal.png
145 ms
BwIeTV_CUAAGx9p.jpg:small
266 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
39 ms
syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css
37 ms
proxy.jpg
42 ms
_Incapsula_Resource
169 ms
jot.html
5 ms
jeenet.jp accessibility score
jeenet.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
General
Impact
Issue
Detected JavaScript libraries
jeenet.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jeenet.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 Jeenet.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.
jeenet.jp
Open Graph description is not detected on the main page of Jeenet. 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: