Analyze 株式会社フューチャースコープ

携帯電話が、従来の既成概念を大きく超える進化を遂げる中で、「もっと便利に」、「もっと楽しく」を追求する会社として、私たちフューチャースコープは未来 を追い続けます。

Page load speed analysis

  • 49/100

    Normal result
  • 6

    Successful tests
  • 2

    Failed tests
  • First response

    404 ms

  • Resources loaded

    7 sec

  • Page rendered

    200 ms

  • Total page load time

    7.6 sec

Click here to check amazing Futurescope content. Otherwise, check out these important facts you probably never knew about

We analyzed page load time and found that the first response time was 404 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Page optimization

  • HTML 30.0 kB
    Images 604.1 kB
    Javascripts 396.5 kB
    CSS 91.5 kB

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

    • Original 30.0 kB
    • After minification 27.4 kB
    • After compression 6.4 kB

    HTML optimization

    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 23.7 kB or 79% of the original size.

    • Original 604.1 kB
    • After optimization 576.7 kB

    Image optimization

    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. Futurescope images are well optimized though.

    • Original 396.5 kB
    • After minification 351.3 kB
    • After compression 119.4 kB

    JavaScript optimization

    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 277.1 kB or 70% of the original size.

    • Original 91.5 kB
    • After minification 66.4 kB
    • After compression 16.1 kB

    CSS optimization

    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. needs all CSS files to be minified and compressed as it can save up to 75.4 kB or 82% of the original size.

Network requests diagram

  • import.css
  • backoffice.css
  • company.css
  • mobile.css
  • team.css
  • group.css
  • newmeasure.css
  • jquery.galleryview-3.0.css
  • ob_contents.css
  • styles.css
  • meteor-slides.css
  • jquery.js
  • jquery-migrate.min.js
  • jquery.cycle.all.js
  • jquery.metadata.v2.js
  • jquery.touchwipe.1.1.1.js
  • slideshow.js
  • wpsf-js.php
  • jquery-1.7.2.min.js
  • jquery.vgrid.0.1.7.js
  • jquery.lightpop-
  • smartRollover.js
  • jquery.easing.1.3.js
  • jquery.galleryview-3.0.min.js
  • jquery.timers-1.2.js
  • jquery.form.js
  • scripts.js
  • delete.css
  • style.css
  • thumblist.css
  • elements.css
  • wp-emoji-release.min.js
  • ga.js
  • btn_pagetop.png
  • description.gif
  • logo.gif
  • 01_bg.png
  • close_o.png
  • 02_off.png
  • 04_off.png
  • 05_off.png
  • 06_off.png
  • 08_01_bg.png
  • 8_topics_off.png
  • 8_press_off.png
  • 8_home_off.png
  • 8_privacy_off.png
  • 8_inquiry_off.png
  • btn_more_off.gif
  • tail_160.png
  • frame_02_a.png
  • 10.gif
  • tail_data1.jpg
  • tail_map.jpg
  • tail_160.png
  • frame_04_a.png
  • tail.png
  • frame_05_a.png
  • tail.png
  • tail.png
  • %E3%82%BF%E3%82%A4%E3%83%AB-2.png
  • frame_05_b.png
  • 17.jpg
  • tail.png
  • frame_06_a.png
  • tail.png
  • tail1.png
  • tail_1601.png
  • __utm.gif
  • tail_1601.png
  • b59363343336128d53c695dc673e25c2.png
  • logo_f.gif
  • bg_topics.png
  • bg_press.png
  • bg_02_a.png
  • bg_04_a.png
  • bg_05_a.png
  • bg_05_b.png
  • bg_06_a.png
  • lightpop-btn-prev.gif
  • lightpop-btn-next.gif

Our browser made a total of 83 requests to load all elements on the main page. We found that 98% of them (81 requests) were addressed to the original, 2% (2 requests) were made to The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain

Additional info on


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









Possible request optimization











Normal result


As for redirects, our browser was forwarded to before it reached this domain.

IP address uses IP addresses which are currently shared with 14 other domains. The more sites share the same stack of IP addresses, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Normal result

IP Trace

DNS records

Type Host Target/ip TTL Other
A 300
NS 300
NS 300
NS 300
NS 300

HTTPS certificate

SSL Certificate has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

The server of is located in United States, but, unfortunately, we cannot identify the countries where the visitors come from and thus it’s impossible to define if the distance can potentially affect the page load time.

Good result

Poor result

Social Sharing Optimization

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

Language and encoding

Good result


JA ja language flag


JA ja language flag





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

Share this report in social media

Analyze another website