Tools & Wizards About Us
okiagari.net screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

okiagari.net

屍鬼

Page Load Speed

4.7 sec in total

First Response

882 ms

Resources Loaded

3.7 sec

Page Rendered

122 ms

okiagari.net screenshot

About Website

Click here to check amazing Okiagari content for Japan. Otherwise, check out these important facts you probably never knew about okiagari.net

TVアニメーション「屍鬼」公式サイト

Visit okiagari.net

Key Findings

We analyzed Okiagari.net page load time and found that the first response time was 882 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

okiagari.net performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

www.okiagari.net

882 ms

base.css

202 ms

top.jpg

1060 ms

aniplex.videoplayer.js

474 ms

bg_menu01.jpg

510 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 75% of them (21 requests) were addressed to the original Okiagari.net, 11% (3 requests) were made to Metrics.brightcove.com and 4% (1 request) were made to Aniplex.co.jp. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Okiagari.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 614.1 kB (45%)

Content Size

1.4 MB

After Optimization

756.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Okiagari.net main page is 1.4 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. 20% of websites need less resources to load. Javascripts take 779.3 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 77.0 kB

  • Original 100.9 kB
  • After minification 97.4 kB
  • After compression 23.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 77.0 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 429 B

  • Original 473.2 kB
  • After minification 472.8 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. Okiagari images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 522.4 kB

  • Original 779.3 kB
  • After minification 779.3 kB
  • After compression 257.0 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 522.4 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 14.3 kB

  • Original 16.8 kB
  • After minification 14.1 kB
  • After compression 2.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. Okiagari.net needs all CSS files to be minified and compressed as it can save up to 14.3 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (19%)

Requests Now

26

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Okiagari. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Network Requests Diagram

www.okiagari.net

www.okiagari.net

882 ms

base.css

base.css

202 ms

top.jpg

top.jpg

1060 ms

aniplex.videoplayer.js

aniplex.videoplayer.js

474 ms

bg_menu01.jpg

bg_menu01.jpg

510 ms

m_news01_off.jpg

m_news01_off.jpg

529 ms

m_intro01_off.jpg

m_intro01_off.jpg

530 ms

m_story01_off.jpg

m_story01_off.jpg

534 ms

m_chara01_off.jpg

m_chara01_off.jpg

533 ms

m_staff01_off.jpg

m_staff01_off.jpg

687 ms

m_gallery01_off.jpg

m_gallery01_off.jpg

721 ms

m_special01_off.jpg

m_special01_off.jpg

720 ms

m_package01_off.jpg

m_package01_off.jpg

731 ms

m_goods01_off.jpg

m_goods01_off.jpg

723 ms

m_music01_off.jpg

m_music01_off.jpg

878 ms

m_mail01_off.jpg

m_mail01_off.jpg

915 ms

bg_main01_l.jpg

bg_main01_l.jpg

1238 ms

bg_main01_r.jpg

bg_main01_r.jpg

1247 ms

bn_anx.gif

bn_anx.gif

923 ms

bn_noitamina.gif

bn_noitamina.gif

1044 ms

bn_jsq.jpg

bn_jsq.jpg

1069 ms

index.min.js

index.min.js

125 ms

bg_footer02.jpg

bg_footer02.jpg

980 ms

tracker

tracker

51 ms

5086031034001

5086031034001

198 ms

tracker

tracker

50 ms

I5YL3XhodRRsVWZe4NnZOhWnSAWgxhMoEr6SmzZieF43Mk7ZOBdeCVGrp9Eu+54J2xhySplfB5XHwQLXUmT9KH6+kPnQ7ZYuIEzNyfs1DLU1VU4SWZ6LkXGHsD1ZKbMw=

I5YL3XhodRRsVWZe4NnZOhWnSAWgxhMoEr6SmzZieF43Mk7ZOBdeCVGrp9Eu+54J2xhySplfB5XHwQLXUmT9KH6+kPnQ7ZYuIEzNyfs1DLU1VU4SWZ6LkXGHsD1ZKbMw=

6 ms

tracker

tracker

35 ms

Accessibility Review

okiagari.net accessibility score

88

Accessibility Issues

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

okiagari.net best practices score

58

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

okiagari.net 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 Okiagari.net 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 Okiagari.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.

Social Sharing Optimization

okiagari.net

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