Tools & Wizards About Us
no-rin.tv screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

no-rin.tv

TVアニメ　『のうりん』公式サイト

Page Load Speed

3.8 sec in total

First Response

515 ms

Resources Loaded

3.2 sec

Page Rendered

164 ms

no-rin.tv screenshot

About Website

Visit no-rin.tv now to see the best up-to-date No Rin content for Japan and also check out these interesting facts you probably never knew about no-rin.tv

のうりん　アニメオフィシャルサイト

Visit no-rin.tv

Key Findings

We analyzed No-rin.tv page load time and found that the first response time was 515 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

no-rin.tv performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value32.0 s

0/100

25%

SI (Speed Index)

Value9.6 s

11/100

10%

TBT (Total Blocking Time)

Value890 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.256

48/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

no-rin.tv

515 ms

top.css

171 ms

jquery.jscrollpane.css

338 ms

colorbox.css

341 ms

jquery.min.js

7 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 54% of them (49 requests) were addressed to the original No-rin.tv, 22% (20 requests) were made to Platform.twitter.com and 7% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

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

Content Size

4.0 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of No-rin.tv main page is 4.0 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. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 14.1 kB

  • Original 20.5 kB
  • After minification 20.0 kB
  • After compression 6.4 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 14.1 kB or 69% of the original size.

Image Optimization

-52%

Potential reduce by 2.0 MB

  • Original 3.8 MB
  • After minification 1.8 MB

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, No Rin needs image optimization as it can save up to 2.0 MB or 52% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 9.9 kB

  • Original 219.1 kB
  • After minification 219.1 kB
  • After compression 209.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-26%

Potential reduce by 908 B

  • Original 3.5 kB
  • After minification 3.5 kB
  • After compression 2.5 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. No-rin.tv needs all CSS files to be minified and compressed as it can save up to 908 B or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (45%)

Requests Now

86

After Optimization

47

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of No Rin. 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 as a result speed up the page load time.

Network Requests Diagram

no-rin.tv

no-rin.tv

515 ms

top.css

top.css

171 ms

jquery.jscrollpane.css

jquery.jscrollpane.css

338 ms

colorbox.css

colorbox.css

341 ms

jquery.min.js

jquery.min.js

7 ms

queryLoader.js

queryLoader.js

353 ms

rollover.js

rollover.js

351 ms

footerFixed.js

footerFixed.js

351 ms

jquery.mousewheel.js

jquery.mousewheel.js

353 ms

jquery.jscrollpane.js

jquery.jscrollpane.js

507 ms

jquery.colorbox.js

jquery.colorbox.js

510 ms

bookmark_button.js

bookmark_button.js

8 ms

bookmark_button.js

bookmark_button.js

17 ms

ga.js

ga.js

19 ms

button-only.gif

button-only.gif

17 ms

main_bg.gif

main_bg.gif

183 ms

p_mainvisual02.png

p_mainvisual02.png

1539 ms

p_logo_l.png

p_logo_l.png

338 ms

b_menu01.png

b_menu01.png

182 ms

b_menu02.png

b_menu02.png

182 ms

b_menu03.png

b_menu03.png

182 ms

b_menu04.png

b_menu04.png

348 ms

b_menu05.png

b_menu05.png

353 ms

b_menu06.png

b_menu06.png

352 ms

b_menu07.png

b_menu07.png

349 ms

b_menu08.png

b_menu08.png

516 ms

b_menu09.png

b_menu09.png

521 ms

bana_miracle.jpg

bana_miracle.jpg

687 ms

bana_ikkimi.jpg

bana_ikkimi.jpg

688 ms

tp_norintv.jpg

tp_norintv.jpg

689 ms

base_tw.png

base_tw.png

681 ms

b_promo2.png

b_promo2.png

1025 ms

logo_foot.gif

logo_foot.gif

843 ms

bana_gabunko.jpg

bana_gabunko.jpg

856 ms

bana_frontierworks.gif

bana_frontierworks.gif

858 ms

widgets.js

widgets.js

78 ms

base_news.png

base_news.png

1017 ms

bg_foot.png

bg_foot.png

1000 ms

t_share.gif

t_share.gif

1014 ms

button-only.gif

button-only.gif

32 ms

__utm.gif

__utm.gif

40 ms

like.php

like.php

262 ms

plusone.js

plusone.js

63 ms

t_menu.gif

t_menu.gif

947 ms

overlay.png

overlay.png

1098 ms

controls.png

controls.png

1112 ms

border.png

border.png

1283 ms

loading_background.png

loading_background.png

1117 ms

loading.gif

loading.gif

1118 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

192 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

33 ms

fastbutton

fastbutton

44 ms

postmessageRelay

postmessageRelay

75 ms

developers.google.com

developers.google.com

1563 ms

544727282-postmessagerelay.js

544727282-postmessagerelay.js

24 ms

rpc:shindig_random.js

rpc:shindig_random.js

11 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

settings

settings

97 ms

q6SaOKt-Ruv.js

q6SaOKt-Ruv.js

23 ms

FEppCFCt76d.png

FEppCFCt76d.png

15 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

27 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

53 ms

norin_anime

norin_anime

60 ms

embeds

embeds

48 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

39 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

31 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

50 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

81 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

63 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

108 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

110 ms

_buildManifest.js

_buildManifest.js

138 ms

_ssgManifest.js

_ssgManifest.js

139 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

28 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

27 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

28 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

60 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

52 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

81 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

32 ms

b_menu01_o.png

b_menu01_o.png

171 ms

b_menu02_o.png

b_menu02_o.png

175 ms

b_menu03_o.png

b_menu03_o.png

171 ms

b_menu04_o.png

b_menu04_o.png

174 ms

b_menu05_o.png

b_menu05_o.png

173 ms

b_menu06_o.png

b_menu06_o.png

172 ms

b_menu07_o.png

b_menu07_o.png

338 ms

b_menu08_o.png

b_menu08_o.png

337 ms

b_menu09_o.png

b_menu09_o.png

341 ms

b_promo2_o.png

b_promo2_o.png

343 ms

Accessibility Review

no-rin.tv accessibility score

71

Accessibility Issues

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

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

High

Image elements do not have [alt] attributes

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

no-rin.tv best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

SEO Factors

no-rin.tv SEO score

67

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise No-rin.tv can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that No-rin.tv 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

no-rin.tv

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