Tools & Wizards About Us
weba.ru screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

weba.ru

Провайдер WEBA — интернет, телевидение, телефония в СПб

Page Load Speed

5.2 sec in total

First Response

403 ms

Resources Loaded

4.6 sec

Page Rendered

203 ms

weba.ru screenshot

About Website

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

Подключить быстрый интернет, домашнюю телефонию, IPTV HD качества у провайдера WEBA — выгодные тарифы на услуги | Обслуживание физических и юридических лиц.

Visit weba.ru

Key Findings

We analyzed Weba.ru page load time and found that the first response time was 403 ms and then it took 4.8 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

weba.ru performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value14.0 s

0/100

25%

SI (Speed Index)

Value14.3 s

1/100

10%

TBT (Total Blocking Time)

Value560 ms

53/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

weba.ru

403 ms

www.weba.ru

979 ms

kernel_main.css

255 ms

template_609dcc560430ad6f3c260c4d89e9417d.css

271 ms

AC_RunActiveContent.js

272 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 69% of them (49 requests) were addressed to the original Weba.ru, 11% (8 requests) were made to Apis.google.com and 6% (4 requests) were made to Online.weba.ru. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Weba.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 688.1 kB (70%)

Content Size

986.7 kB

After Optimization

298.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weba.ru main page is 986.7 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 856.3 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 22.0 kB

  • Original 30.0 kB
  • After minification 27.0 kB
  • After compression 8.0 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 22.0 kB or 73% of the original size.

Image Optimization

-14%

Potential reduce by 5.6 kB

  • Original 41.6 kB
  • After minification 36.0 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, WEBA needs image optimization as it can save up to 5.6 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 609.9 kB

  • Original 856.3 kB
  • After minification 851.1 kB
  • After compression 246.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 609.9 kB or 71% of the original size.

CSS Optimization

-86%

Potential reduce by 50.6 kB

  • Original 58.8 kB
  • After minification 57.6 kB
  • After compression 8.2 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. Weba.ru needs all CSS files to be minified and compressed as it can save up to 50.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (65%)

Requests Now

65

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WEBA. 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

weba.ru

weba.ru

403 ms

www.weba.ru

www.weba.ru

979 ms

kernel_main.css

kernel_main.css

255 ms

template_609dcc560430ad6f3c260c4d89e9417d.css

template_609dcc560430ad6f3c260c4d89e9417d.css

271 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

272 ms

kernel_main.js

kernel_main.js

580 ms

rsasecurity.min.js

rsasecurity.min.js

272 ms

jquery.tools.min.js

jquery.tools.min.js

542 ms

plusone.js

plusone.js

87 ms

conversion.js

conversion.js

35 ms

ba.js

ba.js

182 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

41 ms

bigban_html5.html

bigban_html5.html

572 ms

miniban_html5.html

miniban_html5.html

389 ms

head_bg.gif

head_bg.gif

264 ms

head_socket0.gif

head_socket0.gif

265 ms

logo.gif

logo.gif

266 ms

tel.gif

tel.gif

267 ms

ico_support.gif

ico_support.gif

519 ms

ico_forums.gif

ico_forums.gif

526 ms

ico_safety.gif

ico_safety.gif

527 ms

ico_blogs.gif

ico_blogs.gif

604 ms

ico_news.gif

ico_news.gif

659 ms

ico_achive.gif

ico_achive.gif

769 ms

t_11.gif

t_11.gif

783 ms

t_12.gif

t_12.gif

784 ms

t_13.gif

t_13.gif

811 ms

t_21.gif

t_21.gif

882 ms

speed_1.gif

speed_1.gif

929 ms

t_22.gif

t_22.gif

1032 ms

speed_2.gif

speed_2.gif

1043 ms

t_23.gif

t_23.gif

1051 ms

speed_3.gif

speed_3.gif

1070 ms

t_31.gif

t_31.gif

1134 ms

t_32.gif

t_32.gif

1175 ms

t_33.gif

t_33.gif

1287 ms

tarifs_logo_avast.png

tarifs_logo_avast.png

1299 ms

tarifs_logo_kav.png

tarifs_logo_kav.png

1312 ms

tarif_ico_phone.png

tarif_ico_phone.png

1338 ms

tarif_ico_teamviewer.png

tarif_ico_teamviewer.png

1388 ms

tarif_ico_support.png

tarif_ico_support.png

1428 ms

ico_login.gif

ico_login.gif

1546 ms

but_login.gif

but_login.gif

1567 ms

leaveacomment.jpg

leaveacomment.jpg

1712 ms

corner.gif

corner.gif

1595 ms

ico_arrow.gif

ico_arrow.gif

1623 ms

ico_users.gif

ico_users.gif

1637 ms

ico_services.gif

ico_services.gif

1778 ms

watch.js

watch.js

0 ms

phplive_v2.js.php

phplive_v2.js.php

407 ms

58 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

13 ms

fastbutton

fastbutton

75 ms

postmessageRelay

postmessageRelay

48 ms

57 ms

1077434459-postmessagerelay.js

1077434459-postmessagerelay.js

54 ms

rpc:shindig_random.js

rpc:shindig_random.js

49 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

39 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

38 ms

W5F8_SL0XFawnjxHGsZjJA.ttf

W5F8_SL0XFawnjxHGsZjJA.ttf

42 ms

bx_stat

bx_stat

216 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

ico_info.gif

ico_info.gif

1574 ms

swiffy_7.4.js

swiffy_7.4.js

2164 ms

ico_networks.gif

ico_networks.gif

1636 ms

foot_bg.gif

foot_bg.gif

1670 ms

foot_plug.gif

foot_plug.gif

1595 ms

footprints.php

footprints.php

420 ms

framework.js

framework.js

391 ms

image.php

image.php

276 ms

index.php

index.php

129 ms

Accessibility Review

weba.ru accessibility score

59

Accessibility Issues

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

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

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

weba.ru best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

weba.ru SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    EN

  • Encoding

    WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weba.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Weba.ru main page’s claimed encoding is windows-1251. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

weba.ru

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