7.1 sec in total
274 ms
6.1 sec
696 ms
Welcome to slon.ru homepage info - get ready to check Slon best content for Russia right away, or after learning these important things about slon.ru
Republic. Платформа профессиональной журналистики. Это сообщество редакторов и авторов, рассказывающих о самых важных событиях в России и мире, а также об экономике, науке, здоровье, истории и многом ...
Visit slon.ruWe analyzed Slon.ru page load time and found that the first response time was 274 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.
slon.ru performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value10.9 s
0/100
25%
Value11.0 s
6/100
10%
Value6,680 ms
0/100
30%
Value0.336
33/100
15%
Value28.0 s
0/100
10%
274 ms
429 ms
1472 ms
55 ms
453 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Slon.ru, 73% (74 requests) were made to Republic.ru and 6% (6 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Republic.ru.
Page size can be reduced by 425.9 kB (22%)
1.9 MB
1.5 MB
In fact, the total size of Slon.ru main page is 1.9 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. 65% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 383.9 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 383.9 kB or 83% of the original size.
Potential reduce by 37.8 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. Slon images are well optimized though.
Potential reduce by 4.2 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 24 (26%)
92
68
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Slon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
slon.ru
274 ms
share-cookie
429 ms
republic.ru
1472 ms
gtm.js
55 ms
symbol-defs.svg
453 ms
c294bb4ba1b864cbc49f8d350b0710f6.jpeg
738 ms
05b2d8f3bf6eca7677dbc88273e38ada.jpeg
484 ms
7faf4a24adfbcd2c35f624aef721146c.jpeg
736 ms
f7e9bb78eb9ac933e375783709c20e9e.jpeg
737 ms
31455c7b07721e32cb02c5c9842001ee.png
740 ms
cf0a84296e6aa3363e54c679dffe0698.png
738 ms
ab63a4b05437bd5c7bb2a56158d98afd.png
744 ms
33899c2aa8c5f2558aea96e48a24778c.jpeg
739 ms
d8342587b9e7fb8e85d7115a3bb9b8e5.jpeg
740 ms
2f8ee489ce68b53bbb9969d0c6754f02.jpeg
741 ms
6c8f60654a3ec1180c18.js
664 ms
5c409c22303090901eec.js
692 ms
f0ed667f559177ff6acb.js
784 ms
6bfa08b85bf73036c3d1.js
892 ms
b3861612e82cb84789e9.js
980 ms
eda71c5131df7344a4eff65e1d7a2547.jpeg
696 ms
4bcdcb54e1dddb2746ba532c208002be.jpeg
729 ms
2d0de9db30c08897dd130d87995dfb08.jpeg
991 ms
7fcc577016d1dc2835c624971384b208.jpeg
799 ms
0e26d9a01c40c8060111d09c860416fd.png
992 ms
9de7ffbc7e280f49ffa4c96cac9f65b8.jpeg
886 ms
d4191b7750ebb609907051ac3da7a068.jpeg
989 ms
5ed0fde237619dee931845f0cef72503.jpeg
995 ms
a77ee804f5fd421dbfcdaa718002eb62.jpeg
997 ms
aa5e46be329083f6eb767598e2638148.jpeg
1005 ms
26f0888757bf16b67a69259d031688b5.jpeg
1004 ms
07b92156282fb4cc75955affc171667b.jpeg
1043 ms
d7badf323f3fc32d2455ddd92da1667e.jpeg
1084 ms
4bfa8e3612cb146d88042386a5b6e82d.jpeg
1104 ms
027386c8763d763c7e2aabc3367f3e3b.jpeg
1104 ms
3891b8318defbb5ce82fd0bc670e94a4.jpeg
1119 ms
9111f2343c1213f4fd3938bf5ece5b76.jpeg
1120 ms
5917361658b26c4f8173f7737702bf8f.jpeg
1161 ms
a26ccd3dcb95efd15d02949ad517fb32.jpeg
1226 ms
fb427eb.woff
1326 ms
bat.js
63 ms
analytics.js
56 ms
fbevents.js
82 ms
code.js
1001 ms
tag.js
77 ms
collect
179 ms
collect
230 ms
js
75 ms
collect
47 ms
advert.gif
741 ms
b235727.woff
808 ms
b93746d.woff
908 ms
3e6b403.woff
579 ms
bbba216.woff
762 ms
c3d0889.woff
677 ms
befd5000621322c9711bfc94e9d6f0f9.jpeg
677 ms
58c4fc2a3258c5e45f3a72c02558dcec.jpeg
676 ms
22a4192e126f8ce4a21480de49145b59.jpeg
757 ms
00a3f2ddafd4282fa413ce1a34b127ee.jpeg
757 ms
96c6c562c024f08e1e41cd99a2dd75f6.jpeg
809 ms
17ccd9ec2110e20fd2df79b5a2741ef5.png
808 ms
822948ccefd5cb586f6d87b8b9de3108.png
802 ms
bb283ba82ac4f416b33385dc8833eb2b.jpeg
831 ms
6e42ab6d2224f2b3e0aa96f2bb5a7838.png
812 ms
3980235e762599b6edfc97abdd75b8cd.jpeg
788 ms
a86255a54bb6d8556e61a08ccb579dab.jpeg
730 ms
bb16c25a87459099e7b860ad466f18b3.png
730 ms
openapi.a2ed73393cad04481c1dfb3f7794921f.js
253 ms
144832d6aa658631eef88eb271ab9441.jpeg
680 ms
collect
72 ms
1d825a249cd9470acbf683b53edd0c79.jpeg
634 ms
14d8820fb7922632e7fb012fdc220ed3.png
631 ms
bdef40fe020d7016acc265325fd8fd1f.jpeg
636 ms
c31275046b7362420b6434ee263ac0f3.jpeg
650 ms
1
423 ms
5ccf2d689961571a4c86a962cc4dbd96.jpeg
639 ms
edde380f470ed17125bbca65d71f5d18.png
690 ms
842cbea7f6a07e2720050e728db53222.jpeg
717 ms
2828c71a30603192934487a73b07840d.jpeg
719 ms
d4c1dd167da856981017d3d1a6044162.jpeg
724 ms
be8c7a22d0a10414f13ddf92e39d56c7.jpeg
692 ms
rtrg
164 ms
30f21a3d8be38448ca4789a5ada04011.jpeg
674 ms
sync-loader.js
1110 ms
counter
228 ms
dyn-goal-config.js
745 ms
91e69b7fe1723082b0626ec915059e48.jpeg
701 ms
e04c85535d2a2f83424a7cae235b6324.jpeg
709 ms
d117355263bb4e6ae932a8770c191d46.jpeg
706 ms
9a799442eb523c3fe8353de073e9dffd.jpeg
713 ms
4dac87a5efa8356dafdfac7ee16ae0a6.jpeg
674 ms
1732803685b99a2711175193c035f46c.png
653 ms
77a504620506087f651c041005bfc6ea.jpeg
696 ms
google-news.png
648 ms
1
148 ms
collect
49 ms
sync_cookie_image_decide
132 ms
tracker
140 ms
collect
118 ms
counter
126 ms
rtrg
137 ms
slon.ru 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
Image elements do not have [alt] attributes
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.
slon.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
slon.ru SEO score
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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Slon.ru 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 Slon.ru 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.
slon.ru
Open Graph data is detected on the main page of Slon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: