Tools & Wizards About Us
vtomske.ru screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

vtomske.ru

vtomske.ru — новости Томска, России и мира сегодня

Page Load Speed

5.3 sec in total

First Response

537 ms

Resources Loaded

4.6 sec

Page Rendered

146 ms

vtomske.ru screenshot

About Website

Welcome to vtomske.ru homepage info - get ready to check Vtomske best content for Russia right away, or after learning these important things about vtomske.ru

Актуальные новости Томска, России и мира. Фоторепортажи и видео. Аналитические материалы, мнения экспертов.

Visit vtomske.ru

Key Findings

We analyzed Vtomske.ru page load time and found that the first response time was 537 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

vtomske.ru performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value3,560 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.456

20/100

15%

TTI (Time to Interactive)

Value16.3 s

5/100

10%

Network Requests Diagram

vtomske.ru

537 ms

vtomske.ru

762 ms

styles.min.css

177 ms

vtomske.min.js

1320 ms

common.min.js

352 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 22% of them (14 requests) were addressed to the original Vtomske.ru, 14% (9 requests) were made to Dn1.vtomske.ru and 13% (8 requests) were made to St.vtomske.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source St.vtomske.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 79.9 kB (10%)

Content Size

835.0 kB

After Optimization

755.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vtomske.ru main page is 835.0 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. Javascripts take 628.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 35.3 kB

  • Original 47.8 kB
  • After minification 47.5 kB
  • After compression 12.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. 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 35.3 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 3.5 kB

  • Original 145.7 kB
  • After minification 142.2 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. Vtomske images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 40.2 kB

  • Original 628.7 kB
  • After minification 628.7 kB
  • After compression 588.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. This website has mostly compressed JavaScripts.

CSS Optimization

-7%

Potential reduce by 881 B

  • Original 12.8 kB
  • After minification 12.8 kB
  • After compression 11.9 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. Vtomske.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (43%)

Requests Now

56

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vtomske. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

vtomske.ru

vtomske.ru

537 ms

vtomske.ru

vtomske.ru

762 ms

styles.min.css

styles.min.css

177 ms

vtomske.min.js

vtomske.min.js

1320 ms

common.min.js

common.min.js

352 ms

context.js

context.js

990 ms

adsbygoogle.js

adsbygoogle.js

100 ms

radio.min.js

radio.min.js

526 ms

site-logo.svg

site-logo.svg

175 ms

fc692409ff69720915e36b48d1220ce6_mde342e6.jpg

fc692409ff69720915e36b48d1220ce6_mde342e6.jpg

1007 ms

logo;vtomske

logo;vtomske

521 ms

site-sign.svg

site-sign.svg

283 ms

z.gif

z.gif

283 ms

f58366ca22528acbf6611194340feec0_xsbf406e.jpg

f58366ca22528acbf6611194340feec0_xsbf406e.jpg

845 ms

23238b00950043b7beea92d63629754a_xsd4f2ed.jpg

23238b00950043b7beea92d63629754a_xsd4f2ed.jpg

866 ms

0816f5210aa9663c33534fc97b5d0101_xs5a0bd3.jpg

0816f5210aa9663c33534fc97b5d0101_xs5a0bd3.jpg

879 ms

ddc4366eeea0662434d1e812e586d0e2_xs987531.jpg

ddc4366eeea0662434d1e812e586d0e2_xs987531.jpg

900 ms

c7c706cec24c22dbc70d3e3053dd57c5_xs312df7.jpg

c7c706cec24c22dbc70d3e3053dd57c5_xs312df7.jpg

954 ms

9248a7a7d0a2a84f808e29f718789f14_xsfab89d.jpg

9248a7a7d0a2a84f808e29f718789f14_xsfab89d.jpg

1027 ms

93c262ef388cfa7fae422db749c397a9_xsf16db6.jpg

93c262ef388cfa7fae422db749c397a9_xsf16db6.jpg

1109 ms

631eb6349cdc69832ba591505dee321a_xs356b14.jpg

631eb6349cdc69832ba591505dee321a_xs356b14.jpg

1110 ms

play-button-black.png

play-button-black.png

172 ms

logo-sign.svg

logo-sign.svg

355 ms

show_ads_impl.js

show_ads_impl.js

280 ms

hit

hit

312 ms

hit;vtomske

hit;vtomske

492 ms

site-icons.png

site-icons.png

899 ms

head-underline.png

head-underline.png

329 ms

site-icons.png

site-icons.png

329 ms

job-underline.png

job-underline.png

468 ms

horo-bg.png

horo-bg.png

507 ms

radio-bg.png

radio-bg.png

510 ms

PT_Sans-Caption-Regular.woff

PT_Sans-Caption-Regular.woff

793 ms

PT_Sans-Caption-Bold.woff

PT_Sans-Caption-Bold.woff

1051 ms

PT_Sans-Regular.woff

PT_Sans-Regular.woff

1381 ms

PT_Sans-Bold.woff

PT_Sans-Bold.woff

1383 ms

site-icons.png

site-icons.png

504 ms

analytics.js

analytics.js

14 ms

tag.js

tag.js

939 ms

collect

collect

11 ms

js

js

53 ms

zrt_lookup.html

zrt_lookup.html

38 ms

login-sprite.png

login-sprite.png

953 ms

ads

ads

516 ms

hit;vtomske

hit;vtomske

130 ms

reactive_library.js

reactive_library.js

208 ms

ca-pub-1494072297171491

ca-pub-1494072297171491

62 ms

ads

ads

142 ms

ads

ads

165 ms

ads

ads

310 ms

advert.gif

advert.gif

678 ms

14924004616097795287

14924004616097795287

24 ms

abg_lite.js

abg_lite.js

27 ms

s

s

7 ms

window_focus.js

window_focus.js

139 ms

qs_click_protection.js

qs_click_protection.js

30 ms

ufs_web_display.js

ufs_web_display.js

20 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

138 ms

icon.png

icon.png

14 ms

activeview

activeview

61 ms

ingest

ingest

171 ms

check

check

19 ms

WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js

WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js

5 ms

sync_cookie_image_decide

sync_cookie_image_decide

146 ms

Accessibility Review

vtomske.ru accessibility score

78

Accessibility Issues

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

High

[role] values are not valid

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

vtomske.ru best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

vtomske.ru SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vtomske.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 Vtomske.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.

Social Sharing Optimization

vtomske.ru

Open Graph data is detected on the main page of Vtomske. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: