Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

live2.nicovideo.jp

ニコニコ生放送

Page Load Speed

8.7 sec in total

First Response

1.2 sec

Resources Loaded

7 sec

Page Rendered

528 ms

live2.nicovideo.jp screenshot

About Website

Visit live2.nicovideo.jp now to see the best up-to-date Live 2 Nicovideo content for Japan and also check out these interesting facts you probably never knew about live2.nicovideo.jp

【ニコニコ生放送】は無料ですぐに楽しめる日本最大級のライブ配信サービス!最新作のアニメ・音楽ライブ・ゲーム実況・料理・歌ってみたなど、様々な番組をコメントで盛り上がりながら視聴できます。ニコニコ生放送アプリで、誰でも簡単に配信することができます。

Visit live2.nicovideo.jp

Key Findings

We analyzed Live2.nicovideo.jp page load time and found that the first response time was 1.2 sec and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

live2.nicovideo.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value20.3 s

0/100

10%

TBT (Total Blocking Time)

Value11,250 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value34.8 s

0/100

10%

Network Requests Diagram

live.nicovideo.jp

1158 ms

watching_reservation.css

632 ms

button.css

684 ms

reset.css

520 ms

base.css

858 ms

Our browser made a total of 191 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Live2.nicovideo.jp, 7% (14 requests) were made to Ads.nicovideo.jp and 5% (9 requests) were made to Live.nicovideo.jp. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Nl.simg.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (49%)

Content Size

2.2 MB

After Optimization

1.2 MB

In fact, the total size of Live2.nicovideo.jp main page is 2.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. 65% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 150.6 kB

  • Original 180.4 kB
  • After minification 171.2 kB
  • After compression 29.9 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 150.6 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 29.4 kB

  • Original 807.4 kB
  • After minification 778.0 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. Live 2 Nicovideo images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 789.1 kB

  • Original 1.1 MB
  • After minification 999.2 kB
  • After compression 317.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 789.1 kB or 71% of the original size.

CSS Optimization

-82%

Potential reduce by 118.4 kB

  • Original 145.2 kB
  • After minification 132.1 kB
  • After compression 26.8 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. Live2.nicovideo.jp needs all CSS files to be minified and compressed as it can save up to 118.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 112 (60%)

Requests Now

187

After Optimization

75

The browser has sent 187 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Live 2 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 79 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

live2.nicovideo.jp accessibility score

66

Accessibility Issues

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

High

[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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

live2.nicovideo.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

live2.nicovideo.jp SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Live2.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 Live2.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Live 2 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: