5.8 sec in total
557 ms
4.9 sec
364 ms
Welcome to i.nicovideo.jp homepage info - get ready to check I Nicovideo best content for Japan right away, or after learning these important things about i.nicovideo.jp
Visit i.nicovideo.jpWe analyzed I.nicovideo.jp page load time and found that the first response time was 557 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
i.nicovideo.jp performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value20.2 s
0/100
25%
Value16.9 s
0/100
10%
Value2,210 ms
6/100
30%
Value0
100/100
15%
Value22.5 s
1/100
10%
557 ms
559 ms
473 ms
474 ms
489 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original I.nicovideo.jp, 34% (39 requests) were made to Uni.res.nimg.jp and 18% (21 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Tn-skr4.smilevideo.jp.
Page size can be reduced by 587.7 kB (35%)
1.7 MB
1.1 MB
In fact, the total size of I.nicovideo.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. 55% of websites need less resources to load. Images take 914.1 kB which makes up the majority of the site volume.
Potential reduce by 33.5 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 33.5 kB or 79% of the original size.
Potential reduce by 34.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. I Nicovideo images are well optimized though.
Potential reduce by 413.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 413.3 kB or 71% of the original size.
Potential reduce by 106.4 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. I.nicovideo.jp needs all CSS files to be minified and compressed as it can save up to 106.4 kB or 84% of the original size.
Number of requests can be reduced by 55 (49%)
112
57
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I Nicovideo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
i.nicovideo.jp
557 ms
www.nicovideo.jp
559 ms
ini.css
473 ms
zero_common.css
474 ms
zero_index.css
489 ms
timeshift.css
497 ms
zero_default.css
496 ms
index_overseas.css
497 ms
setcountry.css
626 ms
prototype.js
936 ms
common.js
648 ms
swfobject.js
661 ms
nicolib.js
661 ms
ads.js
829 ms
ads-2.15.0.min.js
1306 ms
__utm.js
945 ms
1252970284.js
22 ms
base.js
805 ms
jquery-1.6.1.min.js
1349 ms
contentslide.js
823 ms
index_overseas.js
967 ms
nicolib-SuggestSearch.js
1372 ms
setcountry.js
991 ms
siteHeader.css
1084 ms
site_header_extension.css
1084 ms
nicolib-CommonNotificationHeader.css
1128 ms
siteHeader.js
1156 ms
nicolib-CommonNotificationHeader.js
1394 ms
notify.js
497 ms
enquete.js
826 ms
ga.js
7 ms
__utm.gif
532 ms
__utm.gif
42 ms
__utm.gif
48 ms
smile
711 ms
smile
1647 ms
smile
491 ms
smile
484 ms
co39593.jpg
957 ms
smile
883 ms
smile
1063 ms
smile
1321 ms
smile
1409 ms
smile
1583 ms
smile
1758 ms
smile
498 ms
smile
522 ms
smile
533 ms
smile
552 ms
smile
734 ms
smile
637 ms
co3185582.jpg
817 ms
co13383.jpg
851 ms
co2380691.jpg
700 ms
smile
628 ms
smile
773 ms
smile
919 ms
smile
1072 ms
smile
1314 ms
to_member_en-us.png
195 ms
icon_new.png
197 ms
bnr_psvita_us.jpg
198 ms
logo_jasrac.png
197 ms
smile
1501 ms
smile
1515 ms
smile
1546 ms
smile
1547 ms
smile
1560 ms
collect
98 ms
logo.png
179 ms
icon.png
307 ms
icon_svc.png
323 ms
trendy_tags_icon.png
323 ms
top_baloon_cur.png
323 ms
icon_cur.png
325 ms
widgets.js
122 ms
getAdvertisements.jsonp
345 ms
bg_footbtn.png
266 ms
icon_arrow_gray.png
387 ms
icon_cur.png
413 ms
icon_langselector.png
412 ms
arrow_default.png
412 ms
likebox.php
234 ms
410ucuAGgaJ.css
290 ms
tSbl8xBI27R.css
363 ms
Czh0gDTFcBt.css
430 ms
Ek6lpayKeeB.css
573 ms
EoarYgA68t4.css
563 ms
1kPfZUdGrka.js
625 ms
Yuj_Y8xNH2C.js
658 ms
Mpe38fuBVZ2.js
494 ms
n8qIhCw3vMx.js
499 ms
QKy94bWvcbp.js
583 ms
6q5od22S-uf.js
583 ms
7B-2ZS3Qt8r.js
699 ms
qcMicXoOToy.js
830 ms
57RpJa05x58.js
705 ms
a5f0d282c274b562201a0490a2003265.jpeg
1227 ms
logImpression.jsonp
331 ms
logImpression.jsonp
360 ms
688c978360bc6436d2de501b60c406b9.jpeg
1507 ms
10922691_793049437429602_1041946678666520000_n.png
561 ms
1601058_793049497429596_3727900166572134283_n.png
620 ms
155096_986086461459231_5176813881105659842_n.png
825 ms
1620514_984562214944989_7021708737031708527_n.png
957 ms
12115814_983482948386249_1969179850019632781_n.jpg
820 ms
12804852_981478061920071_5097372619484447430_n.png
822 ms
944864_980823611985516_42177249148644165_n.png
1023 ms
wL6VQj7Ab77.png
80 ms
s7jcwEQH7Sx.png
79 ms
QDwYpIaRyfG.png
78 ms
pimRBh7B6ER.png
78 ms
K00K-UgnsKu.png
77 ms
VXcANLwwL5J.js
69 ms
AmlxWlqMvlv.js
135 ms
i.nicovideo.jp 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
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
i.nicovideo.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
i.nicovideo.jp SEO score
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
Tap targets are not sized appropriately
JA
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise I.nicovideo.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that I.nicovideo.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.
i.nicovideo.jp
Open Graph description is not detected on the main page of I Nicovideo. 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: