Tools & Wizards About Us
miraikaigi.org screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

miraikaigi.org

未来会議 | 未来会議は、様々な人たちが地域もジャンルも世代も越えて出会い、感じていることを共有し、違いや問題からも気づきや学びを得る。そこから一人ひとりが一歩を踏み出し、疲れたら戻れる苗床のような場を目指しています。

Page Load Speed

4.2 sec in total

First Response

708 ms

Resources Loaded

3.3 sec

Page Rendered

238 ms

miraikaigi.org screenshot

About Website

Visit miraikaigi.org now to see the best up-to-date Miraikaigi content and also check out these interesting facts you probably never knew about miraikaigi.org

未来会議は、様々な人たちが地域もジャンルも世代も越えて出会い、感じていることを共有し、違いや問題からも気づきや学びを得る。そこから一人ひとりが一歩を踏み出し、疲れたら戻れる苗床のような場を目指しています。

Visit miraikaigi.org

Key Findings

We analyzed Miraikaigi.org page load time and found that the first response time was 708 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

miraikaigi.org performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

8/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value1,820 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.164

72/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

miraikaigi.org

708 ms

style.css

183 ms

normalize.css

358 ms

main.css

361 ms

flexnav.css

359 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 54% of them (43 requests) were addressed to the original Miraikaigi.org, 25% (20 requests) were made to Platform.twitter.com and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Miraikaigi.org.

Page Optimization Overview & Recommendations

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

Content Size

925.4 kB

After Optimization

847.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Miraikaigi.org main page is 925.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. 70% of websites need less resources to load. Images take 690.6 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 27.9 kB

  • Original 36.8 kB
  • After minification 32.8 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 4.0 kB, which is 11% 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 27.9 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 14.6 kB

  • Original 690.6 kB
  • After minification 676.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. Miraikaigi images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 15.1 kB

  • Original 134.8 kB
  • After minification 134.0 kB
  • After compression 119.6 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 15.1 kB or 11% of the original size.

CSS Optimization

-32%

Potential reduce by 20.2 kB

  • Original 63.2 kB
  • After minification 62.3 kB
  • After compression 43.0 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. Miraikaigi.org needs all CSS files to be minified and compressed as it can save up to 20.2 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (55%)

Requests Now

78

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

miraikaigi.org

miraikaigi.org

708 ms

style.css

style.css

183 ms

normalize.css

normalize.css

358 ms

main.css

main.css

361 ms

flexnav.css

flexnav.css

359 ms

font-awesome.min.css

font-awesome.min.css

12 ms

jquery.min.js

jquery.min.js

8 ms

script.js

script.js

359 ms

jquery.flexnav.js

jquery.flexnav.js

381 ms

jquery.wpcf7.confirm.js

jquery.wpcf7.confirm.js

381 ms

styles.css

styles.css

546 ms

font-awesome.min.css

font-awesome.min.css

547 ms

bootstrap.css

bootstrap.css

717 ms

front.css

front.css

552 ms

amazonjs.css

amazonjs.css

556 ms

jquery.js

jquery.js

739 ms

jquery-migrate.min.js

jquery-migrate.min.js

714 ms

bootstrap.min.js

bootstrap.min.js

736 ms

front.js

front.js

737 ms

chosen.jquery.min.js

chosen.jquery.min.js

736 ms

jquery.form.min.js

jquery.form.min.js

905 ms

scripts.js

scripts.js

905 ms

analytics.js

analytics.js

7 ms

collect

collect

40 ms

collect

collect

16 ms

js

js

65 ms

css

css

39 ms

bg_rainbow.png

bg_rainbow.png

185 ms

head_logo.png

head_logo.png

184 ms

gnavi01.png

gnavi01.png

188 ms

gnavi02.png

gnavi02.png

181 ms

gnavi03.png

gnavi03.png

306 ms

gnavi04.png

gnavi04.png

306 ms

gnavi06.png

gnavi06.png

366 ms

gnavi07.png

gnavi07.png

370 ms

gnavi08.png

gnavi08.png

371 ms

top_twitter_head.png

top_twitter_head.png

371 ms

top_fb_btn.png

top_fb_btn.png

516 ms

s_navi02.png

s_navi02.png

836 ms

s_navi03.png

s_navi03.png

893 ms

s_navi04.png

s_navi04.png

896 ms

s_navi06.png

s_navi06.png

898 ms

s_navi07.png

s_navi07.png

566 ms

page_top_btn.png

page_top_btn.png

693 ms

footer_logo.png

footer_logo.png

734 ms

widgets.js

widgets.js

9 ms

line_bg_top.png

line_bg_top.png

825 ms

t_newsview_btn.png

t_newsview_btn.png

872 ms

top_title_sbg.png

top_title_sbg.png

964 ms

s_navi01.png

s_navi01.png

1712 ms

icon01.png

icon01.png

1022 ms

like.php

like.php

171 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

51 ms

sdk.js

sdk.js

47 ms

settings

settings

126 ms

sdk.js

sdk.js

5 ms

51 ms

XjQ1X4X-N6a.js

XjQ1X4X-N6a.js

44 ms

FEppCFCt76d.png

FEppCFCt76d.png

42 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

4 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

12 ms

mirai_iwaki

mirai_iwaki

55 ms

embeds

embeds

122 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

20 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

6 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

5 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

45 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

44 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

96 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

102 ms

_buildManifest.js

_buildManifest.js

118 ms

_ssgManifest.js

_ssgManifest.js

117 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

16 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

17 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

6 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

10 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

10 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

30 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

29 ms

Accessibility Review

miraikaigi.org accessibility score

80

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

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

miraikaigi.org best practices score

67

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

Browser errors were logged to the console

SEO Factors

miraikaigi.org SEO score

98

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

High

Tap targets are not sized appropriately

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 Miraikaigi.org 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 Miraikaigi.org 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

miraikaigi.org

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