7.7 sec in total
887 ms
6 sec
758 ms
Welcome to 103.by homepage info - get ready to check 103 best content for Russia right away, or after learning these important things about 103.by
Сервис поиска врачей и медицинских центров в Минске на 103.by - онлайн-консультации, цены, отзывы пациентов, удобная запись на прием.
Visit 103.byWe analyzed 103.by page load time and found that the first response time was 887 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
103.by performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value5.1 s
25/100
25%
Value10.4 s
8/100
10%
Value3,100 ms
2/100
30%
Value0
100/100
15%
Value16.1 s
6/100
10%
887 ms
782 ms
462 ms
946 ms
22 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original 103.by, 44% (40 requests) were made to Static.103.by and 10% (9 requests) were made to Mh8.adriver.ru. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Static.103.by.
Page size can be reduced by 570.7 kB (14%)
4.0 MB
3.4 MB
In fact, the total size of 103.by main page is 4.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. 40% of websites need less resources to load. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 313.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 147.2 kB, which is 41% 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 313.7 kB or 88% of the original size.
Potential reduce by 44.5 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. 103 images are well optimized though.
Potential reduce by 68.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 68.0 kB or 53% of the original size.
Potential reduce by 144.5 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. 103.by needs all CSS files to be minified and compressed as it can save up to 144.5 kB or 73% of the original size.
Number of requests can be reduced by 32 (40%)
81
49
The browser has sent 81 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 103. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and as a result speed up the page load time.
www.103.by
887 ms
all.css
782 ms
global.js
462 ms
all.js
946 ms
analytics.js
22 ms
watch.js
184 ms
acode.js
1707 ms
08193234dba6cdc630f42c3b4d681d6f.png
679 ms
a4c28eeeaeb516cf3f88809e1badfdae.jpg
680 ms
232811233df0c77d790dc143fab93c18.jpg
824 ms
b038c2dd7e6e03e55f2b309436f626ce.JPG
977 ms
896dacffc6941870ad7ca588b640b99a.jpg
612 ms
45c8e7cdd2b434f10a3eede5e76b95fb.jpg
776 ms
b1eebc39287d64fabd02d96f9af68bda.jpg
1089 ms
caefe18f12bf36d8b8d938bb48f58f37.jpg
841 ms
7dc3cba877d571e49528f4de16170cef.jpg
845 ms
6a2465a3ed2efe24d58d0f2c0231652c.jpg
936 ms
a12fd03fc45f37ea099f8eb541e9cd0c.jpg
983 ms
f478096a79d1cf11737575ee66c5898b.jpg
1000 ms
c9a7486830ff877ef9670bd8c427023e.jpg
1001 ms
57e1bc4cccc5d20c7844acac3791de5e.png
1256 ms
b4d33be2736d57b912e533cabda10d0c.png
1500 ms
e192784a4c0231aa102a95185d92ba46.png
1501 ms
9df61a58aa29d09d91c928bcc0819cc1.png
1498 ms
c1d740e9751003c9bc845511ef2e851e.png
1501 ms
2d8595e391881b431508b202053a235c.png
1571 ms
a8ff923752ab05f2303dae2f64b84528.png
1580 ms
9b38f32ba3b51155d53b6bcb29d63c6d.jpg
1500 ms
1e6510269860298327354b9fce79d636.jpg
1614 ms
5bb12192da727abf613775f6263cd1ce.jpg
1623 ms
5c820bc06b5cab6943accc5d44334a03.jpg
1642 ms
4cb07a23875ce163bd3324a080fae9d5.jpg
1647 ms
6979cb0e5712dcf5cbe06955efd41d72.jpg
1728 ms
gemius.js
1737 ms
autoUpdate.adriver.js
623 ms
gtm.js
65 ms
collect
13 ms
RobotoLight.woff
1722 ms
qDUaAaId5ga4rR6q5gBIYLzTkYrTRjcL7UTMC40UzBpNbMwLTSzMGs1CzAfD1RUiG+eRFRAAAAAAABVJLr9QAA
2 ms
RobotoMedium.ttf
1895 ms
RobotoBold.woff
1749 ms
suggest-loader.gif
1752 ms
collect
72 ms
1a9d0efa30bfddaa46ed3f3bda10260d.png
2298 ms
e117bfb7824914c3a3e53a8cbdfd3796.png
2306 ms
599641ff9670ebda1c97bd51fd72f5ee.jpg
2174 ms
208b74932288737bc86117abde907cda.jpg
2040 ms
conversion_async.js
30 ms
ga-audiences
58 ms
54 ms
watch.js
607 ms
18 ms
722 ms
937 ms
676 ms
688 ms
698 ms
721 ms
93fd2f3653935005b190d811c03cfe6b.jpg
1535 ms
platform-logo.svg
1506 ms
old.adriver.js
320 ms
advert.gif
90 ms
checkFlash.adriver.js
319 ms
functions.adriver.js
547 ms
1
92 ms
merle.cgi
367 ms
merle.cgi
368 ms
merle.cgi
368 ms
merle.cgi
370 ms
merle.cgi
372 ms
merle.cgi
370 ms
rexdot.gif
126 ms
script.js
393 ms
script.js
410 ms
script.js
387 ms
script.js
415 ms
script.js
410 ms
script.js
419 ms
pixel.adriver.js
270 ms
makeFlash.adriver.js
270 ms
checkFB.adriver.js
277 ms
makeImage.adriver.js
271 ms
clickCoord.adriver.js
279 ms
checkOver.adriver.js
307 ms
html.adriver.js
547 ms
Optiki.jpg
562 ms
event.adriver.js
234 ms
240.png
390 ms
more_life_1920_90.png
536 ms
adlik
191 ms
103.by 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
[role] values are not valid
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
103.by best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
103.by SEO score
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 103.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 103.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.
103.by
Open Graph description is not detected on the main page of 103. 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: