5.7 sec in total
618 ms
4.7 sec
372 ms
Click here to check amazing City Call content for Russia. Otherwise, check out these important facts you probably never knew about city-call.ru
Организация аутсорсинг колл центра в Москве от City-Call — продажи по телефону, привлечение, возврат и поиск клиентов. Сегодня мы входим в топ-5 КЦ России
Visit city-call.ruWe analyzed City-call.ru page load time and found that the first response time was 618 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
city-call.ru performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value5.3 s
22/100
25%
Value4.8 s
68/100
10%
Value960 ms
29/100
30%
Value0.323
35/100
15%
Value13.1 s
12/100
10%
618 ms
661 ms
173 ms
317 ms
40 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 25% of them (24 requests) were addressed to the original City-call.ru, 14% (13 requests) were made to Vk.com and 11% (10 requests) were made to W.uptolike.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain City-call.ru.
Page size can be reduced by 692.8 kB (52%)
1.3 MB
629.8 kB
In fact, the total size of City-call.ru main page is 1.3 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 708.0 kB which makes up the majority of the site volume.
Potential reduce by 140.7 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 140.7 kB or 83% of the original size.
Potential reduce by 214.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. Obviously, City Call needs image optimization as it can save up to 214.2 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 261.8 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 261.8 kB or 74% of the original size.
Potential reduce by 76.1 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. City-call.ru needs all CSS files to be minified and compressed as it can save up to 76.1 kB or 82% of the original size.
Number of requests can be reduced by 50 (60%)
83
33
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of City Call. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
city-call.ru
618 ms
www.city-call.ru
661 ms
style.css
173 ms
fancybox.css
317 ms
jquery.min.js
40 ms
main.js
315 ms
jquery.bxslider.min.js
339 ms
select.js
341 ms
jquery.fancybox-1.3.4.pack.js
341 ms
profile.js
342 ms
cities.js
468 ms
logo.jpg
183 ms
bg_login.jpg
181 ms
fon_opt1.png
1598 ms
sloy1-min_mini.jpg
498 ms
bg_read_more_news.jpg
169 ms
sloy3_mini.jpg
310 ms
2slide_opt.jpg
622 ms
bg_actions.jpg
666 ms
our_compay_yerstedey.jpg
506 ms
bg_our_worck.jpg
624 ms
logo_footer.jpg
664 ms
uptolike.js
326 ms
hit
254 ms
watch.js
181 ms
7CoTNHcSBn
170 ms
webfont.js
22 ms
get_years
962 ms
select_check.jpg
631 ms
bg_front_slider.png
733 ms
css
23 ms
RjgO7rYTmqiVp7vzi-Q5UaCWcynf_cDxXwCLxiixG1c.ttf
26 ms
DXI1ORHCpsQm3Vp6mXoaTfOEPOIfcPv-fZ-WyMUtx48.ttf
49 ms
k3k702ZOKiLJc3WVjuplzPOEPOIfcPv-fZ-WyMUtx48.ttf
61 ms
widget_ru_RU.js
201 ms
watch.js
436 ms
hit
128 ms
version.js
164 ms
widgetsModule.js
330 ms
advert.gif
85 ms
1
111 ms
share-counter.html
166 ms
impression.html
327 ms
all.js
40 ms
like_vk.html
321 ms
plusone.js
68 ms
share-button.png
284 ms
117 ms
cb=gapi.loaded_0
44 ms
xd_arbiter.php
33 ms
xd_arbiter.php
42 ms
widgets-batch.js
207 ms
connect.js
556 ms
openapi.js
363 ms
sync
257 ms
extra.js
164 ms
23414332
171 ms
fastbutton
52 ms
pixel
18 ms
405 ms
pixel
16 ms
rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw
7 ms
cb=gapi.loaded_0
13 ms
cb=gapi.loaded_1
40 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
83 ms
like.php
76 ms
9S-PuPSi5xI.js
36 ms
LVx-xkvaJ0b.png
25 ms
match
89 ms
dk
142 ms
share.3aa457d6.css
137 ms
upload.gif
121 ms
widget_like.php
274 ms
ok-like-bg-l.png
136 ms
ok-logon.png
272 ms
preloader.gif
396 ms
share.php
141 ms
share.php
226 ms
fql.query
123 ms
fql.query
201 ms
share_count
256 ms
share_count
268 ms
count.json
34 ms
count.json
34 ms
support.html
167 ms
loader_nav19188_3.js
160 ms
lite.css
173 ms
lite.js
474 ms
lang3_0.js
245 ms
widgets.css
246 ms
xdm.js
250 ms
al_like.js
289 ms
dk
139 ms
dk
220 ms
like_widget.png
121 ms
city-call.ru accessibility score
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 input fields do not have accessible names
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
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
city-call.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
city-call.ru 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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise City-call.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that City-call.ru 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.
city-call.ru
Open Graph description is not detected on the main page of City Call. 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: