14.6 sec in total
2.4 sec
11.9 sec
407 ms
Visit 1z.by now to see the best up-to-date 1 Z content for Belarus and also check out these interesting facts you probably never knew about 1z.by
???????, ?????????, ???????????? ???????????? ? ?????????????, ??????????, ??????????? ????? ? ?????? ????? ? ? ??????? ?? ?????? ?????. ???????? ????? ???????: ???????????? ? ??????? ???????, ???????...
Visit 1z.byWe analyzed 1z.by page load time and found that the first response time was 2.4 sec and then it took 12.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
1z.by performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value7.9 s
3/100
25%
Value10.3 s
8/100
10%
Value2,260 ms
6/100
30%
Value0.028
100/100
15%
Value17.3 s
4/100
10%
2350 ms
210 ms
378 ms
376 ms
416 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 78% of them (40 requests) were addressed to the original 1z.by, 4% (2 requests) were made to Brut.to and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (7.1 sec) belongs to the original domain 1z.by.
Page size can be reduced by 339.1 kB (62%)
550.3 kB
211.3 kB
In fact, the total size of 1z.by main page is 550.3 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. Images take 263.9 kB which makes up the majority of the site volume.
Potential reduce by 189.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. 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 189.7 kB or 88% of the original size.
Potential reduce by 93.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. Obviously, 1 Z needs image optimization as it can save up to 93.6 kB or 35% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 29.5 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 29.5 kB or 75% of the original size.
Potential reduce by 26.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. 1z.by needs all CSS files to be minified and compressed as it can save up to 26.3 kB or 81% of the original size.
Number of requests can be reduced by 10 (22%)
46
36
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1 Z. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
index.php
2350 ms
index_new.css
210 ms
colorbox.css
378 ms
jquery.fancybox.css
376 ms
jquery.min.js
416 ms
main.js
377 ms
login.js
371 ms
change_fon.js
380 ms
show_category.js
543 ms
basket.js
549 ms
jquery.easing.1.3.js
549 ms
jquery.fancybox-1.2.1.pack.js
552 ms
bck.png
247 ms
head_top_block_vr.png
157 ms
work_time.png
155 ms
shipment_money.png
154 ms
head_menu_body_bck.png
156 ms
basket.png
154 ms
zakaz_zvon.png
298 ms
online_cons.png
293 ms
checking.png
290 ms
logo.png
292 ms
phones.png
297 ms
phones_empty.png
453 ms
icq.png
448 ms
skype.png
449 ms
viber.png
455 ms
mail.png
451 ms
xls.png
1289 ms
private_cab.png
1272 ms
catalog_icon.png
632 ms
plus_red.png
1272 ms
minus_gray.png
641 ms
OpenSans-Regular.ttf
3676 ms
OpenSans-Semibold.ttf
7115 ms
days.ttf
1462 ms
3_0_90A0B0FF_708090FF_0_pageviews
318 ms
sale.png
674 ms
search_button.png
639 ms
rek1.gif
4722 ms
wm.png
738 ms
cards.png
2727 ms
acode.js
418 ms
watch.js
2 ms
539 ms
v2kNVZzzbA
268 ms
widget_ru_RU.js
267 ms
wm
402 ms
radio_brutto_150%D1%85150.jpg
4952 ms
allc.gif
463 ms
adlik
332 ms
1z.by accessibility score
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
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
<input type="image"> elements do not have [alt] text
Links do not have a discernible name
1z.by 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
Missing source maps for large first-party JavaScript
1z.by 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1z.by 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 1z.by 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.
1z.by
Open Graph description is not detected on the main page of 1 Z. 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: