13.9 sec in total
103 ms
11.4 sec
2.4 sec
Welcome to imaginingthecity.com homepage info - get ready to check Imagining The City best content right away, or after learning these important things about imaginingthecity.com
Imagining the City is the photography of C. Alex de Freitas
Visit imaginingthecity.comWe analyzed Imaginingthecity.com page load time and found that the first response time was 103 ms and then it took 13.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
imaginingthecity.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value9.5 s
0/100
25%
Value5.3 s
59/100
10%
Value180 ms
92/100
30%
Value0.227
55/100
15%
Value4.9 s
78/100
10%
103 ms
69 ms
72 ms
124 ms
125 ms
Our browser made a total of 43 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Imaginingthecity.com, 21% (9 requests) were made to Bucket1.format-assets.com and 14% (6 requests) were made to Use.edgefonts.net. The less responsive or slowest element that took the longest time to load (10.6 sec) relates to the external source Format-com-cld-res.cloudinary.com.
Page size can be reduced by 559.4 kB (15%)
3.8 MB
3.3 MB
In fact, the total size of Imaginingthecity.com main page is 3.8 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 3.1 MB which makes up the majority of the site volume.
Potential reduce by 304.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 304.5 kB or 92% of the original size.
Potential reduce by 136 B
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. Imagining The City images are well optimized though.
Potential reduce by 207.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 207.3 kB or 66% of the original size.
Potential reduce by 47.4 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. Imaginingthecity.com needs all CSS files to be minified and compressed as it can save up to 47.4 kB or 82% of the original size.
Number of requests can be reduced by 18 (49%)
37
19
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Imagining The City. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
www.imaginingthecity.net
103 ms
jquery.scrollpane.css
69 ms
crimson-text.js
72 ms
share_panel-a983444eba01955e5ad018d31cf0a430a54c9532f866f36728b72f51768dae17.css
124 ms
font-awesome.min-4beed5f2b0ee8f6550ccd992748f76540633c5a205510d3648a52723a3adcb71.css
125 ms
theme_social-c985894a58f09ef7b4feca674406de2916e87cbbb58d420fff1ac15b709ac68c.css
141 ms
stylesheet.css
199 ms
jquery.js
69 ms
jquery.migrate.js
68 ms
jquery.cookie.js
65 ms
jquery.lazyload.js
67 ms
jquery.jscrollpane.js
67 ms
jquery.mousewheel.js
90 ms
scrollDelta-1-a3dd9cda1577a24806f10f58011d0abb0bb95829e14b333f8ff198669c28d017.js
137 ms
responsive-5879e596e12a8817b3efa337f24cb47e34fdd28c2fa64d324e5a2a07b4611264.js
138 ms
mobile_menu-979959ccc30317859c174e9b3ee8f181dd58e9b00bb06bab9a2a52c8fc127fd8.js
136 ms
theme.js
90 ms
favicon_fixup-c07ecdcd7c9c7d4a1245db8a74c43258e97779780064ee802a5681610614b69b.js
137 ms
4ormat-b2a281bf412c1e982414a3bb51f2ece8ff436bf93c673c10f048fe739b61c361.js
138 ms
www.imaginingthecity.net
217 ms
153230-9175500-logotoff2.png
277 ms
loading.gif
152 ms
ga.js
213 ms
153230-7998369-oceans_polychrome_100000_of_40_.jpg
188 ms
153230-9208281-text_jpg.jpg
230 ms
153230-7998443-oceans_polychrome_100023_of_40_.jpg
268 ms
153230-7998424-oceans_polychrome_100012_of_40_.jpg
275 ms
153230-7998455-oceans_polychrome_100031_of_40_.jpg
251 ms
153230-7998468-oceans_polychrome_100038_of_40_.jpg
224 ms
153230-7998400-oceans_polychrome_100006_of_40_.jpg
256 ms
153230-7998419-oceans_polychrome_100011_of_40_.jpg
10562 ms
153230-7998425-oceans_polychrome_100013_of_40_.jpg
308 ms
153230-7998450-oceans_polychrome_100027_of_40_.jpg
339 ms
153230-7998447-oceans_polychrome_100025_of_40_.jpg
323 ms
153230-7998445-oceans_polychrome_100024_of_40_.jpg
339 ms
NBAgvOe9OtPKy7Cr4ueJuqe4FvKK-JDSCSnfD68Z_u6ffJ2JggMdeMJ6Mk6fwyBuSh90ZAs1ZAZzd1sDOco8i26I.woff
114 ms
3U9jpfsmfrTGozmHxpGeRjb_ecCws2-1vlOUrrInQ19ff524ggMdeMJ6Mk6fwyBuSh90ZAs1ZAZzd1sDOco8i26Y.woff
148 ms
HdCWBrMYdxZWGa1qwMLIyyb8xs6KdzdEYeq2BhCBnO3ffFx4ggMdeMJ6Mk6fwyBuSh90ZAs1ZAZzd1sDOco8i265.woff
177 ms
v-KLJvBvxPJ-hfK3Ti25Gd1UNGAFAdpANL6E-X6TpASff5Y4ggMdeMJ6Mk6fwyBuSh90ZAs1ZAZzd1sDOco8i26s.woff
203 ms
theme_social.woff
113 ms
__utm.gif
34 ms
__utm.gif
23 ms
p.gif
142 ms
imaginingthecity.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
imaginingthecity.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
imaginingthecity.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imaginingthecity.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 Imaginingthecity.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.
imaginingthecity.com
Open Graph description is not detected on the main page of Imagining The City. 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: