Tools & Wizards About Us
tomorrow.me screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

tomorrow.me

Everything you need to plan your estate | Ethos Life

Page Load Speed

1.5 sec in total

First Response

33 ms

Resources Loaded

912 ms

Page Rendered

571 ms

tomorrow.me screenshot

About Website

Visit tomorrow.me now to see the best up-to-date Tomorrow content for United States and also check out these interesting facts you probably never knew about tomorrow.me

These simple estate planning tools allow you to make a will, trust, power of attorney, and more. Built by attorneys, customized by you!

Visit tomorrow.me

Key Findings

We analyzed Tomorrow.me page load time and found that the first response time was 33 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

tomorrow.me performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value4,990 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value36.1 s

0/100

10%

Network Requests Diagram

tomorrow.me

33 ms

tomorrow.me

11 ms

48 ms

airgap.js

123 ms

polyfills-78c92fac7aa8fdd8.js

30 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Tomorrow.me, 84% (46 requests) were made to Ethoslife.com and 9% (5 requests) were made to Res.cloudinary.com. The less responsive or slowest element that took the longest time to load (273 ms) relates to the external source Res.cloudinary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 192.5 kB (34%)

Content Size

571.1 kB

After Optimization

378.7 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-81%

Potential reduce by 192.5 kB

  • Original 238.3 kB
  • After minification 238.2 kB
  • After compression 45.8 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 192.5 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 16 B

  • Original 279.3 kB
  • After minification 279.3 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. Tomorrow images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 53.6 kB
  • After minification 53.6 kB
  • After compression 53.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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 40 (77%)

Requests Now

52

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tomorrow.me

tomorrow.me

33 ms

tomorrow.me

tomorrow.me

11 ms

48 ms

airgap.js

airgap.js

123 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

30 ms

2007.f42b2b93894d184d.js

2007.f42b2b93894d184d.js

50 ms

5601.b8c1fd18cad76396.js

5601.b8c1fd18cad76396.js

51 ms

2328.19963fc9c902d556.js

2328.19963fc9c902d556.js

52 ms

3198.39fc5acf4a75c75f.js

3198.39fc5acf4a75c75f.js

61 ms

8234.dd5071d4946c7edf.js

8234.dd5071d4946c7edf.js

61 ms

9860.807c4f92992c3682.js

9860.807c4f92992c3682.js

61 ms

7963.7a6bf9eb197a623c.js

7963.7a6bf9eb197a623c.js

63 ms

5675.51330ae5c8be75d0.js

5675.51330ae5c8be75d0.js

63 ms

1135.e333e8e65349b00b.js

1135.e333e8e65349b00b.js

63 ms

587.853c72e1a628097c.js

587.853c72e1a628097c.js

71 ms

webpack-ad04fa37887c5afc.js

webpack-ad04fa37887c5afc.js

70 ms

framework-3ab5f7855fd38ca6.js

framework-3ab5f7855fd38ca6.js

70 ms

main-9a1f1e4c254b7035.js

main-9a1f1e4c254b7035.js

78 ms

_app-3f4b28e8f7acd6b9.js

_app-3f4b28e8f7acd6b9.js

98 ms

2852872c-304323d344ff1d1e.js

2852872c-304323d344ff1d1e.js

78 ms

190662ed-3adde8075b82e810.js

190662ed-3adde8075b82e810.js

92 ms

75fc9c18-0d33c00b4fa07b1d.js

75fc9c18-0d33c00b4fa07b1d.js

87 ms

9851-2499faf302fac09b.js

9851-2499faf302fac09b.js

120 ms

8453-cee654ab5bb85e8d.js

8453-cee654ab5bb85e8d.js

87 ms

7899-3e56978033a256c1.js

7899-3e56978033a256c1.js

96 ms

%5B%5B...slug%5D%5D-333ee8bb4979cb47.js

%5B%5B...slug%5D%5D-333ee8bb4979cb47.js

132 ms

_buildManifest.js

_buildManifest.js

119 ms

_ssgManifest.js

_ssgManifest.js

132 ms

parents_with_baby_desktop_fbd54h.png

parents_with_baby_desktop_fbd54h.png

127 ms

maxresdefault.jpg

maxresdefault.jpg

108 ms

parents_with_baby_mobile_ceioze.png

parents_with_baby_mobile_ceioze.png

122 ms

EP_landing_page_graphics_txvsul.svg

EP_landing_page_graphics_txvsul.svg

273 ms

6_czddd4.svg

6_czddd4.svg

180 ms

7_zufaoy.svg

7_zufaoy.svg

176 ms

facebook-icon-white.5d6386c9.svg

facebook-icon-white.5d6386c9.svg

105 ms

twitter-icon-white.ded49ea3.svg

twitter-icon-white.ded49ea3.svg

109 ms

instagram-icon-white.e6bccc03.svg

instagram-icon-white.e6bccc03.svg

107 ms

linkedin-icon-white.54662e5a.svg

linkedin-icon-white.54662e5a.svg

106 ms

9d7949d04d5fe561.css

9d7949d04d5fe561.css

14 ms

9d7949d04d5fe561.css

9d7949d04d5fe561.css

11 ms

1ec842aeb4f72ad4.css

1ec842aeb4f72ad4.css

9 ms

1ec842aeb4f72ad4.css

1ec842aeb4f72ad4.css

4 ms

08c720b78259d6d6.css

08c720b78259d6d6.css

5 ms

08c720b78259d6d6.css

08c720b78259d6d6.css

4 ms

7885f55c9d8f5b2c.css

7885f55c9d8f5b2c.css

5 ms

27c9d87050de7451.css

27c9d87050de7451.css

14 ms

64d591aa9095c426.css

64d591aa9095c426.css

5 ms

ee01cbc6356db975.css

ee01cbc6356db975.css

7 ms

31de9a23823d66f2.css

31de9a23823d66f2.css

6 ms

248fb006ea6aa690.css

248fb006ea6aa690.css

4 ms

ac9f857c28b7c7ae.css

ac9f857c28b7c7ae.css

4 ms

c45a7645ce8f5817.css

c45a7645ce8f5817.css

4 ms

19ecb6f17e45508a.css

19ecb6f17e45508a.css

5 ms

80d9f8152471d1ca.css

80d9f8152471d1ca.css

4 ms

7129621772a35928.css

7129621772a35928.css

4 ms

Accessibility Review

tomorrow.me accessibility score

84

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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

Best Practices

tomorrow.me best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

tomorrow.me SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

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 Tomorrow.me 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 Tomorrow.me 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

tomorrow.me

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