11.2 sec in total
2.2 sec
8.4 sec
636 ms
Welcome to tomskpress.ru homepage info - get ready to check Tomskpress best content for Russia right away, or after learning these important things about tomskpress.ru
Актуальная картина дня новостей Томска за сегодня, неделю, год. Все новости Томска и Томской области на РИА Томскпресс
Visit tomskpress.ruWe analyzed Tomskpress.ru page load time and found that the first response time was 2.2 sec and then it took 9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
tomskpress.ru performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value1.2 s
100/100
25%
Value2.0 s
99/100
10%
Value0 ms
100/100
30%
Value0.152
75/100
15%
Value1.2 s
100/100
10%
2217 ms
720 ms
496 ms
746 ms
932 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 55% of them (60 requests) were addressed to the original Tomskpress.ru, 15% (16 requests) were made to Vk.com and 5% (5 requests) were made to Openstat.net. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Tomskpress.ru.
Page size can be reduced by 688.7 kB (46%)
1.5 MB
807.2 kB
In fact, the total size of Tomskpress.ru main page is 1.5 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. 50% of websites need less resources to load. Images take 664.8 kB which makes up the majority of the site volume.
Potential reduce by 118.1 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 118.1 kB or 82% of the original size.
Potential reduce by 51.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. Tomskpress images are well optimized though.
Potential reduce by 432.4 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 432.4 kB or 74% of the original size.
Potential reduce by 86.4 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. Tomskpress.ru needs all CSS files to be minified and compressed as it can save up to 86.4 kB or 83% of the original size.
Number of requests can be reduced by 36 (35%)
104
68
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tomskpress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
tomskpress.ru
2217 ms
jquery-1.5.2.min.js
720 ms
scrollable.js
496 ms
JsHttpRequest.js
746 ms
jquery.cookie.js
932 ms
swfobject.js
953 ms
jnotifier.jquery.js
1172 ms
jnotifier.css
1184 ms
pack.php
1404 ms
jquery-ui-1.7.3.custom.min.js
1878 ms
floating_panel.jquery.js
504 ms
jquery.autocomplete.js
509 ms
jquery-ui-1.7.3.custom.css
1458 ms
template.css
1459 ms
openapi.js
579 ms
zp.js
2792 ms
mynews.php
1481 ms
top100.jcn
633 ms
watch.js
1 ms
1d5eaaa5fb8d22141783eb93c52ef7d9.png
306 ms
rss.gif
248 ms
vk.gif
251 ms
tw.gif
250 ms
ya.gif
259 ms
tomsk.png
254 ms
doSearch.gif
256 ms
bdd7272c59ac05762ea34fb9fa9d692b.jpg
1331 ms
890bfc959f814b5aa9ef9c4c392327b8.jpg
2479 ms
57d3d0f10473df8ba192e4a9663a5f93.jpg
1509 ms
154445af598cbb037a4f31cccdafffb2.jpg
1520 ms
8a25a8569240949b673975c385371f0c.jpg
494 ms
a39a1c7b0230be24d80f7847f2cf119a.jpg
489 ms
817875ddd57699fe1d460289984299f0.jpeg
1017 ms
4504c63caf1ad17a4dead1f226fed5ba.jpg
726 ms
10cdade259674a8c73fe9ea97d7430a1.jpg
1786 ms
fd03e104c2ef87fb4f2875836d57d207.jpg
1254 ms
1204bd50b3a8d538f1c09b34fc6719df.jpg
1508 ms
d9103874509ca2c2ca9af1e9cb90a127.jpg
1568 ms
1ee7578e5a597f4a071b785d987efd0a.jpg
1774 ms
dc1fa12401419c3ac417cd9ffaebeb71.jpg
1783 ms
35b483859c74dc486ae220d6d2137802.jpg
1793 ms
dcf44665d8aa728a2bb2f97449411ce2.jpg
1818 ms
mini_42fc80944a388823c7fc8eaf9ddd7517.jpg
2012 ms
mini_1666b410bef65c967b5dc0bb173eb862.jpg
3057 ms
mini_163eb92d0808c8e22dd22b86824b89c1.jpg
3026 ms
mini_82c3e42d02f5ba77386c7e9bba0a4c96.jpg
2018 ms
mini_b43b4d3918112f8e96851c1d22a4dbf9.JPG
2086 ms
mini_1d16c4439b9599f71292d5ad4eda32b9.jpg
2238 ms
mini_84e3bb97a25816f840c55e5707100374.jpg
2273 ms
mini_b969ff27462b78131138589c76ea5b67.jpg
2296 ms
16330934cfee931812eddc7451d29b75.gif
1516 ms
f-photo.gif
2474 ms
f-video.gif
2481 ms
f-like.gif
2500 ms
info_line_bg.gif
2704 ms
info_line_bottom_bg.jpg
2707 ms
act_bg.png
2710 ms
context.js
329 ms
act_bgtop.png
2537 ms
bgtop.png
2757 ms
big_line.png
2760 ms
left_mod_th.jpg
4222 ms
oreder_box_bg.gif
3899 ms
context_static_r1084.js
466 ms
111570
199 ms
y150
328 ms
l_mod_th.jpg
2077 ms
circus_str.gif
2080 ms
mini_mod_th.jpg
2102 ms
tomsk.jpg
3142 ms
upload.gif
151 ms
widget_community.php
346 ms
bottom_map_th.jpg
2233 ms
widget_recommended.php
321 ms
cnt.js
366 ms
hit
364 ms
top100.scn
182 ms
impression.html
387 ms
extra.js
392 ms
bottom_text.gif
2168 ms
loader_nav19239_3.js
187 ms
lite.css
173 ms
lite.js
510 ms
lang3_0.js
348 ms
widget_recommended.css
347 ms
xdm.js
348 ms
al_recommended.js
351 ms
widget_community.css
356 ms
al_community.js
504 ms
hit
203 ms
2230669.js
200 ms
digits
214 ms
cnt
374 ms
counter
392 ms
widget_logo.gif
216 ms
e_2b0dacf2.jpg
450 ms
00L8vhALLKM.jpg
468 ms
2rwlVSGWMFY.jpg
452 ms
XrHR9-eTQo4.jpg
452 ms
e_4abf6915.jpg
453 ms
VGL8fTCFidw.jpg
1350 ms
v6Wv5vtgado.jpg
463 ms
w_logo.png
1420 ms
camera_50.png
205 ms
f.gif
169 ms
support.html
235 ms
pixel
127 ms
VeZiCnc8wje40000gK6EiA1_S0M5aZqRkliK4KX9KqFY0P6mclv529DKhlg2GcXix3AH0R2miWCe1B41mV__________3te7=d6aXFAa0bGAR0Mv3jmA9b0m4cF__________3ugyl_-D0Rs-5xVH0QMYdFa3YBEZbM43lAD0CWEcDPsZMYa8ZxHlKe8EdxA_r6W6cGQWhZPR0REQ67Ald75lj92V9DcZ3Mm1sf2XTwU0fwYmG5bp1q6n0RAWqW02kQDQAGZ5Zm_DlR__ZG7EkIP1E0BI__________yFq___________3y80trHu5000
163 ms
pixel
56 ms
collect
163 ms
tomskpress.ru accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
tomskpress.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
tomskpress.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
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tomskpress.ru 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 Tomskpress.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.
tomskpress.ru
Open Graph description is not detected on the main page of Tomskpress. 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: