Tools & Wizards About Us
webpay.by screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

webpay.by

Оплата онлайн, сервис приёма платежей на сайте в Беларуси

Page Load Speed

6.9 sec in total

First Response

523 ms

Resources Loaded

5.2 sec

Page Rendered

1.2 sec

webpay.by screenshot

About Website

Visit webpay.by now to see the best up-to-date Webpay content for Belarus and also check out these interesting facts you probably never knew about webpay.by

Сервис онлайн-оплаты банковскими картами Visa ⭐ MasterCard ⭐ Белкарт ⭐ картами рассрочки и через Систему "Расчёт" ЕРИП от WEBPAY ⭐ Прием платежей на сайте в Беларуси с комиссией от 1,3% ⭐ Подключение ...

Visit webpay.by

Key Findings

We analyzed Webpay.by page load time and found that the first response time was 523 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

webpay.by performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value19.7 s

0/100

25%

SI (Speed Index)

Value15.9 s

0/100

10%

TBT (Total Blocking Time)

Value2,390 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.903

3/100

15%

TTI (Time to Interactive)

Value21.6 s

1/100

10%

Network Requests Diagram

webpay.by

523 ms

webpay.by

942 ms

js

73 ms

intranet-common.min.css

309 ms

ui.design-tokens.min.css

414 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 63% of them (46 requests) were addressed to the original Webpay.by, 14% (10 requests) were made to Crm2.webpay.by and 10% (7 requests) were made to Fonts.bitrix24.by. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Yastatic.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 471.3 kB (38%)

Content Size

1.2 MB

After Optimization

763.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Webpay.by main page is 1.2 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. Javascripts take 614.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 341.7 kB

  • Original 406.3 kB
  • After minification 387.2 kB
  • After compression 64.6 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 341.7 kB or 84% of the original size.

JavaScript Optimization

-14%

Potential reduce by 86.9 kB

  • Original 614.8 kB
  • After minification 614.8 kB
  • After compression 527.9 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 86.9 kB or 14% of the original size.

CSS Optimization

-20%

Potential reduce by 42.6 kB

  • Original 213.2 kB
  • After minification 213.2 kB
  • After compression 170.6 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. Webpay.by needs all CSS files to be minified and compressed as it can save up to 42.6 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (92%)

Requests Now

65

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

webpay.by

webpay.by

523 ms

webpay.by

webpay.by

942 ms

js

js

73 ms

intranet-common.min.css

intranet-common.min.css

309 ms

ui.design-tokens.min.css

ui.design-tokens.min.css

414 ms

bitrix24-design-tokens.min.css

bitrix24-design-tokens.min.css

761 ms

ui.font.opensans.min.css

ui.font.opensans.min.css

418 ms

main.popup.bundle.min.css

main.popup.bundle.min.css

419 ms

style.min.css

style.min.css

463 ms

style.min.css

style.min.css

468 ms

sidepanel.min.css

sidepanel.min.css

550 ms

core_date.min.css

core_date.min.css

555 ms

ui.buttons.bundle.min.css

ui.buttons.bundle.min.css

556 ms

ui.switcher.bundle.min.css

ui.switcher.bundle.min.css

618 ms

landing_public.min.css

landing_public.min.css

779 ms

style.min.css

style.min.css

825 ms

popup.min.css

popup.min.css

693 ms

catalog_cond.min.css

catalog_cond.min.css

694 ms

style.min.css

style.min.css

806 ms

bootstrap.min.css

bootstrap.min.css

1106 ms

theme.min.css

theme.min.css

1384 ms

template_styles.min.css

template_styles.min.css

896 ms

core.min.js

core.min.js

1552 ms

core_fx.min.js

core_fx.min.js

961 ms

protobuf.min.js

protobuf.min.js

1099 ms

model.min.js

model.min.js

1034 ms

rest.client.min.js

rest.client.min.js

1117 ms

pull.client.min.js

pull.client.min.js

1313 ms

pageobject.min.js

pageobject.min.js

1237 ms

main.popup.bundle.min.js

main.popup.bundle.min.js

1244 ms

core_clipboard.min.js

core_clipboard.min.js

1272 ms

manager.min.js

manager.min.js

1376 ms

slider.min.js

slider.min.js

1400 ms

main.date.min.js

main.date.min.js

1426 ms

core_date.min.js

core_date.min.js

1451 ms

core_window.min.js

core_window.min.js

1652 ms

core_tree.min.js

core_tree.min.js

1521 ms

ui.buttons.bundle.min.js

ui.buttons.bundle.min.js

1522 ms

868 ms

phones.js

phones.js

775 ms

style.css

style.css

1151 ms

main.js

main.js

1178 ms

css2

css2

629 ms

ui.switcher.bundle.min.js

ui.switcher.bundle.min.js

1435 ms

intersectionobserver.min.js

intersectionobserver.min.js

1289 ms

script.js

script.js

1251 ms

jquery_landing.min.js

jquery_landing.min.js

1384 ms

jquery.easing_landing.min.js

jquery.easing_landing.min.js

1297 ms

icon-base.css

icon-base.css

1287 ms

lazyload.min.js

lazyload.min.js

1268 ms

script.min.js

script.min.js

1245 ms

script.min.js

script.min.js

1256 ms

tag.js

tag.js

837 ms

full-e375679eab0e00a5e81ddbb027f673d8841bde2c.js

full-e375679eab0e00a5e81ddbb027f673d8841bde2c.js

1759 ms

assets_webpack_0015364cca_1712155978.js

assets_webpack_0015364cca_1712155978.js

995 ms

loader_170_rn9roz.js

loader_170_rn9roz.js

639 ms

KFOmCnqEu92Fr1Me5WZNCzc.ttf

KFOmCnqEu92Fr1Me5WZNCzc.ttf

611 ms

KFOlCnqEu92Fr1MmEU9vAx0_IsE.ttf

KFOlCnqEu92Fr1MmEU9vAx0_IsE.ttf

826 ms

KFOlCnqEu92Fr1MmSU5vAx0_IsE.ttf

KFOlCnqEu92Fr1MmSU5vAx0_IsE.ttf

826 ms

KFOkCnqEu92Fr1MmgWxPKTU1Kg.ttf

KFOkCnqEu92Fr1MmgWxPKTU1Kg.ttf

851 ms

KFOlCnqEu92Fr1MmWUlvAx0_IsE.ttf

KFOlCnqEu92Fr1MmWUlvAx0_IsE.ttf

852 ms

KFOlCnqEu92Fr1MmYUtvAx0_IsE.ttf

KFOlCnqEu92Fr1MmYUtvAx0_IsE.ttf

919 ms

loader_171_zvf1ce.js

loader_171_zvf1ce.js

675 ms

loader_173_hlhwii.js

loader_173_hlhwii.js

625 ms

call.tracker.js

call.tracker.js

567 ms

loader_1_2bsej6.js

loader_1_2bsej6.js

733 ms

polyfill.js

polyfill.js

143 ms

app.js

app.js

135 ms

advert.gif

advert.gif

528 ms

app.bundle.min.css

app.bundle.min.css

126 ms

app.bundle.min.js

app.bundle.min.js

449 ms

sync_cookie_image_decide

sync_cookie_image_decide

146 ms

sync_cookie_image_decide

sync_cookie_image_decide

136 ms

Accessibility Review

webpay.by accessibility score

83

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

[aria-hidden="true"] elements contain focusable descendents

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

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

webpay.by best practices score

92

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

Page has valid source maps

SEO Factors

webpay.by SEO score

90

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

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 Webpay.by 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 Webpay.by 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

webpay.by

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