Tools & Wizards About Us
mirai-no-mirai.jp screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

mirai-no-mirai.jp

「未来のミライ」公式サイト

Page Load Speed

3.5 sec in total

First Response

23 ms

Resources Loaded

3 sec

Page Rendered

502 ms

mirai-no-mirai.jp screenshot

About Website

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

細田守監督待望の最新作。「未来のミライ」2018年7月20日（金）公開！

Visit mirai-no-mirai.jp

Key Findings

We analyzed Mirai-no-mirai.jp page load time and found that the first response time was 23 ms and then it took 3.5 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

mirai-no-mirai.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value39.0 s

0/100

25%

SI (Speed Index)

Value28.0 s

0/100

10%

TBT (Total Blocking Time)

Value20,690 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value38.3 s

0/100

10%

Network Requests Diagram

mirai-no-mirai.jp

23 ms

common.css

46 ms

style.css

379 ms

colorbox.css

30 ms

slick.css

355 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 80% of them (82 requests) were addressed to the original Mirai-no-mirai.jp, 7% (7 requests) were made to Youtube.com and 3% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Mirai-no-mirai.jp.

Page Optimization Overview & Recommendations

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

Content Size

3.0 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mirai-no-mirai.jp main page is 3.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. Only a small number of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 30.8 kB

  • Original 36.7 kB
  • After minification 35.6 kB
  • After compression 6.0 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 30.8 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 157.8 kB

  • Original 2.6 MB
  • After minification 2.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. Mirai No images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 39.5 kB

  • Original 283.3 kB
  • After minification 282.8 kB
  • After compression 243.8 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 39.5 kB or 14% of the original size.

CSS Optimization

-3%

Potential reduce by 2.1 kB

  • Original 68.2 kB
  • After minification 68.2 kB
  • After compression 66.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. Mirai-no-mirai.jp has all CSS files already compressed.

Requests Breakdown

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

Requests Now

97

After Optimization

76

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mirai-no-mirai.jp

mirai-no-mirai.jp

23 ms

common.css

common.css

46 ms

style.css

style.css

379 ms

colorbox.css

colorbox.css

30 ms

slick.css

slick.css

355 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

8 ms

redirect.js

redirect.js

374 ms

jquery.colorbox.js

jquery.colorbox.js

29 ms

slick.min.js

slick.min.js

40 ms

jquery.cookie.js

jquery.cookie.js

347 ms

common.js

common.js

51 ms

menu.js

menu.js

52 ms

top.js

top.js

396 ms

news.js

news.js

55 ms

notosansjp.css

notosansjp.css

68 ms

css

css

84 ms

main.jpg

main.jpg

370 ms

logo-top.png

logo-top.png

388 ms

copy.png

copy.png

314 ms

chara.png

chara.png

368 ms

stadio-chizu.png

stadio-chizu.png

576 ms

bnr_190123-1.png

bnr_190123-1.png

340 ms

bnr_bddvd.png

bnr_bddvd.png

745 ms

bnr_line.png

bnr_line.png

813 ms

bnr_190305-1.png

bnr_190305-1.png

747 ms

bnr_190121-1.png

bnr_190121-1.png

744 ms

bnr_message.png

bnr_message.png

744 ms

topicsbnr_30.png

topicsbnr_30.png

575 ms

topicsbnr_29.jpg

topicsbnr_29.jpg

576 ms

topicsbnr_28.jpg

topicsbnr_28.jpg

923 ms

topicsbnr_27.jpg

topicsbnr_27.jpg

746 ms

topicsbnr_26.jpg

topicsbnr_26.jpg

1331 ms

topicsbnr_25.jpg

topicsbnr_25.jpg

1338 ms

topicsbnr_24.jpg

topicsbnr_24.jpg

1349 ms

topicsbnr_23.jpg

topicsbnr_23.jpg

748 ms

topicsbnr_22.png

topicsbnr_22.png

1357 ms

topicsbnr_21.png

topicsbnr_21.png

811 ms

topicsbnr_20.jpg

topicsbnr_20.jpg

812 ms

topicsbnr_17.png

topicsbnr_17.png

811 ms

topicsbnr_18.jpg

topicsbnr_18.jpg

917 ms

topicsbnr_19.png

topicsbnr_19.png

920 ms

topicsbnr_16.png

topicsbnr_16.png

1472 ms

topicsbnr_15.png

topicsbnr_15.png

1356 ms

topicsbnr_14.jpg

topicsbnr_14.jpg

1809 ms

topicsbnr_13.jpg

topicsbnr_13.jpg

1343 ms

topicsbnr_12.png

topicsbnr_12.png

1345 ms

topicsbnr_11.jpg

topicsbnr_11.jpg

1346 ms

topicsbnr_10.png

topicsbnr_10.png

1351 ms

topicsbnr_09.png

topicsbnr_09.png

1348 ms

topicsbnr_08.jpg

topicsbnr_08.jpg

1351 ms

topicsbnr_07.png

topicsbnr_07.png

1354 ms

topicsbnr_06.png

topicsbnr_06.png

1327 ms

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf

o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6Vc.ttf

155 ms

analytics.js

analytics.js

107 ms

U2QgBMj6NBI

U2QgBMj6NBI

9 ms

U2QgBMj6NBI

U2QgBMj6NBI

8 ms

U2QgBMj6NBI

U2QgBMj6NBI

98 ms

collect

collect

27 ms

collect

collect

37 ms

js

js

78 ms

www-player.css

www-player.css

11 ms

www-embed-player.js

www-embed-player.js

31 ms

base.js

base.js

79 ms

topicsbnr_05.jpg

topicsbnr_05.jpg

1052 ms

topicsbnr_04.jpg

topicsbnr_04.jpg

1022 ms

topicsbnr_03.jpg

topicsbnr_03.jpg

996 ms

topicsbnr_02.jpg

topicsbnr_02.jpg

980 ms

ad_status.js

ad_status.js

230 ms

nav_icon-theater.png

nav_icon-theater.png

1112 ms

sns_btn-twitter.png

sns_btn-twitter.png

1112 ms

sns_btn-fb.png

sns_btn-fb.png

1112 ms

zsuYbLQL7cfgkPw96EIg59zP1zcoLT-EKB-9U6ATFis.js

zsuYbLQL7cfgkPw96EIg59zP1zcoLT-EKB-9U6ATFis.js

161 ms

embed.js

embed.js

55 ms

sns_btn-insta.png

sns_btn-insta.png

1002 ms

news190116-1-main.jpg

news190116-1-main.jpg

735 ms

news-disc.jpg

news-disc.jpg

737 ms

news-media.jpg

news-media.jpg

738 ms

news180807-1-main.jpg

news180807-1-main.jpg

743 ms

news180803-1-main.jpg

news180803-1-main.jpg

745 ms

id

id

45 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

42 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

55 ms

news180706-3-main.jpg

news180706-3-main.jpg

743 ms

Create

Create

123 ms

news180802-1-main.jpg

news180802-1-main.jpg

687 ms

news180801-1-main.jpg

news180801-1-main.jpg

692 ms

billing.png

billing.png

1184 ms

footer_logo.png

footer_logo.png

1182 ms

qr_line.png

qr_line.png

1087 ms

share-title.png

share-title.png

1103 ms

share_btn-twitter.png

share_btn-twitter.png

801 ms

GenerateIT

GenerateIT

15 ms

share_btn-fb.png

share_btn-fb.png

750 ms

share_btn-line.png

share_btn-line.png

840 ms

share_btn-plus.png

share_btn-plus.png

983 ms

bnr_udcast01.png

bnr_udcast01.png

1001 ms

bnr_udcast02.png

bnr_udcast02.png

1021 ms

btn-prev.jpg

btn-prev.jpg

998 ms

btn-next.jpg

btn-next.jpg

1053 ms

controls.png

controls.png

829 ms

loading_background.png

loading_background.png

835 ms

loading.gif

loading.gif

838 ms

close.png

close.png

1165 ms

Accessibility Review

mirai-no-mirai.jp accessibility score

86

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

mirai-no-mirai.jp 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

High

Page has valid source maps

SEO Factors

mirai-no-mirai.jp SEO score

92

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

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

    JA

  • Encoding

    UTF-8

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

mirai-no-mirai.jp

Open Graph data is detected on the main page of Mirai No. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: