5.7 sec in total
378 ms
5 sec
345 ms
Click here to check amazing Kandagar content for Russia. Otherwise, check out these important facts you probably never knew about kandagar.com
Туроператор Кандагар предложение оздоровительнолечебных и экскурсионных туров Описание здравниц и санаториев цены наличие мест
Visit kandagar.comWe analyzed Kandagar.com page load time and found that the first response time was 378 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
kandagar.com performance score
name
value
score
weighting
Value2.9 s
51/100
10%
Value5.4 s
21/100
25%
Value6.1 s
45/100
10%
Value1,420 ms
15/100
30%
Value0.016
100/100
15%
Value13.3 s
12/100
10%
378 ms
488 ms
767 ms
232 ms
349 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 68% of them (79 requests) were addressed to the original Kandagar.com, 21% (24 requests) were made to Online.kandagar.com and 3% (3 requests) were made to Img.kandagar.com. The less responsive or slowest element that took the longest time to load (933 ms) belongs to the original domain Kandagar.com.
Page size can be reduced by 274.2 kB (18%)
1.6 MB
1.3 MB
In fact, the total size of Kandagar.com main page is 1.6 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. 50% of websites need less resources to load. Images take 874.2 kB which makes up the majority of the site volume.
Potential reduce by 125.0 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 58.2 kB, which is 40% 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 125.0 kB or 86% of the original size.
Potential reduce by 35.8 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. Kandagar images are well optimized though.
Potential reduce by 88.6 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 88.6 kB or 19% of the original size.
Potential reduce by 24.8 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. Kandagar.com needs all CSS files to be minified and compressed as it can save up to 24.8 kB or 32% of the original size.
Number of requests can be reduced by 58 (54%)
107
49
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kandagar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
kandagar.com
378 ms
kandagar.com
488 ms
www.kandagar.com
767 ms
jquery.ck.css
232 ms
jquery.gddr.css
349 ms
selectBox.css
350 ms
gdstyle_main.css
470 ms
kandagar.css
475 ms
main.css
351 ms
homepage.css
351 ms
main_form.css
463 ms
font-awesome.min.css
467 ms
owl.carousel.min.css
471 ms
openapi.js
781 ms
bannercode.js
901 ms
jquery-2.1.4.min.js
480 ms
jquery.reveal.js
467 ms
footer.js
471 ms
jquery.ck.js
634 ms
jquery.gddr.js
474 ms
kandagar.js
481 ms
currency.js
632 ms
geo_autocomplete_2.js
708 ms
owl.carousel.min.js
633 ms
main.js
721 ms
header.js
633 ms
homepage.js
698 ms
analytics.js
41 ms
watch.js
35 ms
bg_2015-1.jpg
449 ms
colon_fon.png
334 ms
light-bg.gif
338 ms
blue-bg.gif
439 ms
shadow.png
447 ms
logo_3.png
452 ms
header-razd-h2.png
455 ms
triangle.png
460 ms
en_logo.png
557 ms
arrow-run.png
564 ms
lm-arrow-2.png
565 ms
element_fire.png
699 ms
46172d16e0e75870af1316a92662f463.jpg
700 ms
e73c8d7b1cdc42bffa043df1345b1cb7.jpg
701 ms
2ed75a60b48adba5aba0f30e0bd0d310.jpg
702 ms
b3089f39d074a68602f6e58178bba67a.png
703 ms
7e6a9cdf1ed9fb2b90db9084d12e1833.png
702 ms
5b962ccd62c1f8a0d18c8e6e8c5f2946.png
702 ms
2ff6c4eb26e0357c02e6376baf284e8e.png
703 ms
9523f35f1d6624627ee993631e206310.png
704 ms
b269a26b38df23b5e6ed63beeb945f7f.jpg
787 ms
1060fa711e9b1654b905d77beece0da1.jpg
799 ms
ddf22e27b14ff0b510a5b955676705f3.jpg
798 ms
23bc66bb8d97f21ab158dc8617f7f9af.jpg
780 ms
collect
12 ms
js
70 ms
52a5886de47d7caf50324f763343bc31.jpg
840 ms
b339dba050126eba9662bbd9547a77bb.jpg
732 ms
e6efaceb5d8b9be28fb9444f2ef4283a.jpg
812 ms
4e37521e40654d4aa644db47f4353917.jpg
821 ms
aa30ca9ec1cee2faf61f565b121a443b.jpg
933 ms
up.png
674 ms
soc-icon-viber.svg
685 ms
soc-icon-whatsapp.svg
770 ms
subscribe_result.png
776 ms
rss.png
723 ms
962f5444353612459aece615cd22101a.jpg
719 ms
help.png
724 ms
rst.png
805 ms
rostourism.png
812 ms
subscribe_form.png
616 ms
vk-telega-insta-fb.png
623 ms
left-menu-li.png
625 ms
line.png
620 ms
call-icon.png
702 ms
mail-icon.png
715 ms
hit
512 ms
ttt.aspx
655 ms
Escape
655 ms
status
139 ms
blue-bg.gif
710 ms
icon-clear-field.svg
580 ms
loader8.gif
583 ms
5879df125676dfe46d44d70563d4de8b.jpg
597 ms
826 ms
831 ms
838 ms
fontawesome-webfont.woff
767 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
230 ms
hit
126 ms
styles.css
123 ms
Classic.css
120 ms
WebResource.axd
239 ms
ScriptResource.axd
361 ms
ScriptResource.axd
367 ms
jquery.js
720 ms
PopCalendarAjaxNet.js
610 ms
PopCalendarFunctionsAjaxNet.js
483 ms
checkboxlist.js
480 ms
datepicker.js
482 ms
dialog.js
485 ms
Utils.js
609 ms
Help.js
608 ms
jquery.colorbox.js
609 ms
ttt.aspx
622 ms
jquery.url.js
184 ms
online.js
200 ms
rtrg
123 ms
kandagar.css
622 ms
c4f5f5718281e2cbc45c90c761d87fd0.jpg
882 ms
3de609da71dab0ce959ffe0aff79d291.jpg
633 ms
df75cddc18198d69e68c51b64ee1d1dd.jpg
629 ms
jgk7.jpg
38 ms
repeart.png
38 ms
ttt.aspx
288 ms
ttt.aspx
141 ms
jgk7.jpg
581 ms
repeart.png
237 ms
kandagar.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
Image elements do not have [alt] attributes
Links do not have a discernible 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.
kandagar.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
kandagar.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kandagar.com 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 Kandagar.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.
kandagar.com
Open Graph description is not detected on the main page of Kandagar. 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: