Tools & Wizards About Us
tomorrow.city screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    35% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

tomorrow.city

Tomorrow.City – The biggest platform about urban innovation

Page Load Speed

10.3 sec in total

First Response

407 ms

Resources Loaded

3.7 sec

Page Rendered

6.2 sec

tomorrow.city screenshot

About Website

Visit tomorrow.city 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.city

A platform of platforms to accelerate sustainable, inclusive cities, enable collaboration, and identify solutions to critical urban issues.

Visit tomorrow.city

Key Findings

We analyzed Tomorrow.city page load time and found that the first response time was 407 ms and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

tomorrow.city performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value16.4 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value16,010 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value25.2 s

0/100

10%

Network Requests Diagram

tomorrow.city

407 ms

uc.js

50 ms

settings

102 ms

events

99 ms

fonts.css

206 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 8% of them (5 requests) were addressed to the original Tomorrow.city, 14% (9 requests) were made to Storage.googleapis.com and 12% (8 requests) were made to . The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Cdn.net.elogia.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 416.0 kB (50%)

Content Size

825.6 kB

After Optimization

409.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tomorrow.city main page is 825.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. 55% of websites need less resources to load. CSS take 498.1 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 159.2 kB

  • Original 189.9 kB
  • After minification 189.8 kB
  • After compression 30.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 159.2 kB or 84% of the original size.

Image Optimization

-64%

Potential reduce by 45.5 kB

  • Original 71.3 kB
  • After minification 25.8 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, Tomorrow needs image optimization as it can save up to 45.5 kB or 64% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 8.4 kB

  • Original 66.3 kB
  • After minification 66.3 kB
  • After compression 57.9 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 8.4 kB or 13% of the original size.

CSS Optimization

-41%

Potential reduce by 202.8 kB

  • Original 498.1 kB
  • After minification 498.1 kB
  • After compression 295.2 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. Tomorrow.city needs all CSS files to be minified and compressed as it can save up to 202.8 kB or 41% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (60%)

Requests Now

52

After Optimization

21

  • AJAX
  • 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 24 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

tomorrow.city

tomorrow.city

407 ms

uc.js

uc.js

50 ms

settings

settings

102 ms

events

events

99 ms

fonts.css

fonts.css

206 ms

jwplayer-8.20.1.min.js

jwplayer-8.20.1.min.js

369 ms

cc.js

cc.js

193 ms

gtm.js

gtm.js

68 ms

hotjar-2991208.js

hotjar-2991208.js

106 ms

analytics.js

analytics.js

84 ms

bat.js

bat.js

153 ms

conversion_async.js

conversion_async.js

152 ms

modules.bcd9ade6b0bb9bdd0789.js

modules.bcd9ade6b0bb9bdd0789.js

99 ms

8DC225367677D2A02.css

8DC225367677D2A02.css

808 ms

build.js

build.js

310 ms

collect

collect

50 ms

collect

collect

74 ms

72 ms

118 ms

22021155.js

22021155.js

62 ms

22021155

22021155

61 ms

45 ms

18 ms

clarity.js

clarity.js

24 ms

Wordmark_TomorrowCity_black_small.png

Wordmark_TomorrowCity_black_small.png

117 ms

read2022.svg

read2022.svg

282 ms

fira-bcn_logo2.png

fira-bcn_logo2.png

271 ms

tomorrow.svg

tomorrow.svg

269 ms

logos.png

logos.png

279 ms

lock2022.svg

lock2022.svg

286 ms

play2022.svg

play2022.svg

502 ms

logo-200.png

logo-200.png

504 ms

linkedin_logo.svg

linkedin_logo.svg

480 ms

twitter_logo.svg

twitter_logo.svg

475 ms

facebook_logo.svg

facebook_logo.svg

826 ms

bc-v4.min.html

bc-v4.min.html

238 ms

build.css

build.css

367 ms

mtc.js

mtc.js

752 ms

fbevents.js

fbevents.js

372 ms

obtp.js

obtp.js

643 ms

onpage.js

onpage.js

1280 ms

insight.min.js

insight.min.js

751 ms

uwt.js

uwt.js

640 ms

mtc.js

mtc.js

997 ms

activityi;src=5079218;type=invmedia;cat=zl1n0aq6;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=$%7BGDPR%7D;gdpr_consent=$%7BGDPR_CONSENT_755%7D;ord=9383851871825.754

activityi;src=5079218;type=invmedia;cat=zl1n0aq6;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=$%7BGDPR%7D;gdpr_consent=$%7BGDPR_CONSENT_755%7D;ord=9383851871825.754

1131 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

1092 ms

icon-loading.png

icon-loading.png

707 ms

152252505371063

152252505371063

642 ms

MKGI0=

MKGI0=

68 ms

MKGI0=

MKGI0=

67 ms

HpAawDtjwP9fo78woYjQ==

HpAawDtjwP9fo78woYjQ==

74 ms

HpAawDtjwP9fo78woYjQ==

HpAawDtjwP9fo78woYjQ==

65 ms

MKGI0=

MKGI0=

64 ms

HpAawDtjwP9fo78woYjQ==

HpAawDtjwP9fo78woYjQ==

64 ms

MKGI0=

MKGI0=

63 ms

MKGI0=

MKGI0=

63 ms

unifiedPixel

unifiedPixel

408 ms

cachedClickId

cachedClickId

411 ms

src=5079218;type=invmedia;cat=zl1n0aq6;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=$%7BGDPR%7D;gdpr_consent=$%7BGDPR_CONSENT_755%7D;ord=9383851871825.754

src=5079218;type=invmedia;cat=zl1n0aq6;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;npa=;gdpr=$%7BGDPR%7D;gdpr_consent=$%7BGDPR_CONSENT_755%7D;ord=9383851871825.754

321 ms

1834375866730403

1834375866730403

112 ms

visit-data

visit-data

500 ms

adsct

adsct

233 ms

adsct

adsct

231 ms

32 ms

c.gif

c.gif

17 ms

Accessibility Review

tomorrow.city accessibility score

61

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.

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

tomorrow.city 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

SEO Factors

tomorrow.city SEO score

85

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

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

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: