5.5 sec in total
690 ms
4.7 sec
203 ms
Visit city.travel now to see the best up-to-date City content for Russia and also check out these interesting facts you probably never knew about city.travel
Search and book air tickets and hotels all over the world. Cheap prices and best availability.
Visit city.travelWe analyzed City.travel page load time and found that the first response time was 690 ms and then it took 4.9 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.travel performance score
name
value
score
weighting
Value2.6 s
65/100
10%
Value17.4 s
0/100
25%
Value9.0 s
14/100
10%
Value1,280 ms
18/100
30%
Value0.155
74/100
15%
Value22.2 s
1/100
10%
690 ms
156 ms
319 ms
456 ms
458 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 75% of them (78 requests) were addressed to the original City.travel, 3% (3 requests) were made to Top-fwz1.mail.ru and 3% (3 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain City.travel.
Page size can be reduced by 235.4 kB (18%)
1.3 MB
1.1 MB
In fact, the total size of City.travel 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. 40% of websites need less resources to load. Images take 996.4 kB which makes up the majority of the site volume.
Potential reduce by 57.1 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. This page needs HTML code to be minified as it can gain 16.4 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 57.1 kB or 82% of the original size.
Potential reduce by 29.7 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. City images are well optimized though.
Potential reduce by 65.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 65.5 kB or 42% of the original size.
Potential reduce by 83.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.travel needs all CSS files to be minified and compressed as it can save up to 83.1 kB or 82% of the original size.
Number of requests can be reduced by 60 (61%)
99
39
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 31 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
city.travel
690 ms
detectinframe.js
156 ms
common.css
319 ms
jquery.ui.css
456 ms
search.css
458 ms
jquery.js
620 ms
jquery-ui-1.8.9.custom.min.js
791 ms
scripts.js
647 ms
jquery.simplemodal.js
493 ms
button_totop.js
604 ms
jquery.scrollTo-min.js
604 ms
script_avia.js
651 ms
jquery.validate.min.js
756 ms
jquery.autocomplete.js
755 ms
sc.js
767 ms
tip.js
811 ms
detectmobile.js
811 ms
jquery.stylish-select.js
905 ms
jquery.formCounter-0.4.js
903 ms
jquery.groupinputs.js
918 ms
jquery.spritely-0.6.js
942 ms
fx.js
951 ms
jquery.ct.redline.js
963 ms
jquery.ct.bigpicslider.js
1052 ms
script_tour.js
1108 ms
pixelNew.js
33 ms
bk.jpg
314 ms
date-pic-sh.png
160 ms
data-day.gif
159 ms
active-day.png
164 ms
err-ok.png
164 ms
preloader.gif
159 ms
logs-t.png
310 ms
logs-c.png
307 ms
logs-b.png
305 ms
logo.png
312 ms
headerphonenew.png
465 ms
followme.png
454 ms
vkontakte-top.png
456 ms
facebook-top.png
458 ms
livejournal.png
462 ms
twitter-top.png
466 ms
common.css
608 ms
avia-link-top-b.png
609 ms
hotel-link-top-b.png
610 ms
filter-bk.png
614 ms
filter-plane.png
615 ms
date-plane.png
618 ms
planes-icos.png
756 ms
peoples-point.gif
757 ms
peoples-icos.png
760 ms
filter-but.png
769 ms
blues.gif
769 ms
all-about.png
771 ms
mains1.png
910 ms
mains2.png
911 ms
mains3.png
914 ms
dot-transparent.png
921 ms
visa-logo.png
922 ms
mastercard-logo.png
928 ms
maestro4.png
1039 ms
quwi-logo.png
1031 ms
analytics.js
40 ms
ooo4
92 ms
gtm.js
65 ms
code.js
643 ms
dc.js
126 ms
watch.js
430 ms
i.js
76 ms
b10358fcf47c11e97b6de2d6ddd4cf70a6f6085c.2.js
88 ms
collect
50 ms
pixel.gif
14 ms
470 ms
mts3.png
930 ms
megafon2.png
927 ms
evroset-logo.png
931 ms
svyaznoi-logo.png
1057 ms
e
56 ms
__utm.gif
28 ms
compay.png
916 ms
logo-footer.png
936 ms
point.gif
944 ms
tour-sel.png
940 ms
totop.png
981 ms
bg-footer8.png
913 ms
bg-footer29.png
1364 ms
g1.png
1585 ms
bpbt-act.png
960 ms
g2.png
1583 ms
bpbt-noact.png
977 ms
advert.gif
88 ms
g3.png
1664 ms
rl-gradient.png
971 ms
183 ms
counter
166 ms
1
85 ms
533 ms
wv.php
257 ms
nvid.png
348 ms
pixel
36 ms
pixel
14 ms
sync
855 ms
nvid.png
91 ms
tracker
156 ms
city.travel 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Form elements do not have associated labels
Links do not have a discernible name
city.travel 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
city.travel 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise City.travel can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that City.travel 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.travel
Open Graph data is detected on the main page of City. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: