Tools & Wizards About Us
strike-the-blood.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

strike-the-blood.com

TVアニメ「ストライク・ザ・ブラッド」公式サイト

Page Load Speed

5.2 sec in total

First Response

435 ms

Resources Loaded

4.6 sec

Page Rendered

175 ms

strike-the-blood.com screenshot

About Website

Click here to check amazing Strike The Blood content for United States. Otherwise, check out these important facts you probably never knew about strike-the-blood.com

ライトノベル市場で人気急上昇中、大きな支持を得ている電撃文庫の「ストライク・ザ・ブラッド」がTVアニメ化！

Visit strike-the-blood.com

Key Findings

We analyzed Strike-the-blood.com page load time and found that the first response time was 435 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

strike-the-blood.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value22.7 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value1,570 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.579

12/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

strike-the-blood.com

435 ms

www.strike-the-blood.com

956 ms

sliding.css

523 ms

base.css

350 ms

style.css

712 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 68% of them (67 requests) were addressed to the original Strike-the-blood.com, 6% (6 requests) were made to Pbs.twimg.com and 5% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Strike-the-blood.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 326.2 kB (8%)

Content Size

3.9 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Strike-the-blood.com main page is 3.9 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.5 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 33.9 kB

  • Original 39.1 kB
  • After minification 36.9 kB
  • After compression 5.2 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.9 kB or 87% of the original size.

Image Optimization

-3%

Potential reduce by 110.0 kB

  • Original 3.5 MB
  • After minification 3.4 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. Strike The Blood images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 160.9 kB

  • Original 277.7 kB
  • After minification 262.7 kB
  • After compression 116.9 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 160.9 kB or 58% of the original size.

CSS Optimization

-82%

Potential reduce by 21.5 kB

  • Original 26.3 kB
  • After minification 20.3 kB
  • After compression 4.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. Strike-the-blood.com needs all CSS files to be minified and compressed as it can save up to 21.5 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

92

After Optimization

73

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

strike-the-blood.com

strike-the-blood.com

435 ms

www.strike-the-blood.com

www.strike-the-blood.com

956 ms

sliding.css

sliding.css

523 ms

base.css

base.css

350 ms

style.css

style.css

712 ms

colorbox.css

colorbox.css

372 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

1145 ms

jquery.queryloader2.js

jquery.queryloader2.js

697 ms

jquery.address-1.4.min.js

jquery.address-1.4.min.js

740 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

691 ms

sliding.js

sliding.js

868 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

1212 ms

conversion.js

conversion.js

14 ms

ga.js

ga.js

22 ms

mn1.png

mn1.png

176 ms

icon_new.png

icon_new.png

176 ms

mn2.png

mn2.png

179 ms

mn3.png

mn3.png

176 ms

mn4.png

mn4.png

200 ms

mn5.png

mn5.png

187 ms

mn6.png

mn6.png

354 ms

mn7.png

mn7.png

355 ms

mn8.png

mn8.png

354 ms

mn9.png

mn9.png

357 ms

mn10.png

mn10.png

371 ms

mn11.png

mn11.png

390 ms

mn12.png

mn12.png

528 ms

mn13.png

mn13.png

529 ms

mn14.png

mn14.png

528 ms

logo.png

logo.png

712 ms

neo.jpg

neo.jpg

567 ms

ova_02.jpg

ova_02.jpg

624 ms

title_world.png

title_world.png

705 ms

world_sub_01.png

world_sub_01.png

705 ms

world_sub_02.png

world_sub_02.png

705 ms

world_sub_03.png

world_sub_03.png

740 ms

world_sub_04.png

world_sub_04.png

796 ms

world_sub_05.png

world_sub_05.png

880 ms

world_sub_06.png

world_sub_06.png

879 ms

world_sub_07.png

world_sub_07.png

880 ms

world_sub_08.png

world_sub_08.png

888 ms

world_sub_09.png

world_sub_09.png

924 ms

world_sub_10.png

world_sub_10.png

986 ms

term.jpg

term.jpg

1401 ms

staff.jpg

staff.jpg

1227 ms

book.jpg

book.jpg

1400 ms

bluray.jpg

bluray.jpg

1242 ms

news.jpg

news.jpg

1477 ms

movie.jpg

movie.jpg

1177 ms

bl_track.js

bl_track.js

344 ms

87 ms

96 ms

story.jpg

story.jpg

1360 ms

widgets.js

widgets.js

121 ms

__utm.gif

__utm.gif

28 ms

53 ms

conversion.js

conversion.js

27 ms

conversion.js

conversion.js

37 ms

conversion.js

conversion.js

38 ms

__utm.gif

__utm.gif

4 ms

59 ms

__utm.gif

__utm.gif

19 ms

47 ms

38 ms

timeline.1b43d11859b7663a2225b885f87704a5.js

timeline.1b43d11859b7663a2225b885f87704a5.js

127 ms

14 ms

14 ms

cd.jpg

cd.jpg

1233 ms

onair.jpg

onair.jpg

1253 ms

radio.jpg

radio.jpg

1395 ms

index_02.jpg

index_02.jpg

1932 ms

17 ms

18 ms

world.jpg

world.jpg

1745 ms

character.jpg

character.jpg

1383 ms

syndication

syndication

90 ms

380716808266723329

380716808266723329

204 ms

staff_text.png

staff_text.png

1430 ms

bgr_right.png

bgr_right.png

1315 ms

new.png

new.png

1407 ms

index_ova.jpg

index_ova.jpg

1751 ms

wm_01.jpg

wm_01.jpg

1854 ms

wm_02.jpg

wm_02.jpg

1565 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

29 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

101 ms

wm_03.jpg

wm_03.jpg

1614 ms

wm_04.jpg

wm_04.jpg

1751 ms

wm_05.jpg

wm_05.jpg

1811 ms

fzySQZcJ_normal.jpg

fzySQZcJ_normal.jpg

147 ms

dCnZqzZX_normal.png

dCnZqzZX_normal.png

144 ms

133a3ffaf4ab18f618615d8fc81d8246_normal.jpeg

133a3ffaf4ab18f618615d8fc81d8246_normal.jpeg

143 ms

ES9vdF69_normal.png

ES9vdF69_normal.png

143 ms

L2w-aZmU_normal.png

L2w-aZmU_normal.png

144 ms

329pgKZX_normal.jpeg

329pgKZX_normal.jpeg

143 ms

wm_06.jpg

wm_06.jpg

1661 ms

wm_07.jpg

wm_07.jpg

1833 ms

wm_08.jpg

wm_08.jpg

1794 ms

comingsoon2.png

comingsoon2.png

1703 ms

jot

jot

27 ms

Accessibility Review

strike-the-blood.com accessibility score

93

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

Links do not have a discernible name

Best Practices

strike-the-blood.com best practices score

75

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

SEO Factors

strike-the-blood.com SEO score

75

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

strike-the-blood.com

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