Analyze

futureme.org: FutureMe: Write a Letter to your Future Self

Write a letter to the future: set goals for yourself, make a prediction about the world. Envision the future, and then make it happen

Page load speed analysis

  • 63/100

    Normal result
  • 7

    Successful tests
  • 1

    Failed test
  • First response

    186 ms

  • Resources loaded

    2.2 sec

  • Page rendered

    631 ms

  • Total page load time

    3 sec

Welcome to futureme.org homepage info - get ready to check Future Me best content for United States right away, or after learning these important things about futureme.org

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

Page optimization

  • HTML 42.3 kB
    Images 62.3 kB
    Javascripts 272.6 kB
    CSS 47.5 kB

    In fact, the total size of Futureme.org main page is 424.7 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. 35% of websites need less resources to load. Javascripts take 272.6 kB which makes up the majority of the site volume.

    • Original 42.3 kB
    • After minification 41.5 kB
    • After compression 12.7 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 29.6 kB or 70% of the original size.

    • Original 62.3 kB
    • After optimization 47.2 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. Obviously, Future Me needs image optimization as it can save up to 15.1 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

    • Original 272.6 kB
    • After minification 272.6 kB
    • After compression 97.9 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 174.8 kB or 64% of the original size.

    • Original 47.5 kB
    • After minification 47.1 kB
    • After compression 9.8 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. Futureme.org needs all CSS files to be minified and compressed as it can save up to 37.7 kB or 79% of the original size.

Network requests diagram

  • www.futureme.org
  • font-awesome.min.css
  • show_ads.js
  • brand
  • application-7bf718ad7f83cd8877cdea28a32f41c7.css
  • application-410631b32a0cb1e21e266e5b55165659.js
  • DlsR62rj4TUCUB8R7dLxbg.js
  • mixpanel-2.2.min.js
  • analytics.js
  • badge_blue.png
  • futuremelogo-c72859e1dfbec0b9415378dff56aa593.png
  • ca-pub-8322407134806155.js
  • zrt_lookup.html
  • show_ads_impl.js
  • fmteachers-bg-small.jpg
  • like.php
  • track.js
  • collect
  • collect
  • ads
  • osd.js
  • zH0IPw-UmpL.js
  • LVx-xkvaJ0b.png
  • ga-audiences
  • nr-852.min.js

Our browser made a total of 26 requests to load all elements on the main page. We found that 15% of them (4 requests) were addressed to the original Futureme.org, 15% (4 requests) were made to Pagead2.googlesyndication.com and 8% (2 requests) were made to Cdn.mxpnl.com. The less responsive or slowest element that took the longest time to load (800 ms) relates to the external source Futureme.s3.amazonaws.com.

Additional info on futureme.org

Requests

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

11

Javascripts

6

Images

2

CSS

5

AJAX

24

All

Possible request optimization

1

Javascripts

6

Images

2

CSS

5

AJAX

10

Optimized

14

All

Good result

IP address

Futureme.org uses IP addresses which are currently shared with 18 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.

Good result

IP Trace

futureme.org

northpoint.org

glocap.com

mcsweeneys.net

insightnow.jp

3.90.94.177

futureme.org

lanueva.com.ar

mediapredict.com

metropolitanwarehouse.com

daddyhunt.com

3.217.50.123

futureme.org

everytimezone.com

wilsonelectronics.com

suicidegirls.com

micromentor.org

34.206.18.248

DNS records

Type Host Target/ip TTL Other
A

futureme.org

52.216.243.179 5
NS

futureme.org

ns-1043.awsdns-02.org 86400
NS

futureme.org

ns-1754.awsdns-27.co.uk 86400
NS

futureme.org

ns-304.awsdns-38.com 86400
NS

futureme.org

ns-911.awsdns-49.net 86400

HTTPS certificate

SSL Certificate

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

Poor result

Visitor World Map

Country of origin for 22.2% of all visits is United States. It’s good for Futureme.org that their server is also located in United States, as that enables the majority of their visitors to benefit from a much faster page load time.

Good result

Good result

Social Sharing Optimization

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

futureme.org

Language and encoding

Normal result

Language

EN en language flag

Detected

N/A  language flag

Claimed

Encoding

UTF-8

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Futureme.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Futureme.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.

Share this report in social media

Analyze another website

Analyze