Tools & Wizards About Us
fortomorrow.org screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

fortomorrow.org

for Tomorrow | A long-term, multifaceted commitment to building a more sustainable world

Page Load Speed

4.7 sec in total

First Response

1.6 sec

Resources Loaded

2.2 sec

Page Rendered

950 ms

fortomorrow.org screenshot

About Website

Visit fortomorrow.org now to see the best up-to-date For Tomorrow content and also check out these interesting facts you probably never knew about fortomorrow.org

Sharing smart solutions for a sustainable future. For Tomorrow is powered by Hyundai Motor Company and the United Nations Development Programme.

Visit fortomorrow.org

Key Findings

We analyzed Fortomorrow.org page load time and found that the first response time was 1.6 sec and then it took 3.2 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

fortomorrow.org performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

19/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value1,100 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.7 s

17/100

10%

Network Requests Diagram

fortomorrow.org

1552 ms

gtm.js

65 ms

app.9cfd5b1.css

165 ms

index.801c59f.css

35 ms

index.72ae59e.css

39 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 57% of them (20 requests) were addressed to the original Fortomorrow.org, 29% (10 requests) were made to Cdn.fortomorrow.org and 9% (3 requests) were made to Fortomorrowprod.blob.core.windows.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Fortomorrow.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 118.5 kB (5%)

Content Size

2.6 MB

After Optimization

2.5 MB

  • HTML
  • Images

In fact, the total size of Fortomorrow.org main page is 2.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 69.7 kB

  • Original 87.2 kB
  • After minification 85.7 kB
  • After compression 17.5 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 69.7 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 48.7 kB

  • Original 2.5 MB
  • After minification 2.5 MB

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

Requests Breakdown

Number of requests can be reduced by 14 (47%)

Requests Now

30

After Optimization

16

  • Images
  • JavaScript
  • CSS

The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of For 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 11 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fortomorrow.org

fortomorrow.org

1552 ms

gtm.js

gtm.js

65 ms

app.9cfd5b1.css

app.9cfd5b1.css

165 ms

index.801c59f.css

index.801c59f.css

35 ms

index.72ae59e.css

index.72ae59e.css

39 ms

2a6bece1.4428792.css

2a6bece1.4428792.css

272 ms

index.dd75fce.css

index.dd75fce.css

183 ms

documentary_2_8230c753e0.jpg

documentary_2_8230c753e0.jpg

229 ms

small_Sudan_v4_dd8213ae3c.jpeg

small_Sudan_v4_dd8213ae3c.jpeg

46 ms

72a1af5.js

72a1af5.js

147 ms

ea4ef89.js

ea4ef89.js

37 ms

c21dd69.js

c21dd69.js

46 ms

6f8af2f.js

6f8af2f.js

54 ms

ab5afc2.js

ab5afc2.js

90 ms

8e2ac8d.js

8e2ac8d.js

89 ms

42a74f8.js

42a74f8.js

90 ms

4b95957.js

4b95957.js

113 ms

d42a5c3.js

d42a5c3.js

339 ms

small_village_e536a2c5d3.jpeg

small_village_e536a2c5d3.jpeg

47 ms

small_hands_b444c7869a.jpeg

small_hands_b444c7869a.jpeg

39 ms

mobility_88ec778e8f.jpg

mobility_88ec778e8f.jpg

344 ms

dialogue_de6d25d5cf.jpg

dialogue_de6d25d5cf.jpg

344 ms

Hero_Taking_Steps_Final_b314bde846.png

Hero_Taking_Steps_Final_b314bde846.png

497 ms

430x300_0c20eae3c5.jpeg

430x300_0c20eae3c5.jpeg

359 ms

430x300_95fae95449.jpeg

430x300_95fae95449.jpeg

348 ms

430x300_63b1b7d0cf.png

430x300_63b1b7d0cf.png

346 ms

430x300_c0e2b7d3db.jpeg

430x300_c0e2b7d3db.jpeg

365 ms

430x300_24e615faca

430x300_24e615faca

398 ms

430x300_0e2042d10a

430x300_0e2042d10a

435 ms

js

js

70 ms

180078b22d6ca55ddf9bfe24bcec99c1.svg

180078b22d6ca55ddf9bfe24bcec99c1.svg

102 ms

HyundaiSansText-Regular.d3d34d2.woff

HyundaiSansText-Regular.d3d34d2.woff

232 ms

HyundaiSansText-Medium.c88f04d.woff

HyundaiSansText-Medium.c88f04d.woff

259 ms

HyundaiSansHead-Regular.f40eb97.ttf

HyundaiSansHead-Regular.f40eb97.ttf

191 ms

HyundaiSansHead-Medium.3982b84.ttf

HyundaiSansHead-Medium.3982b84.ttf

239 ms

Accessibility Review

fortomorrow.org accessibility score

91

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

fortomorrow.org best practices score

92

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

Missing source maps for large first-party JavaScript

SEO Factors

fortomorrow.org SEO score

89

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

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

    EN

  • Encoding

    UTF-8

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

fortomorrow.org

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