3 sec in total
186 ms
2.2 sec
631 ms
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.orgWe 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.
futureme.org performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value10.3 s
0/100
25%
Value16.3 s
0/100
10%
Value4,500 ms
0/100
30%
Value0.131
81/100
15%
Value33.6 s
0/100
10%
186 ms
163 ms
158 ms
215 ms
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 size can be reduced by 155.4 kB (50%)
311.6 kB
156.1 kB
In fact, the total size of Futureme.org main page is 311.6 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 159.5 kB which makes up the majority of the site volume.
Potential reduce by 29.6 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.
Potential reduce by 15.1 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.
Potential reduce by 73.0 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 73.0 kB or 46% of the original size.
Potential reduce by 37.7 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.
Number of requests can be reduced by 10 (42%)
24
14
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.
www.futureme.org
186 ms
font-awesome.min.css
163 ms
show_ads.js
158 ms
brand
215 ms
application-7bf718ad7f83cd8877cdea28a32f41c7.css
17 ms
application-410631b32a0cb1e21e266e5b55165659.js
50 ms
DlsR62rj4TUCUB8R7dLxbg.js
215 ms
mixpanel-2.2.min.js
453 ms
analytics.js
343 ms
badge_blue.png
387 ms
futuremelogo-c72859e1dfbec0b9415378dff56aa593.png
113 ms
ca-pub-8322407134806155.js
64 ms
zrt_lookup.html
696 ms
show_ads_impl.js
378 ms
fmteachers-bg-small.jpg
800 ms
like.php
757 ms
track.js
682 ms
collect
389 ms
collect
591 ms
483 ms
ads
232 ms
osd.js
77 ms
zH0IPw-UmpL.js
490 ms
LVx-xkvaJ0b.png
545 ms
ga-audiences
35 ms
nr-852.min.js
77 ms
futureme.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
futureme.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
futureme.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
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.
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: