29.7 sec in total
2.2 sec
26.9 sec
650 ms
Click here to check amazing 124 content for Belarus. Otherwise, check out these important facts you probably never knew about 124.by
Профессиональные услуги колл-центра, для обеспечения надежной связи с клиентами и эффективной поддержки бизнеса - Аутсорсинговый call-центр 124 в Беларуси (контактный центр в Минске)
Visit 124.byWe analyzed 124.by page load time and found that the first response time was 2.2 sec and then it took 27.5 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.
124.by performance score
name
value
score
weighting
Value9.6 s
0/100
10%
Value14.4 s
0/100
25%
Value18.1 s
0/100
10%
Value2,000 ms
8/100
30%
Value0.003
100/100
15%
Value21.6 s
1/100
10%
2156 ms
295 ms
296 ms
418 ms
299 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 85% of them (131 requests) were addressed to the original 124.by, 5% (8 requests) were made to Media.reformal.ru and 2% (3 requests) were made to Reformal.ru. The less responsive or slowest element that took the longest time to load (10.8 sec) belongs to the original domain 124.by.
Page size can be reduced by 1.4 MB (31%)
4.5 MB
3.1 MB
In fact, the total size of 124.by main page is 4.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. 55% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.
Potential reduce by 86.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 86.2 kB or 81% of the original size.
Potential reduce by 256.1 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. 124 images are well optimized though.
Potential reduce by 573.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 573.5 kB or 69% of the original size.
Potential reduce by 470.8 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. 124.by needs all CSS files to be minified and compressed as it can save up to 470.8 kB or 88% of the original size.
Number of requests can be reduced by 60 (40%)
149
89
The browser has sent 149 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 124. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
{{url}}
{{time}} ms
124.by 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
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
124.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
124.by 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
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 124.by 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 124.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.
{{og_description}}
124.by
Open Graph description is not detected on the main page of 124. 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: