Access tomorrow.city. Tomorrow.City – The biggest platform about urban innovation

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value21.9 s

0/100

25%

SI (Speed Index)

Value5.7 s

51/100

10%

TBT (Total Blocking Time)

Value1,130 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

tomorrow.city

144 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Tomorrow.city and no external sources were called. The less responsive or slowest element that took the longest time to load (144 ms) belongs to the original domain Tomorrow.city.

Content Size

743.6 kB

After Optimization

388.7 kB

In fact, the total size of Tomorrow.city main page is 743.6 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number 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 426 B

Original 507 B
After minification 109 B
After compression 81 B

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. This page needs HTML code to be minified as it can gain 398 B, which is 79% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 426 B 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

-61%

Potential reduce by 106.0 kB

Original 173.7 kB
After minification 173.6 kB
After compression 67.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 106.0 kB or 61% 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 Now

After Optimization

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Image elements do not have [alt] attributes

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

N/A

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 neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Tomorrow.city main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

tomorrow.city

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