5.8 sec in total
327 ms
5.2 sec
245 ms
Visit fate-zero.jp now to see the best up-to-date Fate Zero content for Japan and also check out these interesting facts you probably never knew about fate-zero.jp
Fate/Zeroアニメ公式サイト。虚淵玄によるスピンアウト小説「Fate/Zero」が満を持してのアニメ化!!
Visit fate-zero.jpWe analyzed Fate-zero.jp page load time and found that the first response time was 327 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fate-zero.jp performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value8.3 s
2/100
25%
Value7.1 s
31/100
10%
Value170 ms
92/100
30%
Value0
100/100
15%
Value6.0 s
65/100
10%
327 ms
161 ms
308 ms
307 ms
311 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 85% of them (40 requests) were addressed to the original Fate-zero.jp, 11% (5 requests) were made to Google.com and 2% (1 request) were made to Aniplex.co.jp. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Google.com.
Page size can be reduced by 98.5 kB (13%)
747.4 kB
648.9 kB
In fact, the total size of Fate-zero.jp main page is 747.4 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. 25% of websites need less resources to load. Images take 612.6 kB which makes up the majority of the site volume.
Potential reduce by 11.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. This page needs HTML code to be minified as it can gain 1.8 kB, which is 12% 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 11.4 kB or 73% of the original size.
Potential reduce by 10.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. Fate Zero images are well optimized though.
Potential reduce by 66.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 66.0 kB or 63% of the original size.
Potential reduce by 11.1 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. Fate-zero.jp needs all CSS files to be minified and compressed as it can save up to 11.1 kB or 80% of the original size.
Number of requests can be reduced by 15 (33%)
46
31
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fate Zero. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
www.fate-zero.jp
327 ms
smartRollover.js
161 ms
swfobject.js
308 ms
style.css
307 ms
index.css
311 ms
jsapi
20 ms
jquery.js
742 ms
readnews.js
315 ms
s_code.js
447 ms
15 ms
default+en.css
3 ms
default+en.I.js
6 ms
noFla.jpg
1327 ms
top_logo.png
451 ms
btn-news.png
161 ms
btn-introduction.png
162 ms
btn-onair.png
161 ms
btn-talk.png
163 ms
btn-staffcast.png
321 ms
btn-characters.png
320 ms
btn-story.png
321 ms
spacer.gif
322 ms
btn-oped.png
480 ms
btn-movies.png
482 ms
btn-bdbox01.png
481 ms
btn-bdbox02.png
483 ms
btn-novels.png
610 ms
btn-comics.png
641 ms
btn-goods.png
639 ms
btn-rentdvd.png
641 ms
bnr-aj2016.gif
642 ms
exp.png
768 ms
btn-jpg_off.png
798 ms
btn-pdf_off.png
798 ms
top_titleNews.jpg
799 ms
news_bg.png
800 ms
footlink01_off.gif
928 ms
footlink02_off.gif
957 ms
footlink03_off.gif
959 ms
bnr_01_r.png
1103 ms
bnr_02_r.png
961 ms
bnr_03_r.png
1088 ms
bnr_04_r.png
1116 ms
bnr_06_r.png
1118 ms
logo_02_r.png
1118 ms
s73199086645618
80 ms
Gfeeds
2471 ms
fate-zero.jp accessibility score
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
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
Image elements do not have [alt] attributes
fate-zero.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
fate-zero.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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fate-zero.jp 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 Fate-zero.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.
fate-zero.jp
Open Graph description is not detected on the main page of Fate Zero. 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: