6.7 sec in total
725 ms
5.4 sec
573 ms
Welcome to ex-press.by homepage info - get ready to check EX PRESS best content for Sweden right away, or after learning these important things about ex-press.by
Самая читаемая интернет-газета в Борисове и Жодино. Обзор важнейших новостей и событий региона сегодня
Visit ex-press.byWe analyzed Ex-press.by page load time and found that the first response time was 725 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
ex-press.by performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value21.4 s
0/100
25%
Value14.2 s
1/100
10%
Value2,200 ms
6/100
30%
Value0.027
100/100
15%
Value35.4 s
0/100
10%
725 ms
246 ms
244 ms
244 ms
245 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that 58% of them (69 requests) were addressed to the original Ex-press.by, 4% (5 requests) were made to St.mycdn.me and 4% (5 requests) were made to Avatars-fast.yandex.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Ex-press.by.
Page size can be reduced by 433.1 kB (60%)
724.4 kB
291.2 kB
In fact, the total size of Ex-press.by main page is 724.4 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. 40% of websites need less resources to load. HTML takes 288.9 kB which makes up the majority of the site volume.
Potential reduce by 253.3 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 57.4 kB, which is 20% 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 253.3 kB or 88% of the original size.
Potential reduce by 22.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, EX PRESS needs image optimization as it can save up to 22.6 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 130.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 130.0 kB or 61% of the original size.
Potential reduce by 27.2 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. Ex-press.by needs all CSS files to be minified and compressed as it can save up to 27.2 kB or 85% of the original size.
Number of requests can be reduced by 49 (42%)
117
68
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EX PRESS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
ex-press.by
725 ms
index.css
246 ms
sliderkit.css
244 ms
tag.css
244 ms
typography.css
245 ms
styles.css
246 ms
style.css
358 ms
jquery.min.js
44 ms
jquery.bxSlider.min.js
484 ms
openapi.js
379 ms
xgemius.js
487 ms
asm2.js
539 ms
waypoints.min.js
487 ms
waypoints-sticky.min.js
488 ms
jquery.tabslet.min.js
487 ms
initializers.js
594 ms
zp.js
648 ms
watch.js
1 ms
zp.js
646 ms
require.js
140 ms
logo.gif
241 ms
d1.gif
243 ms
gas.gif
274 ms
wea.gif
243 ms
kurs.gif
243 ms
4.gif
297 ms
4.gif
482 ms
10.gif
484 ms
10.gif
483 ms
line_m_b2.gif
485 ms
line_m_b3.gif
513 ms
line_m_b.gif
550 ms
search.gif
739 ms
mobile.gif
739 ms
skype.gif
742 ms
rss.gif
740 ms
115110.jpg
1256 ms
photo.png
789 ms
comm.gif
985 ms
video.png
987 ms
d2.gif
988 ms
115129.jpg
1225 ms
image.php
1033 ms
image.php
1232 ms
image.php
1228 ms
blank.gif
1229 ms
114987.jpg
1654 ms
image.php
1523 ms
image.php
1531 ms
image.php
1527 ms
image.php
1527 ms
arrow.gif
1526 ms
image.php
1779 ms
image.php
1777 ms
image.php
1773 ms
blankr.gif
1727 ms
require-apsm.js
142 ms
image.php
1542 ms
image.php
1676 ms
image.php
1792 ms
image.php
1793 ms
image.php
1766 ms
apsm.js
452 ms
image.php
1747 ms
rexdot.gif
129 ms
ad.js
124 ms
image.php
1562 ms
image.php
1737 ms
image.php
1812 ms
image.php
1813 ms
sarg=5707D79D45BFFC50
381 ms
blr.png
1786 ms
usd.png
1749 ms
eur.png
1560 ms
rur.png
1662 ms
pln.png
1783 ms
czk.png
1782 ms
uah.png
1735 ms
ad.js
124 ms
line_m.gif
1539 ms
line_ma.gif
1548 ms
line1.gif
1656 ms
sarg=5707D79D45BFFC50
128 ms
context.js
278 ms
context_static_r1084.js
363 ms
124727
220 ms
x90
263 ms
x90
243 ms
x90
245 ms
aci.js
187 ms
connect.js
670 ms
reklamamgm.ru
281 ms
x90
252 ms
x80
261 ms
wwwfly.ru
408 ms
analytics.js
41 ms
impression.html
312 ms
extra.js
315 ms
collect
14 ms
94 ms
184 ms
273 ms
match
179 ms
dk
168 ms
widget.a86e7c8a.css
699 ms
image
778 ms
image
807 ms
image
819 ms
image
860 ms
image
795 ms
image
860 ms
image
859 ms
image
818 ms
image
850 ms
support.html
159 ms
ic_odkl_m.png
170 ms
add-or.png
326 ms
user-f.png
464 ms
ic_odkl.png
468 ms
6_zIAoZfXQG40000gK6EldbzS0M5btCUkltn6XIOVyqd2P6w5scE2PDKhlNZGAf6mw-G0R2mHtsb1B41mV__________3te7=6Z_ynfK2cm5kGxS2CucHYW6O__________yFYho__uq1lRuNjz41fQAS-GE8iwELOGEyeq0o0wOrdQDQAGYFiLV2cmEVkP51KmAP3A2KpbApdJKRhvsvKRIGsnhPdITPsf1C7QUEIAYmG5bp1q6n0RAWKW02kQDQAGZ5Zm_DlR__ZG7EkIP1E0BI__________yFq___________3y80trHz4m00=30ry59K2cm5kGxS2Cecbrgg2c0MAk3QFrmIzkEXqi0IbgOcu1uYpDX2y1gQ029sZvwKDZx-bATS5dxxB5R0AcHwWblejhvRwBTcGr32KbImAfu5_gA5GHZr1iG6oe5800hcZvwKDnOyFpRSsZzS4phAJxOe6ql__________3zF__________m_20DzKUH40=pJh26Qa0bGAR0Mv3jmA9chiUc0MAiSfBRWEzkPtqbmEbeKDL1eYmPuPH0xoYKBK4fZITejS64u-_fIdN1P--onMm2faUe9A2Pg-G0bFPaDrjb9nM2AUBJwYXfKGDGR41ig1I00AvejS64yMF3ysmoajk0ywq-HhT1DB__________m_J__________yFmW3VL7qH
116 ms
ex-press.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.
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
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.
ex-press.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
ex-press.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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ex-press.by can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ex-press.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.
ex-press.by
Open Graph description is not detected on the main page of EX PRESS. 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: