Tools & Wizards About Us
ivezha.ru screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    76% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

ivezha.ru

Психологический форум Вежа

Page Load Speed

2.9 sec in total

First Response

187 ms

Resources Loaded

2 sec

Page Rendered

767 ms

ivezha.ru screenshot

About Website

Visit ivezha.ru now to see the best up-to-date Ivezha content for Germany and also check out these interesting facts you probably never knew about ivezha.ru

На нашем форуме вы всегда можете получить бесплатную психологическую помощь и профессиональную консультацию психолога, задать любые вопросы и получить полезные советы.

Visit ivezha.ru

Key Findings

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

Performance Metrics

ivezha.ru performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.105

88/100

15%

TTI (Time to Interactive)

Value5.5 s

71/100

10%

Network Requests Diagram

ivezha.ru

187 ms

vezha.com

327 ms

main-rollup.css

55 ms

vbulletin-core.js

120 ms

init.js

182 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Ivezha.ru, 61% (33 requests) were made to Static.vezha.com and 33% (18 requests) were made to Vezha.com. The less responsive or slowest element that took the longest time to load (738 ms) relates to the external source Static.vezha.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 112.3 kB (44%)

Content Size

257.3 kB

After Optimization

145.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-87%

Potential reduce by 109.2 kB

  • Original 125.4 kB
  • After minification 112.4 kB
  • After compression 16.2 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 109.2 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 2.6 kB

  • Original 45.6 kB
  • After minification 42.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. Ivezha images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 481 B

  • Original 69.6 kB
  • After minification 69.6 kB
  • After compression 69.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

-0%

Potential reduce by 59 B

  • Original 16.8 kB
  • After minification 16.8 kB
  • After compression 16.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. Ivezha.ru has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 39 (76%)

Requests Now

51

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ivezha.ru

ivezha.ru

187 ms

vezha.com

vezha.com

327 ms

main-rollup.css

main-rollup.css

55 ms

vbulletin-core.js

vbulletin-core.js

120 ms

init.js

init.js

182 ms

forumhome-rollup.css

forumhome-rollup.css

183 ms

additional.css

additional.css

109 ms

vbulletin_read_marker.js

vbulletin_read_marker.js

203 ms

sidebar.css

sidebar.css

215 ms

widgets.css

widgets.css

108 ms

tagcloud.css

tagcloud.css

104 ms

vbulletin-sidebar.js

vbulletin-sidebar.js

24 ms

vbulletin_md5.js

vbulletin_md5.js

106 ms

watch.js

watch.js

2 ms

yuiloader-dom-event.js

yuiloader-dom-event.js

44 ms

connection-min.js

connection-min.js

144 ms

animation-min.js

animation-min.js

105 ms

gradient-grey-down.png

gradient-grey-down.png

598 ms

vezha_logo4_autumn.png

vezha_logo4_autumn.png

594 ms

image.php

image.php

595 ms

image.php

image.php

596 ms

image.php

image.php

691 ms

image.php

image.php

662 ms

image.php

image.php

659 ms

vezha_vezha.png

vezha_vezha.png

572 ms

arrow.png

arrow.png

580 ms

search.png

search.png

571 ms

navbit-home.png

navbit-home.png

579 ms

collapse_40b.png

collapse_40b.png

592 ms

forum_old-48.png

forum_old-48.png

591 ms

lastpost-right.png

lastpost-right.png

592 ms

subforum_old-48.png

subforum_old-48.png

595 ms

subforum_old.png

subforum_old.png

656 ms

icon5.png

icon5.png

642 ms

icon3.png

icon3.png

653 ms

collapse_40b_collapsed.png

collapse_40b_collapsed.png

702 ms

forum_stats.png

forum_stats.png

656 ms

legend.png

legend.png

659 ms

forum_new-16.png

forum_new-16.png

686 ms

forum_old-16.png

forum_old-16.png

658 ms

category-16.png

category-16.png

738 ms

forum_link-16.png

forum_link-16.png

734 ms

tab-collapsed.png

tab-collapsed.png

705 ms

widget-forum.png

widget-forum.png

701 ms

unknown.gif

unknown.gif

702 ms

newbtn_middle.png

newbtn_middle.png

292 ms

selected-tab-gradient-with-top-alpha.png

selected-tab-gradient-with-top-alpha.png

345 ms

grey-up.png

grey-up.png

356 ms

gradient-greytowhite.png

gradient-greytowhite.png

343 ms

top-highlight.png

top-highlight.png

401 ms

gradient-black-down.png

gradient-black-down.png

398 ms

bottom-shadow.png

bottom-shadow.png

403 ms

rss_40b.png

rss_40b.png

435 ms

analytics.js

analytics.js

81 ms

Accessibility Review

ivezha.ru accessibility score

76

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]s do not have all required [aria-*] attributes

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

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

SEO Factors

ivezha.ru SEO score

99

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

ivezha.ru

Open Graph description is not detected on the main page of Ivezha. 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: