11.7 sec in total
1 sec
6.5 sec
4.2 sec
Click here to check amazing Enokido content for Japan. Otherwise, check out these important facts you probably never knew about enokido.net
Visit enokido.netWe analyzed Enokido.net page load time and found that the first response time was 1 sec and then it took 10.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
enokido.net performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value1.0 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
1030 ms
343 ms
411 ms
1282 ms
1118 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 35% of them (32 requests) were addressed to the original Enokido.net, 24% (22 requests) were made to Google.com and 19% (17 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Enokido.net.
Page size can be reduced by 756.7 kB (20%)
3.9 MB
3.1 MB
In fact, the total size of Enokido.net main page is 3.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. 60% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 45.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. This page needs HTML code to be minified as it can gain 7.1 kB, which is 12% 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 45.1 kB or 77% of the original size.
Potential reduce by 231.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. Enokido images are well optimized though.
Potential reduce by 477.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 477.8 kB or 69% of the original size.
Potential reduce by 2.6 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. Enokido.net needs all CSS files to be minified and compressed as it can save up to 2.6 kB or 74% of the original size.
Number of requests can be reduced by 16 (20%)
82
66
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Enokido. 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.
enokido.net
1030 ms
index2.css
343 ms
logo.gif
411 ms
d090723-1.jpg
1282 ms
d090722-1.jpg
1118 ms
d090721-1.jpg
1119 ms
d090721-2.jpg
1117 ms
d090715-1.jpg
1112 ms
d090715-2.jpg
1116 ms
blogger.js
102 ms
bunn2000.json
123 ms
d090515-1.jpg
3610 ms
d090515-2.jpg
2934 ms
m090512-1.jpg
2989 ms
d090512-2.jpg
1484 ms
d090510-1.jpg
1914 ms
d090510-2.jpg
2322 ms
d090509-1.jpg
2860 ms
d090509-2.jpg
2943 ms
d090509-3.jpg
3112 ms
d090508-1.jpg
3907 ms
20090506_4a019cee24ea9.jpg
3559 ms
maps
59 ms
maps
67 ms
embed
220 ms
embed
187 ms
d090505-1.jpg
4080 ms
20090507_4a021052cf914.jpg
4504 ms
d090505-2.jpg
3521 ms
20090507_4a020de21b62b.jpg
4737 ms
20090505_4a0006c32fc5e.jpg
4589 ms
20090504_49fdd0467ef1b.jpg
4001 ms
20090504_49fdbd3960886.jpg
5238 ms
20090503_49fd73ad5e683.jpg
4480 ms
20090503_49fd6ec101c81.jpg
5450 ms
profile.gif
4638 ms
rss.png
4676 ms
wwwcount.cgi
4887 ms
urchin.js
5 ms
__utm.gif
4 ms
js
164 ms
init_embed.js
98 ms
common.js
132 ms
map.js
132 ms
google4.png
70 ms
overlay.js
67 ms
util.js
294 ms
onion.js
61 ms
search_impl.js
294 ms
StaticMapService.GetMapImage
556 ms
stats.js
182 ms
openhand_8_8.cur
265 ms
StaticMapService.GetMapImage
325 ms
ViewportInfoService.GetViewportInfo
51 ms
controls.js
43 ms
ViewportInfoService.GetViewportInfo
139 ms
kh
454 ms
ViewportInfoService.GetViewportInfo
127 ms
ViewportInfoService.GetViewportInfo
124 ms
kh
433 ms
transparent.png
278 ms
css
286 ms
entity11.png
198 ms
vt
119 ms
vt
105 ms
vt
189 ms
vt
192 ms
vt
194 ms
vt
184 ms
vt
190 ms
vt
189 ms
vt
194 ms
vt
194 ms
mapcnt6.png
97 ms
vt
289 ms
vt
229 ms
vt
229 ms
vt
228 ms
vt
226 ms
vt
228 ms
vt
277 ms
vt
287 ms
vt
264 ms
vt
267 ms
tmapctrl.png
117 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
28 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
74 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
91 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
90 ms
AuthenticationService.Authenticate
70 ms
AuthenticationService.Authenticate
18 ms
enokido.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
Document doesn't have a <title> element
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
enokido.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
enokido.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Enokido.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Enokido.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.
enokido.net
Open Graph description is not detected on the main page of Enokido. 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: