8.2 sec in total
540 ms
7.1 sec
578 ms
Welcome to unext.jp homepage info - get ready to check U NEXT best content for Japan right away, or after learning these important things about unext.jp
<31日間無料トライアル実施中>映画/ドラマ/アニメ/電子書籍を観るならU-NEXT(ユーネクスト)。名作はもちろん最新作も!豊富な作品の中からお好きな動画を見つけて、是非お楽しみください。
Visit unext.jpWe analyzed Unext.jp page load time and found that the first response time was 540 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
unext.jp performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value33.6 s
0/100
25%
Value27.3 s
0/100
10%
Value65,240 ms
0/100
30%
Value0
100/100
15%
Value79.8 s
0/100
10%
540 ms
537 ms
827 ms
372 ms
24 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Unext.jp, 47% (56 requests) were made to Imgc.nxtv.jp and 8% (10 requests) were made to Video.unext.jp. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Imgc.nxtv.jp.
Page size can be reduced by 375.4 kB (66%)
573.1 kB
197.7 kB
In fact, the total size of Unext.jp main page is 573.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. 85% 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. HTML takes 189.1 kB which makes up the majority of the site volume.
Potential reduce by 169.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 51.6 kB, which is 27% 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 169.1 kB or 89% of the original size.
Potential reduce by 220 B
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. U NEXT images are well optimized though.
Potential reduce by 75.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 75.5 kB or 53% of the original size.
Potential reduce by 130.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. Unext.jp needs all CSS files to be minified and compressed as it can save up to 130.6 kB or 80% of the original size.
Number of requests can be reduced by 33 (33%)
101
68
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of U NEXT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
unext.jp
540 ms
p.unext.jp
537 ms
video.unext.jp
827 ms
preinitialize.js
372 ms
notosansjapanese.css
24 ms
rev20160222184210.all.min.css
551 ms
ClickIndex.js
556 ms
rev20160222184210.all.min.js
1366 ms
analytics.unext.js
392 ms
sdk.js
169 ms
ajax-loader.gif
206 ms
loading.png
205 ms
widgets.js
146 ms
SID0021135.png
344 ms
NotoSansJP-Light.woff
122 ms
NotoSansJP-Thin.woff
159 ms
NotoSansJP-DemiLight.woff
353 ms
NotoSansJP-Regular.woff
366 ms
NotoSansJP-Medium.woff
462 ms
NotoSansJP-Bold.woff
460 ms
NotoSansJP-Black.woff
460 ms
unx-icon-font.ttf
613 ms
backdrop2_night.jpg
1221 ms
SID0020807.png
485 ms
SID0020984.png
342 ms
SID0021387.png
484 ms
SID0021504.png
342 ms
SID0021320.png
600 ms
SID0021651.png
338 ms
SID0021440.png
455 ms
SID0020590.png
364 ms
SID0020594.png
454 ms
SID0020518.png
453 ms
SID0021174.png
457 ms
SID0021326.png
459 ms
SID0021398.png
460 ms
SID0020044.png
457 ms
SID0021350.png
1051 ms
SID0020924.png
782 ms
SID0020441.png
598 ms
SID0020373.png
599 ms
SID0019584.png
599 ms
SID0017835.png
638 ms
SID0013370.png
600 ms
SID0013325.png
602 ms
SID0012941.png
639 ms
SID0012863.png
636 ms
SID0012129.png
637 ms
SID0011316.png
659 ms
SID0011221.png
645 ms
SID0003980.png
717 ms
SID0002885.png
717 ms
SID0003730.png
2998 ms
SID0018939.png
2814 ms
SID0003836.png
1049 ms
SID0019918.png
843 ms
SID0003759.png
884 ms
SID0014980.png
1279 ms
20100528.js
185 ms
20120528134854.js
369 ms
exec.js
368 ms
170 ms
xd_arbiter.php
174 ms
xd_arbiter.php
313 ms
SID0003894.png
737 ms
SID0017526.png
819 ms
SID0018417.png
712 ms
SID0014864.png
713 ms
SID0020656.png
638 ms
SID0011481.png
600 ms
SID0020236.png
636 ms
SID0003935.png
638 ms
SID0003895.png
632 ms
SID0018838.png
633 ms
SID0017410.png
655 ms
SID0003827.png
663 ms
SID0016037.png
640 ms
SID0020655.png
544 ms
SID0011480.png
627 ms
SID0010931.png
560 ms
SID0019833.png
595 ms
SID0021132.png
572 ms
SID0021133.png
596 ms
SID0021134.png
625 ms
l_mark.png
192 ms
td-1.2.0.js
541 ms
analytics.js
102 ms
tag.js
100 ms
tag
13 ms
linkid.js
30 ms
tag
12 ms
collect
19 ms
collect
62 ms
page_transition_log
44 ms
nr-768.min.js
52 ms
fbds.js
39 ms
aiom.js
399 ms
conversion_async.js
51 ms
collect
20 ms
12 ms
06aabe30ae
64 ms
42 ms
42 ms
50 ms
47 ms
42 ms
38 ms
52 ms
50 ms
49 ms
47 ms
47 ms
42 ms
aio
164 ms
pixel
21 ms
csync
732 ms
csync
161 ms
csync
161 ms
unext.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
[role]s are not contained by their required parent element
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
Image elements do not have [alt] attributes
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
unext.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
Page has valid source maps
unext.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 doesn't use legible font sizes
Tap targets are not sized appropriately
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Unext.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 Unext.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.
unext.jp
Open Graph data is detected on the main page of U NEXT. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: