29.9 sec in total
2.3 sec
27.4 sec
250 ms
Visit glotr.uz now to see the best up-to-date Glotr content for Uzbekistan and also check out these interesting facts you probably never knew about glotr.uz
Необходимо купить или продать товары в Ташкенте или Узбекистане - покупайте и продавайте в торговом центре Glotr.uz. Все товары и услуги.
Visit glotr.uzWe analyzed Glotr.uz page load time and found that the first response time was 2.3 sec and then it took 27.6 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.
glotr.uz performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value18.7 s
0/100
25%
Value9.9 s
9/100
10%
Value3,600 ms
1/100
30%
Value1.154
1/100
15%
Value22.0 s
1/100
10%
2279 ms
7756 ms
11074 ms
1413 ms
2051 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 92% of them (67 requests) were addressed to the original Glotr.uz, 5% (4 requests) were made to Google-analytics.com and 1% (1 request) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (11.1 sec) belongs to the original domain Glotr.uz.
Page size can be reduced by 442.2 kB (44%)
1.0 MB
559.4 kB
In fact, the total size of Glotr.uz main page is 1.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. 15% of websites need less resources to load. Javascripts take 426.3 kB which makes up the majority of the site volume.
Potential reduce by 48.9 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 48.9 kB or 76% of the original size.
Potential reduce by 35.9 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. Glotr images are well optimized though.
Potential reduce by 285.4 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 285.4 kB or 67% of the original size.
Potential reduce by 72.0 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. Glotr.uz needs all CSS files to be minified and compressed as it can save up to 72.0 kB or 83% of the original size.
Number of requests can be reduced by 14 (20%)
70
56
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Glotr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
glotr.uz
2279 ms
4429b704.css
7756 ms
4429b704.js
11074 ms
jquery.sticky.js
1413 ms
topicons.png
2051 ms
541 ms
816 ms
logo.png
1438 ms
create_icon.png
1855 ms
checkbox.png
1598 ms
cat_icon.png
1010 ms
14333930859137.jpg
3492 ms
14277969137089.jpg
3386 ms
14183856327245.jpg
3646 ms
hanshaking.png
2736 ms
14439698113445.jpg
3850 ms
14363464274442.jpg
4002 ms
13849246918450.jpg
5336 ms
14338553653952.jpg
5173 ms
14597898769476.jpg
6022 ms
13852068741657.jpg
5123 ms
13986782955411.jpg
4733 ms
14564718520899.jpg
5277 ms
14334972526434.jpg
6914 ms
14544085445228.jpg
6272 ms
14117159332069.jpg
6359 ms
cat_bot.png
5580 ms
cat_right.png
5684 ms
cat_left.png
5917 ms
14467998644299.jpg
6290 ms
ellipses.png
6228 ms
14334170095139.jpg
6681 ms
13921066228297.jpg
7116 ms
13948616531974.jpg
7216 ms
13869226746098.jpg
7279 ms
14448027629545.jpg
7741 ms
14092911547661.jpg
8466 ms
14068696930631.jpg
8721 ms
14551215453485.jpg
8360 ms
13823377981034.jpg
8784 ms
ga.js
24 ms
analytics.js
45 ms
watch.js
23 ms
__utm.gif
17 ms
collect
26 ms
collect
74 ms
14591615332767.jpg
8137 ms
14413994226440.jpg
8577 ms
14336852962094.jpg
9013 ms
14524864037815.jpg
9395 ms
14531061174140.jpg
9546 ms
14137867520143.jpg
8284 ms
14004943264493.jpg
8715 ms
14175003675620.jpg
8705 ms
14030044162070.jpg
7928 ms
14527052723924.jpg
7766 ms
clock-gray.png
7409 ms
14118160853712.jpg
8312 ms
14560778699366.jpg
8872 ms
14508134524422.jpg
7934 ms
14601381972375.jpg
7229 ms
14578698994845.jpg
7115 ms
13825223386608.jpg
7193 ms
discount-bg.png
7202 ms
13825221464643.jpg
7492 ms
13939559038244.jpg
7714 ms
slideshow2.png
7766 ms
share_button.png
7382 ms
loading.gif
7127 ms
helparrow-bottom.png
6911 ms
helparrow-top.png
7107 ms
ui-bg_flat_75_ffffff_40x100.png
7070 ms
14493014422346.jpg
8259 ms
glotr.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-hidden="true"] elements contain focusable descendents
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
glotr.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
glotr.uz SEO score
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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Glotr.uz 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 Glotr.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.
glotr.uz
Open Graph description is not detected on the main page of Glotr. 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: