1.9 sec in total
145 ms
1.6 sec
132 ms
Visit citydating.com now to see the best up-to-date Citydating content and also check out these interesting facts you probably never knew about citydating.com
Matching Busy Professional Singles; 1000s of top, Elite Single Professionals are just waiting for you!
Visit citydating.comWe analyzed Citydating.com page load time and found that the first response time was 145 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
citydating.com performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value4.1 s
47/100
25%
Value3.8 s
84/100
10%
Value460 ms
61/100
30%
Value0
100/100
15%
Value9.2 s
32/100
10%
145 ms
391 ms
89 ms
88 ms
138 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 54% of them (37 requests) were addressed to the original Citydating.com, 14% (10 requests) were made to Static.xx.fbcdn.net and 6% (4 requests) were made to A.collective-media.net. The less responsive or slowest element that took the longest time to load (421 ms) relates to the external source Speakpipe.com.
Page size can be reduced by 373.4 kB (63%)
591.2 kB
217.8 kB
In fact, the total size of Citydating.com main page is 591.2 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. 30% of websites need less resources to load. Javascripts take 486.5 kB which makes up the majority of the site volume.
Potential reduce by 55.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 55.5 kB or 72% of the original size.
Potential reduce by 4.0 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, Citydating needs image optimization as it can save up to 4.0 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 307.5 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 307.5 kB or 63% of the original size.
Potential reduce by 6.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. Citydating.com needs all CSS files to be minified and compressed as it can save up to 6.4 kB or 82% of the original size.
Number of requests can be reduced by 50 (76%)
66
16
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Citydating. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
citydating.com
145 ms
www.citydating.com
391 ms
singles.css
89 ms
global.css
88 ms
jscript_lib.js
138 ms
jquery.min.js
31 ms
jquery.fixedposition.js
95 ms
addthis_widget.js
12 ms
conversion.js
15 ms
ecd302droc0n5rvdgysaz6iklg2hx8z5.js
368 ms
analytics.js
170 ms
lg-share-en.gif
140 ms
city_skyline.gif
99 ms
citydating_com.gif
37 ms
search_box_tr.gif
39 ms
search_tag.gif
38 ms
search_iama.gif
94 ms
search_looking.gif
98 ms
search_in.gif
96 ms
but_search_1.gif
97 ms
members_score.gif
96 ms
members_tag.gif
96 ms
members_username.gif
100 ms
members_password.gif
100 ms
but_signin_1.gif
99 ms
search_box_b.gif
100 ms
search_box_br.gif
102 ms
register2.gif
163 ms
but_blog.gif
136 ms
twitterbutton17.png
136 ms
nav_shadow.gif
135 ms
nav_online_1.gif
135 ms
nav_seperator.gif
139 ms
nav_speed_1.gif
159 ms
nav_stories_1.gif
161 ms
nav_tips_1.gif
160 ms
nav_help_1.gif
158 ms
illu_home_v4.gif
317 ms
dating_tag.gif
185 ms
footer_bl.gif
186 ms
footer_br.gif
188 ms
stick.png
186 ms
feedback.gif
187 ms
likebox.php
193 ms
boost
35 ms
300lo.json
62 ms
collect
50 ms
collect
41 ms
collect
40 ms
sh.07f0d9bf220d07a763adad1e.html
33 ms
datapair
33 ms
datapair
29 ms
datapair
31 ms
datapair
32 ms
4g0djh32yaimjogg.png
208 ms
pixel
15 ms
McLpmVM3wCm.css
161 ms
r6Aw0SZFbhw.css
202 ms
q68gy-v_YMF.js
276 ms
FJmpeSpHpjS.js
349 ms
0wM5s1Khldu.js
304 ms
1bNoFZUdlYZ.js
305 ms
pixel
14 ms
label_mic_v.png
421 ms
190261_10150168201475921_5849121_n.jpg
223 ms
wL6VQj7Ab77.png
49 ms
s7jcwEQH7Sx.png
49 ms
I6-MnjEovm5.js
39 ms
pQrUxxo5oQp.js
41 ms
citydating.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
citydating.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
Missing source maps for large first-party JavaScript
citydating.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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Citydating.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), while the claimed language is English. Our system also found out that Citydating.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.
citydating.com
Open Graph description is not detected on the main page of Citydating. 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: