11.6 sec in total
2.9 sec
8.1 sec
592 ms
Click here to check amazing Future Cities Shell content for India. Otherwise, check out these important facts you probably never knew about futurecities.shell.com
Which kind of city matches your personality and how what will it look like in the future?
Visit futurecities.shell.comWe analyzed Futurecities.shell.com page load time and found that the first response time was 2.9 sec and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
futurecities.shell.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value5.3 s
22/100
25%
Value7.3 s
29/100
10%
Value520 ms
56/100
30%
Value0.401
25/100
15%
Value6.9 s
54/100
10%
2883 ms
537 ms
500 ms
536 ms
262 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 77% of them (27 requests) were addressed to the original Futurecities.shell.com, 9% (3 requests) were made to Assets.adobedtm.com and 9% (3 requests) were made to Consent.truste.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Futurecities.shell.com.
Page size can be reduced by 984.5 kB (25%)
4.0 MB
3.0 MB
In fact, the total size of Futurecities.shell.com main page is 4.0 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. 55% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 66.3 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 66.3 kB or 88% of the original size.
Potential reduce by 49.2 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. Future Cities Shell images are well optimized though.
Potential reduce by 577.3 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 577.3 kB or 73% of the original size.
Potential reduce by 291.6 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. Futurecities.shell.com needs all CSS files to be minified and compressed as it can save up to 291.6 kB or 80% of the original size.
Number of requests can be reduced by 10 (30%)
33
23
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Future Cities Shell. 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.
futurecities.shell.com
2883 ms
theme-shell.min.a77bc2ac977f635d7afa3a8b63f368c8.css
537 ms
embed-sync.min.360033b563615e6182ccb4cfa05300ee.js
500 ms
embed-async.min.c6c0bd7c6d439d56717b63f75011959b.js
536 ms
satelliteLib-80b242f2c1889ef74db5d8111ab36630e29c0cdf.js
262 ms
slick.min.66ec32e29d5764d31f55e7774c6e6e73.css
703 ms
publish.min.1be9c67cf24d61380addcf81ec4d62c9.js
144 ms
publish.min.f8802307cb79a70145b4a70e64e7636e.js
346 ms
notice
176 ms
shell-datalayer-async.min.0365c191f622b49d5cc795ada0257e6b.js
417 ms
shell-datalayer.min.fea6f79d0ee19f75ecad9cf823528e7c.js
700 ms
image-new-futurecities-moved.jpeg
305 ms
a-lady-besides-busy-road.jpeg
286 ms
six-city-archetypes.jpeg
327 ms
building-blocks.jpeg
490 ms
picture-of-man-infront-of-city.jpeg
277 ms
marikina-city-philippines.jpeg
507 ms
amsterdam-and-rotterdam-city.jpeg
714 ms
beijing-city-skyline-city-pollution.jpeg
551 ms
mix-city-pic.jpeg
775 ms
EECgRDhGaEs4TDhNCE4YT1BP0FOwVohYmFmIXNheQF+oYbBjkGUYZlhqUG24cgB0AHUwdcB2SHggeOB6EHtYfIh9MH2Afdh+uH8QgBiDOIPYhMiGYAAEAAABVAP0ADQAAAAAAAgAAAAAAAAAAAAAAAAAAAAAAAAAOAK4AAQAAAAAAAQAHAAAAAQAAAAAAAgAHAGAAAQAAAAAAAwAHADYAAQAAAAAABAAHAHUAAQAAAAAABQALABUAAQAAAAAABgAHAEsAAQAAAAAACgAaAIoAAwABBAkAAQAOAAcAAwABBAkAAgAOAGcAAwABBAkAAwAOAD0AAwABBAkABAAOAHwAAwABBAkABQAWACAAAwABBAkABgAOAFIAAwABBAkACgA0AKRpY29tb29uAGkAYwBvAG0AbwBvAG5WZXJzaW9uIDEuMABWAGUAcgBzAGkAbwBuACAAMQAuADBpY29tb29uAGkAYwBvAG0AbwBvAG5pY29tb29uAGkAYwBvAG0AbwBvAG5SZWd1bGFyAFIAZQBnAHUAbABhAHJpY29tb29uAGkAYwBvAG0AbwBvAG5Gb250IGdlbmVyYXRlZCBieSBJY29Nb29uLgBGAG8AbgB0ACAAZwBlAG4AZQByAGEAdABlAGQAIABiAHkAIABJAGMAbwBNAG8AbwBuAC4AAAADAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
2 ms
get
155 ms
satellite-5628fd7864746d6a960000e6.js
103 ms
s-code-contents-5b5c636ebd4ae0cd35954fddc6cc26157584033a.js
332 ms
image-new-futurecities-moved.jpeg
720 ms
a-lady-besides-busy-road.jpeg
694 ms
six-city-archetypes.jpeg
1039 ms
building-blocks.jpeg
1302 ms
picture-of-man-infront-of-city.jpeg
922 ms
marikina-city-philippines.jpeg
2126 ms
amsterdam-and-rotterdam-city.jpeg
2009 ms
beijing-city-skyline-city-pollution.jpeg
1163 ms
mix-city-pic.jpeg
2272 ms
get
83 ms
s08039801060222
8 ms
futurecities.shell.com accessibility score
futurecities.shell.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
futurecities.shell.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Futurecities.shell.com 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 Futurecities.shell.com 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.
futurecities.shell.com
Open Graph data is detected on the main page of Future Cities Shell. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: