3 sec in total
311 ms
2.5 sec
204 ms
Welcome to cityheritage.com homepage info - get ready to check Cityheritage best content right away, or after learning these important things about cityheritage.com
Buy a domain and see how a premium domain can be the best investment. Your business starts here. Buy a domain today.
Visit cityheritage.comWe analyzed Cityheritage.com page load time and found that the first response time was 311 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
cityheritage.com performance score
name
value
score
weighting
Value8.0 s
0/100
10%
Value10.9 s
0/100
25%
Value15.1 s
1/100
10%
Value4,200 ms
1/100
30%
Value0.134
80/100
15%
Value22.6 s
1/100
10%
311 ms
195 ms
110 ms
56 ms
109 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Cityheritage.com, 10% (12 requests) were made to D.adroll.com and 6% (7 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (410 ms) relates to the external source Connect.facebook.net.
Page size can be reduced by 739.0 kB (63%)
1.2 MB
427.5 kB
In fact, the total size of Cityheritage.com main page is 1.2 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. 70% of websites need less resources to load. Javascripts take 791.9 kB which makes up the majority of the site volume.
Potential reduce by 34.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 34.3 kB or 75% of the original size.
Potential reduce by 3.5 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, Cityheritage needs image optimization as it can save up to 3.5 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 512.0 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 512.0 kB or 65% of the original size.
Potential reduce by 189.3 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. Cityheritage.com needs all CSS files to be minified and compressed as it can save up to 189.3 kB or 61% of the original size.
Number of requests can be reduced by 76 (78%)
98
22
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cityheritage. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
cityheritage.com
311 ms
monetate.js
195 ms
application.css
110 ms
ng-modal.css
56 ms
angular.min.js
109 ms
ng-modal.js
68 ms
google_analytics.js
67 ms
google_oauth.js
54 ms
bold_chat.js
86 ms
eloqua.js
86 ms
hotjar.js
84 ms
adroll.js
83 ms
impactRadius.js
87 ms
in.js
113 ms
api.js
134 ms
api:client.js
147 ms
app.js
99 ms
cookies.js
84 ms
socialMedia.js
83 ms
countryDropdown.js
102 ms
monetate.js
101 ms
index.js
101 ms
lander.js
105 ms
seoPages.js
104 ms
sitePages.js
104 ms
search.js
108 ms
modal.js
96 ms
forms.js
91 ms
tldSelector.js
94 ms
setFixedTop.js
93 ms
searchBar.js
93 ms
currency.js
97 ms
trust.js
96 ms
conversion.js
78 ms
lander-v2.css
93 ms
tdfs-inner.css
91 ms
tdfs-temp.css
91 ms
thankyou.css
90 ms
entry.js
6 ms
css
25 ms
fontawesome.min.css
13 ms
bd-icons.min.css
15 ms
ga.js
72 ms
foundation-A136666-2811-40ba-bff2-3df3af8bc2ae1.min.js
115 ms
userspace
265 ms
cb=gapi.loaded_0
119 ms
recaptcha__en.js
250 ms
all.js
410 ms
401 ms
ss-social-regular.css
79 ms
css
97 ms
logo-header-2x.png
90 ms
__utm.gif
173 ms
foundation-tags-SD780-3f5b-4f28-957f-6e6dc25a7fc41.min.js
140 ms
__utm.gif
282 ms
postmessageRelay
369 ms
collect
361 ms
cb=gapi.loaded_1
269 ms
310 ms
hotjar-10205.js
218 ms
elqCfg.min.js
216 ms
__utm.gif
195 ms
199 ms
framework
124 ms
anchor
63 ms
3193398744-postmessagerelay.js
119 ms
rpc:shindig_random.js
118 ms
styles__ltr.css
111 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
106 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
180 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
180 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
180 ms
fontawesome-webfont.woff
167 ms
350 ms
svrGP
232 ms
modules-043c1e6abe660c48857202e419ff9d8a.js
229 ms
xd_arbiter.php
273 ms
xd_arbiter.php
407 ms
iframe
104 ms
cb=gapi.loaded_0
136 ms
-FHGegChvKELgmHNPF97Aj33qC9PBXl7UyexHItfpAU.js
79 ms
webworker.js
125 ms
logo_48.png
77 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
186 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
193 ms
1233565733-idpiframe.js
62 ms
svrGP.aspx
110 ms
recaptcha__en.js
23 ms
iframerpc
64 ms
vms.js
80 ms
roundtrip.js
13 ms
6ESKICLQUVAGDN5NI2ETS4.js
34 ms
bc.pv
106 ms
fbevents.hashing.js
65 ms
out
16 ms
56 ms
53 ms
55 ms
out
26 ms
out
25 ms
out
24 ms
out
24 ms
out
23 ms
out
52 ms
out
51 ms
out
51 ms
xd_arbiter.php
105 ms
u.php
143 ms
adsct
153 ms
sync
60 ms
47 ms
45 ms
pixel
77 ms
bounce
39 ms
56 ms
u.php
117 ms
u.php
243 ms
u.php
151 ms
tap.php
18 ms
sd
12 ms
377928.gif
12 ms
in
5 ms
cityheritage.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
cityheritage.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
cityheritage.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cityheritage.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Cityheritage.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.
cityheritage.com
Open Graph data is detected on the main page of Cityheritage. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: