4.8 sec in total
371 ms
3.8 sec
587 ms
Visit kommersant.fm now to see the best up-to-date Kommersant content and also check out these interesting facts you probably never knew about kommersant.fm
Радио «Ъ FM»: Актуальные новости, объективный анализ и эксклюзивные комментарии о важнейших событиях и трендах
Visit kommersant.fmWe analyzed Kommersant.fm page load time and found that the first response time was 371 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
kommersant.fm performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value15.2 s
0/100
25%
Value10.4 s
8/100
10%
Value2,340 ms
5/100
30%
Value0.044
99/100
15%
Value14.1 s
9/100
10%
371 ms
823 ms
965 ms
1104 ms
1226 ms
Our browser made a total of 28 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Kommersant.fm, 14% (4 requests) were made to Top-fwz1.mail.ru and 4% (1 request) were made to Kommersant.ru. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Iy.kommersant.ru.
Page size can be reduced by 348.1 kB (62%)
559.5 kB
211.5 kB
In fact, the total size of Kommersant.fm main page is 559.5 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. HTML takes 359.5 kB which makes up the majority of the site volume.
Potential reduce by 321.5 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 45.3 kB, which is 13% 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 321.5 kB or 89% of the original size.
Potential reduce by 0 B
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. Kommersant images are well optimized though.
Potential reduce by 19.8 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 19.8 kB or 12% of the original size.
Potential reduce by 6.7 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. Kommersant.fm needs all CSS files to be minified and compressed as it can save up to 6.7 kB or 23% of the original size.
Number of requests can be reduced by 13 (52%)
25
12
The browser has sent 25 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kommersant. 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 from 4 to 1 for CSS and as a result speed up the page load time.
fm
371 ms
kom2021.commonCss.css
823 ms
kom2021.rubric.css
965 ms
kom2021.fm.css
1104 ms
kom2021.pushPopup.js
1226 ms
kom2021.commonJS.js
1261 ms
kom2021.pollJS.js
1232 ms
kom2021.lentaVue.js
1659 ms
context.js
998 ms
js
64 ms
kom2021.archive.js
1235 ms
kom2021.commonAsyncJS.js
1641 ms
logo;kommersant
584 ms
adv.gif
136 ms
rusfond_logo.png
139 ms
rustore.svg
144 ms
huawei.svg
137 ms
new-logo_FM_short.svg
279 ms
code.js
860 ms
ajax-loader.gif
798 ms
noto-sans.css
135 ms
NotoSans-SemiCondensed.woff
303 ms
NotoSans-SemiCondensedSemiBold.woff
291 ms
counter2
141 ms
281204989
143 ms
sync-loader.js
765 ms
counter
141 ms
dyn-goal-config.js
141 ms
kommersant.fm 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
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
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
kommersant.fm 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
kommersant.fm 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
RU
RU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kommersant.fm 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 Kommersant.fm 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.
kommersant.fm
Open Graph data is detected on the main page of Kommersant. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: