6.9 sec in total
1.7 sec
4.6 sec
569 ms
Welcome to tr.ru homepage info - get ready to check TR best content for Russia right away, or after learning these important things about tr.ru
Ежедневное интернет-издание о транспорте в России и в мире. Общественный транспорт, транспортные системы городов и регионов, инфраструктура для пассажиров и водителей. Новости, аналитика, обсуждения
Visit tr.ruWe analyzed Tr.ru page load time and found that the first response time was 1.7 sec and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
tr.ru performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value11.4 s
0/100
25%
Value9.3 s
13/100
10%
Value3,360 ms
2/100
30%
Value0.301
39/100
15%
Value15.4 s
7/100
10%
1700 ms
207 ms
209 ms
211 ms
209 ms
Our browser made a total of 140 requests to load all elements on the main page. We found that 76% of them (107 requests) were addressed to the original Tr.ru, 5% (7 requests) were made to Pagead2.googlesyndication.com and 4% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Tr.ru.
Page size can be reduced by 1.4 MB (50%)
2.7 MB
1.4 MB
In fact, the total size of Tr.ru main page is 2.7 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.0 MB which makes up the majority of the site volume.
Potential reduce by 153.8 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 153.8 kB or 85% of the original size.
Potential reduce by 57.9 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. TR images are well optimized though.
Potential reduce by 541.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 541.5 kB or 65% of the original size.
Potential reduce by 609.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. Tr.ru needs all CSS files to be minified and compressed as it can save up to 609.5 kB or 85% of the original size.
Number of requests can be reduced by 66 (52%)
127
61
The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
tr.ru
1700 ms
system.base.css
207 ms
system.messages.css
209 ms
field.css
211 ms
node.css
209 ms
search.css
212 ms
user.css
213 ms
youtube.css
313 ms
views.css
311 ms
ckeditor.css
317 ms
colorbox_style.css
312 ms
ctools.css
316 ms
flexslider_img.css
320 ms
flexslider.css
420 ms
bbpress.css
421 ms
style.css
420 ms
symple_shortcodes_styles.css
426 ms
font-awesome.min.css
423 ms
thumbs-rating.css
428 ms
checkbox.css
522 ms
form.css
522 ms
style_awesome.css
534 ms
swipebox.css
532 ms
style_trru.css
658 ms
style_tab.css
541 ms
style480_mobile.css
625 ms
style320_mobile.css
626 ms
custom_css.css
665 ms
clear-sans.css
667 ms
css
42 ms
default.css
665 ms
update.css
728 ms
jquery.min.js
872 ms
jquery.once.js
759 ms
drupal.js
761 ms
ru_L2PKTujJCGXAngi1JeAN8qXvHfz_SuDSkm_ClulKP1s.js
763 ms
jquery.colorbox-min.js
765 ms
adsbygoogle.js
25 ms
share.js
46 ms
colorbox.js
740 ms
colorbox_style.js
666 ms
jquery.flexslider-min.js
700 ms
jquery-migrate.min.js
696 ms
general.js
697 ms
flexslider.load.js
739 ms
editor.js
798 ms
menu.navigation.js
724 ms
jquery.swipebox.js
723 ms
swipebox-ios-orientationchange-fix.js
724 ms
customs.js
720 ms
jquery.ui.core.min.js
817 ms
jquery.ui.widget.min.js
831 ms
update.js
730 ms
logotr.png
329 ms
logosm.png
331 ms
0_161775_a1bab21c_orig.jpg
365 ms
0_9df9b_d4cc347d_orig.jpg
367 ms
139d430c548cb5628d7516ea0baec983.jpg
384 ms
407a6a0b44c6b74a62438b8a469909aa.jpg
438 ms
a4f55e1kjsg.jpg
431 ms
trolley1_dmit.jpg
364 ms
kuntsevo1.jpg
436 ms
trollvozd.jpg
440 ms
0_161775_a1bab21c_orig.jpg
447 ms
4f5af4d979e30c979db32c949386597c_745x460.jpg
489 ms
dsc_0936.jpg
539 ms
139d430c548cb5628d7516ea0baec983.jpg
554 ms
a4f55e1kjsg.jpg
567 ms
0_1553cf_c7cb5592_xl.jpg
564 ms
45519_0.jpg
613 ms
0_799ca_29d11c7a_orig_745x4601.jpg
652 ms
0_9df9b_d4cc347d_orig.jpg
674 ms
407a6a0b44c6b74a62438b8a469909aa.jpg
673 ms
27750.jpg
680 ms
simfyalta1.jpg
681 ms
cj4s18rodvm.jpg
680 ms
salaryevo201604.jpg
761 ms
liteiny1.jpg
787 ms
angarsk10.jpg
786 ms
watch.js
2 ms
analytics.js
28 ms
vkontakte.png
787 ms
ca-pub-6253434476909231.js
190 ms
zrt_lookup.html
157 ms
show_ads_impl.js
92 ms
collect
30 ms
facebook.png
697 ms
ClearSans-Regular.woff
1117 ms
dazS1PrQQuCxC3iOAJFEJVRROVH9Vvc8xHnAGvvgPQc.woff
84 ms
y7lebkjgREBJK96VQi37ZmOb2gHztoQeulij-1lvl-8.woff
112 ms
context.js
252 ms
ClearSans-Medium.woff
1123 ms
ClearSans-Light.woff
1056 ms
ClearSans-Thin.woff
1180 ms
ClearSans-Bold.woff
1122 ms
ads
332 ms
osd.js
133 ms
ClearSans-Italic.woff
987 ms
ClearSans-MediumItalic.woff
1784 ms
ads
246 ms
ClearSans-BoldItalic.woff
1204 ms
twitter.png
1382 ms
rss.png
1012 ms
ads
296 ms
0_9df9b_d4cc347d_orig.jpg
991 ms
139d430c548cb5628d7516ea0baec983.jpg
1343 ms
context_static_r1082.js
393 ms
407a6a0b44c6b74a62438b8a469909aa.jpg
1340 ms
a4f55e1kjsg.jpg
1327 ms
0_1553cf_c7cb5592_xl.jpg
1305 ms
45519_0.jpg
1384 ms
uv6qocbgrhi.jpg
1381 ms
0_161775_a1bab21c_orig.jpg
1378 ms
0_1553cf_c7cb5592_xl.jpg
1370 ms
4f5af4d979e30c979db32c949386597c_745x460.jpg
1349 ms
m_js_controller.js
45 ms
abg.js
70 ms
8031343792858411736
47 ms
googlelogo_color_112x36dp.png
95 ms
0_799ca_29d11c7a_orig_745x4601.jpg
1382 ms
0_9941_16c814b3_xl.jpg
1366 ms
liteiny1.jpg
1357 ms
s
61 ms
ywvqpbdyjsa.jpg
1324 ms
x_button_blue2.svg
40 ms
0_9df9b_d4cc347d_orig.jpg
1343 ms
redir.html
127 ms
9406744681143802217
37 ms
139d430c548cb5628d7516ea0baec983.jpg
1377 ms
Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js
18 ms
407a6a0b44c6b74a62438b8a469909aa.jpg
1373 ms
a4f55e1kjsg.jpg
1372 ms
0_161775_a1bab21c_orig.jpg
1367 ms
iframe.html
107 ms
152144
206 ms
watch.js
5 ms
x80
288 ms
x80
414 ms
activeview
15 ms
activeview
28 ms
tr.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
tr.ru 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
tr.ru 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 Tr.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 Tr.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.
tr.ru
Open Graph description is not detected on the main page of TR. 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: