15.3 sec in total
2.1 sec
12.5 sec
723 ms
Visit proofline.uz now to see the best up-to-date Proofline content for Uzbekistan and also check out these interesting facts you probably never knew about proofline.uz
Visit proofline.uz
We analyzed Proofline.uz page load time and found that the first response time was 2.1 sec and then it took 13.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster. This domain responded with an error, which can significantly jeopardize Proofline.uz rating and web reputation
proofline.uz performance score
name
value
score
weighting
Value1.6 s
94/100
10%
Value3.0 s
78/100
25%
Value4.4 s
74/100
10%
Value860 ms
33/100
30%
Value0.345
32/100
15%
Value4.1 s
86/100
10%
2118 ms
522 ms
879 ms
666 ms
409 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that all of those requests were addressed to Proofline.uz and no external sources were called. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Proofline.uz.
Page size can be reduced by 1.3 MB (17%)
7.5 MB
6.2 MB
In fact, the total size of Proofline.uz main page is 7.5 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 6.6 MB which makes up the majority of the site volume.
Potential reduce by 56.6 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 10.8 kB, which is 16% 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 56.6 kB or 84% of the original size.
Potential reduce by 550.7 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. Proofline images are well optimized though.
Potential reduce by 640.0 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 640.0 kB or 79% of the original size.
Potential reduce by 31.1 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. Proofline.uz needs all CSS files to be minified and compressed as it can save up to 31.1 kB or 81% of the original size.
Number of requests can be reduced by 17 (18%)
97
80
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Proofline. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
proofline.uz
2118 ms
reset_.css
522 ms
style.css
879 ms
catalog-menu.css
666 ms
device.min.js
409 ms
jquery_005.js
1418 ms
main.js
1234 ms
jquery-ui-1.js
2579 ms
jquery-1.8.2.min.js
1703 ms
jquery.cycle.all.js
1412 ms
style.css
1102 ms
jcarousellite_1.0.1.pack.js
1336 ms
jquery.mousewheel-3.0.6.pack.js
1474 ms
jquery.fancybox.js
1949 ms
jquery.fancybox.css
1601 ms
jquery.fancybox-buttons.css
1631 ms
jquery.fancybox-buttons.js
1669 ms
jquery.fancybox-thumbs.css
1790 ms
jquery.fancybox-thumbs.js
1822 ms
jquery.fancybox-media.js
1865 ms
functions2.js
1881 ms
GoodCyr-WideLight.ttf
483 ms
preloader.gif
978 ms
background.jpg
592 ms
logo.png
406 ms
ru.png
223 ms
eng.png
222 ms
lupa.jpg
986 ms
df50a799a306_1308_716.jpg
3418 ms
banner_phone.png
593 ms
44c274ee4d5c_1308_716.jpg
2911 ms
0928d815ce35_1308_716.jpg
2598 ms
b05c1fbeb477_1308_716.jpg
3233 ms
36f8fbcec830_1308_716.jpg
2278 ms
d46edafba777_1308_716.jpg
4051 ms
5db9708a51d9_1308_716.jpg
3947 ms
2ec4501fb239_1308_716.jpg
4783 ms
navigate.png
3108 ms
banner_right.jpg
4340 ms
catalog.jpg
3708 ms
5f9507d98ec9_176_135.JPG
3626 ms
news_background.png
3851 ms
uznat.png
3899 ms
7e481cc3da5c_176_135.jpg
4066 ms
64259d402e36_176_135.jpg
4125 ms
5a3b8a4d6a66_176_135.jpg
4157 ms
5bc28272c159_176_135.jpg
4256 ms
7482855fa149_176_135.jpg
4271 ms
ea3964c69600_176_135.jpg
4316 ms
f3a1409b429d_176_135.jpg
4346 ms
bc672d3382a9_176_135.jpg
4448 ms
568cd7c68bae_176_135.jpg
4468 ms
f67834120cd8_176_135.jpg
4503 ms
b91b00f4f5aa_176_135.jpg
4559 ms
d48a4dfc782a_176_135.jpg
4567 ms
cedf82493d56_176_135.jpg
4642 ms
5843a28a3e02_176_135.jpg
4667 ms
HeliosCondThin.otf
4482 ms
574ee8874005_176_135.jpg
4544 ms
959b1e33aa1a_176_135.jpg
4356 ms
da215ec564d6_176_135.jpg
4415 ms
background.jpg
4321 ms
menu_1.png
4328 ms
catalog-menu.png
3973 ms
ul.jpg
3984 ms
right.png
2688 ms
menu_2.png
2480 ms
menu_3.png
2200 ms
menu_4.png
2000 ms
menu_5.png
1902 ms
menu_6.png
1731 ms
menu_7.png
1536 ms
3(1).jpg
4161 ms
1.png
1461 ms
soc_1.jpg
1462 ms
soc_2.jpg
1414 ms
soc_3.jpg
1314 ms
footer_logo.png
1317 ms
client_1.jpg
1408 ms
client_2.jpg
1397 ms
client_3.jpg
1306 ms
client_4.jpg
1299 ms
client_5.jpg
1270 ms
client_6.jpg
1382 ms
client_7.jpg
1947 ms
client_8.jpg
1311 ms
client_9.jpg
1287 ms
client_10.jpg
1310 ms
client_11.jpg
1350 ms
client_12.jpg
1371 ms
client_13.jpg
1312 ms
client_14.jpg
1350 ms
client_15.jpg
1396 ms
client_16.jpg
1366 ms
client_17.jpg
1394 ms
client_18.jpg
1444 ms
client_19.jpg
1413 ms
phone.png
1403 ms
mess.png
1435 ms
map.jpg
2271 ms
city.png
1520 ms
proofline.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
Links do not have a discernible name
proofline.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
proofline.uz SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
UZ
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Proofline.uz can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed Uzbek language. Our system also found out that Proofline.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.
proofline.uz
Open Graph description is not detected on the main page of Proofline. 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: