Tools & Wizards About Us
days-project.jp screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

days-project.jp

TVアニメ「DAYS」公式サイト

Page Load Speed

3.2 sec in total

First Response

74 ms

Resources Loaded

2.9 sec

Page Rendered

160 ms

days-project.jp screenshot

About Website

Welcome to days-project.jp homepage info - get ready to check DAYS Project best content for Japan right away, or after learning these important things about days-project.jp

著者安田剛士。2013年から週刊少年マガジンに連載中の本格派高校サッカー漫画「DAYS」。東院学園戦OAD付限定版コミックス３巻連続発売！

Visit days-project.jp

Key Findings

We analyzed Days-project.jp page load time and found that the first response time was 74 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

days-project.jp performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

65/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value19.6 s

0/100

10%

TBT (Total Blocking Time)

Value10,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value22.6 s

1/100

10%

Network Requests Diagram

days-project.jp

74 ms

days-project.jp

464 ms

jquery.min.js

24 ms

set.js

451 ms

index.js

450 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 52% of them (31 requests) were addressed to the original Days-project.jp, 18% (11 requests) were made to Platform.twitter.com and 8% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Days-project.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.9 kB (5%)

Content Size

588.3 kB

After Optimization

559.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Days-project.jp main page is 588.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 294.2 kB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 4.6 kB

  • Original 7.8 kB
  • After minification 7.6 kB
  • After compression 3.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 4.6 kB or 59% of the original size.

Image Optimization

-7%

Potential reduce by 20.0 kB

  • Original 294.2 kB
  • After minification 274.2 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. DAYS Project images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 3.9 kB

  • Original 223.6 kB
  • After minification 223.2 kB
  • After compression 219.7 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

-1%

Potential reduce by 462 B

  • Original 62.6 kB
  • After minification 62.6 kB
  • After compression 62.2 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. Days-project.jp has all CSS files already compressed.

Requests Breakdown

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

Requests Now

56

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

days-project.jp

days-project.jp

74 ms

days-project.jp

days-project.jp

464 ms

jquery.min.js

jquery.min.js

24 ms

set.js

set.js

451 ms

index.js

index.js

450 ms

style.css

style.css

167 ms

pc.css

pc.css

451 ms

pc.css

pc.css

154 ms

loading.gif

loading.gif

199 ms

nav_line.png

nav_line.png

156 ms

title.png

title.png

552 ms

he_btn_171017.png

he_btn_171017.png

553 ms

news

news

830 ms

back.jpg

back.jpg

574 ms

mainimage_171017.jpg

mainimage_171017.jpg

824 ms

news_news_title.png

news_news_title.png

824 ms

news_tw_title.png

news_tw_title.png

573 ms

widgets.js

widgets.js

43 ms

Yr5OdoqLsaM

Yr5OdoqLsaM

143 ms

nav_top_on.png

nav_top_on.png

551 ms

nav_1007.png

nav_1007.png

702 ms

nav_news_on.png

nav_news_on.png

703 ms

nav_onair_on.png

nav_onair_on.png

702 ms

nav_intro_on.png

nav_intro_on.png

831 ms

nav_story_on.png

nav_story_on.png

831 ms

nav_staffcast_on.png

nav_staffcast_on.png

862 ms

nav_chara_on.png

nav_chara_on.png

874 ms

nav_bddvd_on.png

nav_bddvd_on.png

895 ms

nav_cd_on.png

nav_cd_on.png

920 ms

nav_movie_on.png

nav_movie_on.png

989 ms

nav_eve_on.png

nav_eve_on.png

990 ms

loading2.gif

loading2.gif

1012 ms

foo_ball.png

foo_ball.png

1025 ms

totop.png

totop.png

1033 ms

analytics.js

analytics.js

44 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

33 ms

collect

collect

32 ms

settings

settings

123 ms

js

js

116 ms

www-player.css

www-player.css

10 ms

www-embed-player.js

www-embed-player.js

35 ms

base.js

base.js

80 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

309 ms

ad_status.js

ad_status.js

203 ms

XRk6eFbYaDme_I9SSIFgFZ9I1nSvAmlSIHv6h58Lfu0.js

XRk6eFbYaDme_I9SSIFgFZ9I1nSvAmlSIHv6h58Lfu0.js

137 ms

embed.js

embed.js

44 ms

id

id

33 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

144 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

145 ms

days_anime

days_anime

762 ms

Create

Create

108 ms

GenerateIT

GenerateIT

14 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

10 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

21 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

47 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

47 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

79 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

81 ms

_buildManifest.js

_buildManifest.js

77 ms

_ssgManifest.js

_ssgManifest.js

100 ms

Accessibility Review

days-project.jp accessibility score

68

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

days-project.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

days-project.jp SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

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

days-project.jp

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