5.4 sec in total
1.7 sec
3.4 sec
342 ms
Welcome to std.uz homepage info - get ready to check Std best content for Uzbekistan right away, or after learning these important things about std.uz
ўзбек ва жаҳон футболи, футболи, таҳлил, онлайн-трансляциялар, интервьюлар
Visit std.uzWe analyzed Std.uz page load time and found that the first response time was 1.7 sec and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
std.uz performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value12.4 s
0/100
25%
Value13.1 s
2/100
10%
Value1,000 ms
27/100
30%
Value0.015
100/100
15%
Value24.4 s
0/100
10%
1709 ms
248 ms
167 ms
666 ms
167 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 67% of them (56 requests) were addressed to the original Std.uz, 19% (16 requests) were made to Adcode.rontar.com and 2% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Std.uz.
Page size can be reduced by 978.9 kB (46%)
2.1 MB
1.2 MB
In fact, the total size of Std.uz main page is 2.1 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 1.0 MB which makes up the majority of the site volume.
Potential reduce by 139.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. This page needs HTML code to be minified as it can gain 49.5 kB, which is 31% 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 139.7 kB or 86% of the original size.
Potential reduce by 76.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. Std images are well optimized though.
Potential reduce by 708.2 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 708.2 kB or 82% of the original size.
Potential reduce by 54.3 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. Std.uz needs all CSS files to be minified and compressed as it can save up to 54.3 kB or 82% of the original size.
Number of requests can be reduced by 33 (41%)
80
47
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Std. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
std.uz
1709 ms
style.css
248 ms
menu.css
167 ms
jquery.js
666 ms
jquery.tabify.js
167 ms
global.js
169 ms
calendar_style.css
168 ms
calendar.js
249 ms
jquery.fancybox.js
418 ms
jquery.fancybox.css
251 ms
jquery-ui.css
336 ms
jquery-ui.js
748 ms
counter2.0.js
393 ms
bg.jpg
180 ms
cables-wires_banner3.jpg
201 ms
social-icons.png
179 ms
top_logo.png
90 ms
fifaworldcup.jpg
91 ms
laligalogo.jpg
146 ms
seriealogol.jpg
261 ms
real.jpg
180 ms
barselona.jpg
221 ms
atletiko_logo.jpg
261 ms
chelsea.jpg
260 ms
united.jpg
260 ms
liverpool.jpg
270 ms
arsenal.jpg
304 ms
pakhtakor_newlogo.jpg
344 ms
bunyodkor.jpg
341 ms
nasaf.jpg
342 ms
loko_logo3.jpg
342 ms
juventus.jpg
350 ms
inter.jpg
386 ms
milan.jpg
423 ms
bavaria.jpg
429 ms
psg.jpg
427 ms
aristotell.jpg
508 ms
inter_milano.jpg
433 ms
hero493.jpg
470 ms
522 ms
Ronaldu.jpg
593 ms
benzema1.jpg
594 ms
infantino.jpg
516 ms
pirlo-chaknorris.jpg
561 ms
ronaldu_rekord.jpg
591 ms
uzb-u19.jpg
605 ms
afc_chl_logo.jpg
606 ms
rontar2_async.js
212 ms
Mashal_Patrik.JPG
650 ms
uzbek-tigers.JPG
606 ms
rontar2_async.js
193 ms
rontar2_async.js
195 ms
chusovitina1.jpg
606 ms
all.js
75 ms
yussar.JPG
581 ms
rontar2_async.js
198 ms
rontar2_async.js
202 ms
counter.php
520 ms
hit
268 ms
cnt.png
387 ms
dc.js
29 ms
calendar.php
773 ms
shhhh-3.jpg
683 ms
Sher.jpg
567 ms
calWaiting.gif
567 ms
58 ms
xd_arbiter.php
92 ms
xd_arbiter.php
154 ms
context_rontar.css
101 ms
GetCode2.aspx
446 ms
GetCode2.aspx
437 ms
GetCode2.aspx
441 ms
GetCode2.aspx
450 ms
GetCode2.aspx
491 ms
utils.js
303 ms
imp.axd
100 ms
imp.axd
102 ms
context.js
226 ms
imp.axd
97 ms
imp.axd
96 ms
30471.gif
325 ms
imp.axd
101 ms
calLeft.gif
86 ms
calRight.gif
86 ms
std.uz 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Form elements do not have associated labels
Links do not have a discernible name
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
std.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
std.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
N/A
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Std.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), while the claimed language is Russian. Our system also found out that Std.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.
std.uz
Open Graph description is not detected on the main page of Std. 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: