Tools & Wizards About Us
toster.ru screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

toster.ru

Интересные вопросы — Хабр Q&A

Page Load Speed

8.3 sec in total

First Response

247 ms

Resources Loaded

7.2 sec

Page Rendered

816 ms

toster.ru screenshot

About Website

Click here to check amazing Toster content for Russia. Otherwise, check out these important facts you probably never knew about toster.ru

Интересные вопросы сервиса вопросов и ответов по IT-тематике Хабр Q&A.

Visit toster.ru

Key Findings

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

Performance Metrics

toster.ru performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value7.8 s

3/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value1,030 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value13.0 s

13/100

10%

Network Requests Diagram

toster.ru

247 ms

toster.ru

630 ms

css

790 ms

frontend.251d7ab2-d6f6-11e5-81cb-38eaa71001f0.css

877 ms

modernizr.custom.js

908 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 6% of them (3 requests) were addressed to the original Toster.ru, 19% (10 requests) were made to Images1-focus-opensocial.googleusercontent.com and 11% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Content.adriver.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 283.4 kB (64%)

Content Size

440.0 kB

After Optimization

156.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Toster.ru main page is 440.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. 45% of websites need less resources to load. HTML takes 187.0 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 163.6 kB

  • Original 187.0 kB
  • After minification 159.4 kB
  • After compression 23.4 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 27.6 kB, which is 15% 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 163.6 kB or 87% of the original size.

Image Optimization

-15%

Potential reduce by 3.1 kB

  • Original 20.4 kB
  • After minification 17.3 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. Obviously, Toster needs image optimization as it can save up to 3.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-9%

Potential reduce by 9.6 kB

  • Original 101.7 kB
  • After minification 99.6 kB
  • After compression 92.1 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

-82%

Potential reduce by 107.0 kB

  • Original 131.0 kB
  • After minification 130.9 kB
  • After compression 23.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. Toster.ru needs all CSS files to be minified and compressed as it can save up to 107.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (66%)

Requests Now

47

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

toster.ru

toster.ru

247 ms

toster.ru

toster.ru

630 ms

css

css

790 ms

frontend.251d7ab2-d6f6-11e5-81cb-38eaa71001f0.css

frontend.251d7ab2-d6f6-11e5-81cb-38eaa71001f0.css

877 ms

modernizr.custom.js

modernizr.custom.js

908 ms

adriver.core.2.js

adriver.core.2.js

1676 ms

adsbygoogle.js

adsbygoogle.js

387 ms

frontend.251d7ab2-d6f6-11e5-81cb-38eaa71001f0.js

frontend.251d7ab2-d6f6-11e5-81cb-38eaa71001f0.js

1004 ms

autoUpdate.adriver.js

autoUpdate.adriver.js

1490 ms

rta.js

rta.js

508 ms

sprite_0.1.svg

sprite_0.1.svg

1018 ms

proxy

proxy

1282 ms

proxy

proxy

1447 ms

proxy

proxy

1464 ms

proxy

proxy

1510 ms

proxy

proxy

1521 ms

proxy

proxy

1529 ms

proxy

proxy

1521 ms

proxy

proxy

1527 ms

proxy

proxy

1546 ms

proxy

proxy

1582 ms

pkYDSlCHbDnBWPT5PPFFTA.ttf

pkYDSlCHbDnBWPT5PPFFTA.ttf

948 ms

g46X4VH_KHOWAAa-HpnGPi3USBnSvpkopQaUR-2r7iU.ttf

g46X4VH_KHOWAAa-HpnGPi3USBnSvpkopQaUR-2r7iU.ttf

1221 ms

ca-pub-4098002249090227.js

ca-pub-4098002249090227.js

193 ms

zrt_lookup.html

zrt_lookup.html

1157 ms

show_ads_impl.js

show_ads_impl.js

304 ms

context.js

context.js

1418 ms

ads

ads

1412 ms

fbevents.js

fbevents.js

1028 ms

osd.js

osd.js

761 ms

analytics.js

analytics.js

963 ms

watch.js

watch.js

335 ms

803 ms

ads

ads

337 ms

old.adriver.js

old.adriver.js

2270 ms

274 ms

m_js_controller.js

m_js_controller.js

464 ms

abg.js

abg.js

518 ms

collect

collect

66 ms

collect

collect

234 ms

context_static_r1084.js

context_static_r1084.js

945 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

363 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

136 ms

x_button_blue2.png

x_button_blue2.png

312 ms

s

s

34 ms

Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js

Rf2QnA3orEL6Eez56HJgxRuQ77qJyxbefnbSCBE0iUQ.js

20 ms

watch.js

watch.js

0 ms

149488

149488

898 ms

activeview

activeview

72 ms

checkFlash.adriver.js

checkFlash.adriver.js

536 ms

functions.adriver.js

functions.adriver.js

536 ms

y150

y150

658 ms

merle.cgi

merle.cgi

361 ms

Accessibility Review

toster.ru accessibility score

57

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

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

toster.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

toster.ru SEO score

96

Search Engine Optimization Advices

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 Toster.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 Toster.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

toster.ru

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