Tools & Wizards About Us
futureme.org screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

futureme.org

FutureMe: Write a Letter to your Future Self

Page Load Speed

3 sec in total

First Response

186 ms

Resources Loaded

2.2 sec

Page Rendered

631 ms

futureme.org screenshot

About Website

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

Write a letter to the future: set goals for yourself, make a prediction about the world. Envision the future, and then make it happen. FutureMe has been delivering letters to the future for millions o...

Visit futureme.org

Key Findings

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 55% of websites can load faster.

Performance Metrics

futureme.org performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value16.3 s

0/100

10%

TBT (Total Blocking Time)

Value4,500 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.131

81/100

15%

TTI (Time to Interactive)

Value33.6 s

0/100

10%

Network Requests Diagram

www.futureme.org

186 ms

font-awesome.min.css

163 ms

show_ads.js

158 ms

brand

215 ms

application-7bf718ad7f83cd8877cdea28a32f41c7.css

17 ms

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.

Page Optimization Overview & Recommendations

Page size can be reduced by 187.4 kB (55%)

Content Size

343.5 kB

After Optimization

156.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Futureme.org main page is 343.5 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 191.4 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 29.6 kB

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

Image Optimization

-24%

Potential reduce by 15.1 kB

  • Original 62.3 kB
  • After minification 47.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. 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.

JavaScript Optimization

-55%

Potential reduce by 104.9 kB

  • Original 191.4 kB
  • After minification 191.4 kB
  • After compression 86.5 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 104.9 kB or 55% of the original size.

CSS Optimization

-79%

Potential reduce by 37.7 kB

  • Original 47.5 kB
  • After minification 47.1 kB
  • After compression 9.8 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. 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.

Requests Breakdown

Number of requests can be reduced by 10 (42%)

Requests Now

24

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

www.futureme.org

www.futureme.org

186 ms

font-awesome.min.css

font-awesome.min.css

163 ms

show_ads.js

show_ads.js

158 ms

brand

brand

215 ms

application-7bf718ad7f83cd8877cdea28a32f41c7.css

application-7bf718ad7f83cd8877cdea28a32f41c7.css

17 ms

application-410631b32a0cb1e21e266e5b55165659.js

application-410631b32a0cb1e21e266e5b55165659.js

50 ms

DlsR62rj4TUCUB8R7dLxbg.js

DlsR62rj4TUCUB8R7dLxbg.js

215 ms

mixpanel-2.2.min.js

mixpanel-2.2.min.js

453 ms

analytics.js

analytics.js

343 ms

badge_blue.png

badge_blue.png

387 ms

futuremelogo-c72859e1dfbec0b9415378dff56aa593.png

futuremelogo-c72859e1dfbec0b9415378dff56aa593.png

113 ms

ca-pub-8322407134806155.js

ca-pub-8322407134806155.js

64 ms

zrt_lookup.html

zrt_lookup.html

696 ms

show_ads_impl.js

show_ads_impl.js

378 ms

fmteachers-bg-small.jpg

fmteachers-bg-small.jpg

800 ms

like.php

like.php

757 ms

track.js

track.js

682 ms

collect

collect

389 ms

collect

collect

591 ms

483 ms

ads

ads

232 ms

osd.js

osd.js

77 ms

zH0IPw-UmpL.js

zH0IPw-UmpL.js

490 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

545 ms

ga-audiences

ga-audiences

35 ms

nr-852.min.js

nr-852.min.js

77 ms

Accessibility Review

futureme.org accessibility score

76

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

futureme.org SEO score

82

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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.

Social Sharing Optimization

futureme.org

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: