9 sec in total
1.7 sec
5.6 sec
1.7 sec
Visit nakata.net now to see the best up-to-date Nakata content for Japan and also check out these interesting facts you probably never knew about nakata.net
中田英寿のオフィシャルホームページ「nakata.net」最新の活動情報をはじめ、メッセージやフォトギャラリーなど掲載。「club.nakata.net」では会員限定のコンテンツを展開中。
Visit nakata.netWe analyzed Nakata.net page load time and found that the first response time was 1.7 sec and then it took 7.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
nakata.net performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value17.2 s
0/100
25%
Value9.3 s
12/100
10%
Value320 ms
76/100
30%
Value0.659
8/100
15%
Value10.8 s
22/100
10%
1725 ms
296 ms
299 ms
300 ms
302 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 84% of them (97 requests) were addressed to the original Nakata.net, 9% (10 requests) were made to 0 and 3% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Nakata.net.
Page size can be reduced by 397.9 kB (33%)
1.2 MB
794.4 kB
In fact, the total size of Nakata.net main page is 1.2 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. 45% of websites need less resources to load. Images take 750.8 kB which makes up the majority of the site volume.
Potential reduce by 40.3 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 6.6 kB, which is 13% 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 40.3 kB or 80% of the original size.
Potential reduce by 79.9 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, Nakata needs image optimization as it can save up to 79.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 181.5 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 181.5 kB or 66% of the original size.
Potential reduce by 96.1 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. Nakata.net needs all CSS files to be minified and compressed as it can save up to 96.1 kB or 83% of the original size.
Number of requests can be reduced by 69 (60%)
115
46
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nakata. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
nakata.net
1725 ms
import.css
296 ms
buddybar.css
299 ms
theme-my-login.css
300 ms
polls-css.css
302 ms
responsive.css
435 ms
l10n.js
442 ms
jquery.js
881 ms
nakata_net.js
594 ms
snbinder-0.5.3.js
452 ms
jquery.bottom-1.0.js
452 ms
jquery.upload-1.0.2.js
581 ms
jquery.blockUI.js
734 ms
global.js
901 ms
cforms.css
603 ms
cforms.js
728 ms
swfobject.js
741 ms
wpp.css
756 ms
util.js
875 ms
jquery.dropdownPlain.js
879 ms
jquery.textarearesizer.compressed.js
889 ms
jquery.ah-placeholder.js
911 ms
jquery.jscrollpane.css
1021 ms
jquery.mousewheel.js
1023 ms
jquery.jscrollpane.min.js
1025 ms
jquery-ui.js
1183 ms
widgets.js
8 ms
ui.core.js
769 ms
polls-js.js
774 ms
common.css
880 ms
contents.css
883 ms
club.css
1030 ms
club2.css
912 ms
pull.css
918 ms
ie.css
1026 ms
single.css
1031 ms
nissan.css
1044 ms
calendar.css
149 ms
dc.js
229 ms
top-1.jpg
666 ms
title-share.gif
217 ms
btn-mixivoice.png
210 ms
ban-ta.gif
222 ms
ban-rn.gif
225 ms
logo-nakata.net.gif
217 ms
btn-member.gif
232 ms
btn-login.gif
647 ms
g-rtm.gif
660 ms
g-hidesmail.gif
676 ms
g-profile.gif
658 ms
g-data.gif
674 ms
g-photo.gif
671 ms
g-movie.gif
671 ms
g-wallpaper.gif
685 ms
g-feature.gif
685 ms
g-diary.gif
682 ms
mainvisual4.png
1291 ms
btn-detail.png
679 ms
title-siteupdates.png
713 ms
title-message-digest.png
729 ms
view.png
729 ms
btn-register.png
1257 ms
btn-archive.gif
729 ms
title-headline.png
913 ms
menui.jpg
1251 ms
comments.gif
1234 ms
share-twi.gif
1234 ms
share-fb.gif
1232 ms
nakata_cafe02.jpg
1415 ms
5ca400978d77d4ecefa5f037569605a3.jpg
1414 ms
news_sake_1.jpg
1278 ms
news_aera.png
1772 ms
present41.png
1572 ms
sakenomy1.png
2023 ms
ban-gallery.png
712 ms
ban-rtm.png
677 ms
ban-diary.png
724 ms
ban-store.png
1219 ms
ban-mail.png
1234 ms
bottom-1.jpg
688 ms
top-2.jpg
1218 ms
ban-ta.jpg
1264 ms
bottom-2.jpg
1257 ms
ban-rn44.jpg
1814 ms
ban-twitter.gif
1367 ms
ban-facebook.gif
1544 ms
ban-fanmail.gif
1543 ms
tit-mailmagazine.gif
1640 ms
mailadress.gif
1673 ms
like.php
668 ms
logo-ssu.gif
1300 ms
logo-sal.gif
1352 ms
icon-beginner.gif
1393 ms
icon-arrow1.gif
1419 ms
g-home_o.png
1481 ms
g-news.png
1488 ms
g-message.png
1511 ms
g-profile.png
1511 ms
g-gallery.png
1548 ms
g-cafe.png
1604 ms
g-club.png
1594 ms
icon-circle2.png
1589 ms
back-message.png
1623 ms
back-headline.jpg
1606 ms
bottom-headline.jpg
1644 ms
back.jpg
1701 ms
__utm.gif
396 ms
button.b059c0eb61ea902a882e5c5b3c66a17a.js
96 ms
back-1.jpg
1194 ms
back-2.jpg
1210 ms
back-mailadress.gif
1241 ms
btn-ftrregister.gif
1242 ms
zH0IPw-UmpL.js
344 ms
LVx-xkvaJ0b.png
370 ms
tweet_button.baa54ded21a982344c4ced326592f3de.ja.html
74 ms
jot
95 ms
nakata.net 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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA toggle fields do not have accessible names
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
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>).
nakata.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
Page has valid source maps
nakata.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nakata.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 Nakata.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.
nakata.net
Open Graph description is not detected on the main page of Nakata. 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: