17.8 sec in total
802 ms
16.7 sec
304 ms
Visit mobile.beeline.uz now to see the best up-to-date Mobile Beeline content for Uzbekistan and also check out these interesting facts you probably never knew about mobile.beeline.uz
Visit mobile.beeline.uzWe analyzed Mobile.beeline.uz page load time and found that the first response time was 802 ms and then it took 17 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
mobile.beeline.uz performance score
802 ms
273 ms
266 ms
749 ms
1542 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 76% of them (63 requests) were addressed to the original Mobile.beeline.uz, 12% (10 requests) were made to Static.xx.fbcdn.net and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (10.6 sec) belongs to the original domain Mobile.beeline.uz.
Page size can be reduced by 250.9 kB (64%)
391.8 kB
140.9 kB
In fact, the total size of Mobile.beeline.uz main page is 391.8 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. 25% of websites need less resources to load. Javascripts take 299.7 kB which makes up the majority of the site volume.
Potential reduce by 25.2 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 25.2 kB or 81% of the original size.
Potential reduce by 5.5 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. Mobile Beeline images are well optimized though.
Potential reduce by 219.3 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 219.3 kB or 73% of the original size.
Potential reduce by 903 B
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. Mobile.beeline.uz needs all CSS files to be minified and compressed as it can save up to 903 B or 75% of the original size.
Number of requests can be reduced by 59 (78%)
76
17
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile Beeline. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
mobile.beeline.uz
802 ms
ru
273 ms
main
266 ms
index.wbp
749 ms
css.wbh
1542 ms
swfobject.js
1032 ms
Banners.js
557 ms
jquery-1.5.js
10579 ms
jquery.dimensions.js
805 ms
jquery.mousewheel.min.js
646 ms
cookies.js
801 ms
watch.js
1 ms
ad.wbp
697 ms
jScrollHorizontalPane.css
795 ms
jScrollHorizontalPane.js
1330 ms
ad.wbp
722 ms
conversion.js
71 ms
script.wbp
790 ms
ga.js
127 ms
blank.gif
230 ms
m_an_tl.gif
232 ms
m_fix_tl.gif
913 ms
m_fix_tr.gif
231 ms
m_an_tr.gif
244 ms
m_fix_lt.gif
245 ms
bul_gr.gif
479 ms
m_fix_rt.gif
499 ms
m_a_dl.gif
499 ms
m_a_dr.gif
503 ms
m_a_tl.gif
505 ms
m_a_tr.gif
831 ms
m_fix_ld.gif
836 ms
m_fix_rd.gif
2145 ms
m_an_dl.gif
1310 ms
m_fix_dl.gif
1521 ms
m_fix_dr.gif
1031 ms
m_an_dr.gif
1038 ms
icon_facebook.gif
1108 ms
icon_twitter.gif
1222 ms
icon_odnkl.gif
1232 ms
icon_rss.gif
1299 ms
bar_a_t.gif
1447 ms
bar_a_tl.gif
1447 ms
bar_a_tr.gif
1515 ms
ico_beelineclub.gif
1750 ms
5.gif
1645 ms
bar_a_d.gif
1645 ms
bar_a_dl.gif
1734 ms
bar_a_dr.gif
1745 ms
bul_dot.gif
1934 ms
news_arrow.gif
1941 ms
142x91_dengi_vozvrashyayutsya.jpg
2216 ms
status_small.jpg
2883 ms
ban_mc.jpg
4416 ms
ban_lk.gif
2136 ms
158 ms
__utm.gif
53 ms
likebox.php
355 ms
icon_sms_right.gif
1944 ms
icon-usb-modem-right.gif
2320 ms
icon_sms_right.gif
2127 ms
285 ms
m_bkg_t.gif
2126 ms
m_bkg_l.gif
2183 ms
m_bkg_r.gif
2081 ms
m_bkg_d.gif
2081 ms
bm_gdot.gif
2149 ms
bar_bkg_t.gif
2263 ms
bar_bkg_smt.gif
2269 ms
MxOchIADMT_.css
509 ms
3w3jujerapC.css
578 ms
SRSW8M763HA.js
726 ms
ullQFyhrQFI.js
861 ms
y97Ig99UVTs.js
717 ms
KHAtULXOQuz.js
717 ms
bar_bkg_d.gif
1967 ms
bar_bkg.gif
2023 ms
12936770_1244197545624838_2779070692488219677_n.jpg
426 ms
11703362_1055633827814545_3116782556452142116_n.jpg
595 ms
wL6VQj7Ab77.png
103 ms
1JLnMyDN79z.png
102 ms
VXcANLwwL5J.js
110 ms
i8XO-4kv8i7.js
105 ms
mobile.beeline.uz SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.beeline.uz 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Mobile.beeline.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.
mobile.beeline.uz
Open Graph description is not detected on the main page of Mobile Beeline. 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: