28.2 sec in total
854 ms
26.6 sec
707 ms
Welcome to shahar.uz homepage info - get ready to check Shahar best content for Uzbekistan right away, or after learning these important things about shahar.uz
Мультилистинг - поисковик недвижимость Купить, продать, снять и сдать квартиры, дома и коммерческую недвижимость - быстро и выгодно в... Ташкентская
Visit shahar.uzWe analyzed Shahar.uz page load time and found that the first response time was 854 ms and then it took 27.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
shahar.uz performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value6.3 s
11/100
25%
Value10.2 s
8/100
10%
Value2,100 ms
7/100
30%
Value0.329
35/100
15%
Value22.3 s
1/100
10%
854 ms
372 ms
241 ms
246 ms
671 ms
Our browser made a total of 176 requests to load all elements on the main page. We found that 41% of them (72 requests) were addressed to the original Shahar.uz, 7% (13 requests) were made to Api-maps.yandex.ru and 6% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Sat02.maps.yandex.net.
Page size can be reduced by 1.2 MB (60%)
2.0 MB
794.9 kB
In fact, the total size of Shahar.uz main page is 2.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 240.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 240.3 kB or 74% of the original size.
Potential reduce by 15.6 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. Shahar images are well optimized though.
Potential reduce by 778.1 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 778.1 kB or 66% of the original size.
Potential reduce by 158.9 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. Shahar.uz needs all CSS files to be minified and compressed as it can save up to 158.9 kB or 81% of the original size.
Number of requests can be reduced by 96 (59%)
163
67
The browser has sent 163 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shahar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 53 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
shahar.uz
854 ms
bootstrap.min.css
372 ms
style_old.css
241 ms
purecssmenu.css
246 ms
jquery.js
671 ms
bootstrap.min.js
259 ms
jquery-ui.js
595 ms
jquery.lightbox-0.5.js
384 ms
jquery.lightbox-0.5.css
385 ms
jqueryslidemenu.css
402 ms
system.css
518 ms
nanoapi_beta.js
523 ms
304 ms
js
219 ms
jqueryslidemenu.js
525 ms
estate.js
577 ms
jquery.ui.all.css
724 ms
sitebillcore.js
725 ms
interface.js
724 ms
style.css
727 ms
element.js
70 ms
autoNumeric-1.7.5.js
727 ms
mycombobox_ac.js
772 ms
search_form.js
789 ms
utils.js
790 ms
refresher.functions.js
790 ms
json2.js
822 ms
md5.js
758 ms
all.js
494 ms
adsbygoogle.js
60 ms
c.js
630 ms
1721 ms
c.js
507 ms
combine.xml
2647 ms
jquery.ui.base.css
152 ms
jquery.ui.theme.css
148 ms
jquery.ui.core.css
144 ms
jquery.ui.resizable.css
139 ms
jquery.ui.selectable.css
144 ms
jquery.ui.accordion.css
152 ms
jquery.ui.autocomplete.css
142 ms
jquery.ui.button.css
140 ms
jquery.ui.dialog.css
314 ms
jquery.ui.slider.css
314 ms
jquery.ui.tabs.css
315 ms
jquery.ui.datepicker.css
316 ms
jquery.ui.progressbar.css
316 ms
logo.gif
382 ms
logo.gif
154 ms
prv54cdbc9ca1b68_1422769308_1.jpeg
155 ms
m.jpg
154 ms
prv56c37245e18ec_1455649349_1.jpg
154 ms
prv56ffacb851fe2_1459596472_5.jpg
153 ms
no_foto.png
387 ms
prv570554bfb44aa_1459967167_1.jpg
262 ms
prv5704a46b4cfd7_1459922027_1.jpg
260 ms
prv5703d54130536_1459868993_1.jpg
257 ms
prv5703d3579af80_1459868503_2.jpg
255 ms
prv5703c9addf1e1_1459866029_1.jpg
254 ms
prv5703a49a524cc_1459856538_5.jpg
372 ms
tash.jpg
579 ms
captcha.php
376 ms
rss.gif
373 ms
vk.png
373 ms
fb.png
470 ms
tw.png
476 ms
in.jpg
471 ms
gplus.jpg
473 ms
ok.jpg
474 ms
insta.jpg
570 ms
16+.png
571 ms
glyphicons-halflings-white.png
524 ms
translateelement.css
175 ms
main.js
208 ms
element_main.js
140 ms
glyphicons-halflings.png
264 ms
list.png
217 ms
thumb.png
299 ms
square.png
300 ms
add_fav.png
302 ms
context.js
288 ms
639 ms
xd_arbiter.php
527 ms
xd_arbiter.php
1067 ms
ca-pub-8822098336291935.js
774 ms
zrt_lookup.html
623 ms
show_ads_impl.js
873 ms
flist.png
715 ms
context_static_r1084.js
573 ms
analytics.js
544 ms
ui-bg_flat_75_ffffff_40x100.png
225 ms
ui-bg_highlight-soft_75_cccccc_1x100.png
224 ms
ui-bg_glass_75_e6e6e6_1x400.png
225 ms
ui-bg_glass_65_ffffff_1x400.png
225 ms
p70G.libpack.js
703 ms
c2.js
329 ms
translate_24dp.png
336 ms
l
144 ms
cleardot.gif
336 ms
te_ctrl3.gif
90 ms
googlelogo_color_68x28dp.png
171 ms
loading.gif
139 ms
collect
376 ms
125687
203 ms
watch.js
2 ms
like_box.php
344 ms
c2.js
287 ms
te_bk.gif
129 ms
ads
427 ms
osd.js
104 ms
xwWG67BZFLW.css
953 ms
92jR-n5wPxz.css
1236 ms
SRSW8M763HA.js
1292 ms
ullQFyhrQFI.js
1727 ms
y97Ig99UVTs.js
1412 ms
KHAtULXOQuz.js
1491 ms
ads
908 ms
1_1447967217.js
1143 ms
4109926589100282512
1125 ms
abg.js
1098 ms
m_js_controller.js
1085 ms
googlelogo_color_112x36dp.png
89 ms
3282737770107903331
1073 ms
ef50ac9e93aaebe3299791c79f277f8e.cur
754 ms
722 ms
3ce22e999d54bb9ca8150a59207f9d3e.cur
843 ms
4965b66fe115b2f2ed500ece66514d86.cur
926 ms
77492cf358d8b12629399322926c93f2.cur
926 ms
fa68b413dd7a42450e7481fda0c47764.png
683 ms
299a64ea143172b5078d3c40c89d1c26.png
681 ms
830 ms
tiles
895 ms
tiles
462 ms
tiles
831 ms
tiles
778 ms
tiles
626 ms
634 ms
815 ms
tiles
645 ms
tiles
820 ms
tiles
855 ms
tiles
857 ms
tiles
20380 ms
tiles
20379 ms
tiles
799 ms
tiles
797 ms
tiles
845 ms
tiles
849 ms
tiles
858 ms
tiles
979 ms
tiles
881 ms
x_button_blue2.png
68 ms
s
74 ms
inception-1458751524111.js
822 ms
j6SDDiQit5YY48GNgPpnCluJgoNCzbKlh5o6eVjReZI.js
16 ms
transp.png
237 ms
arrows3.png
328 ms
default.png
310 ms
mic.png
337 ms
CWicon-send7.png
367 ms
10888879_1526141221001708_3832659217496758318_n.jpg
738 ms
10301929_1526141047668392_5271487856100468232_n.jpg
830 ms
10441309_931357026982480_1018933538726762540_n.jpg
902 ms
12512378_554541668041157_2165636377433117558_n.jpg
967 ms
12742702_195622447461857_794230490629597358_n.jpg
969 ms
12936599_928709307237261_7900023616396690691_n.jpg
976 ms
1379841_10150004552801901_469209496895221757_n.jpg
969 ms
wL6VQj7Ab77.png
199 ms
1JLnMyDN79z.png
198 ms
VXcANLwwL5J.js
79 ms
i8XO-4kv8i7.js
78 ms
common.js
50 ms
util.js
136 ms
stats.js
85 ms
AuthenticationService.Authenticate
352 ms
h_checksite.ashx
223 ms
shahar.uz 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-*] attributes do not match their roles
button, link, and menuitem elements do not have accessible names.
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
shahar.uz 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
shahar.uz 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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shahar.uz can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Shahar.uz 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.
shahar.uz
Open Graph data is detected on the main page of Shahar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: