Access ssl.easypay.by. EasyPay — подключение к ЕРИП (Расчет) и приему онлайн-платежей банковскими картами

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value8.4 s

19/100

10%

TBT (Total Blocking Time)

Value4,350 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

ssl.easypay.by

466 ms

ssl.easypay.by

972 ms

fonts.css

154 ms

header.css

309 ms

vk.css

464 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 96% of them (82 requests) were addressed to the original Ssl.easypay.by, 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (972 ms) belongs to the original domain Ssl.easypay.by.

Content Size

361.6 kB

After Optimization

110.0 kB

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

HTML Optimization

-78%

Potential reduce by 36.3 kB

Original 46.3 kB
After minification 46.2 kB
After compression 10.1 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 36.3 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 483 B

Original 9.2 kB
After minification 8.7 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. Ssl Easy Pay images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 177.9 kB

Original 262.4 kB
After minification 217.9 kB
After compression 84.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 177.9 kB or 68% of the original size.

CSS Optimization

-85%

Potential reduce by 36.9 kB

Original 43.6 kB
After minification 32.5 kB
After compression 6.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. Ssl.easypay.by needs all CSS files to be minified and compressed as it can save up to 36.9 kB or 85% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the interpretation of your content by users in different locales.

High

<html> element does not have a [lang] attribute

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.

High

Form elements do not have associated labels

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

RU
Language Claimed

N/A
Encoding

WINDOWS-1251

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ssl.easypay.by can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ssl.easypay.by 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

ssl.easypay.by

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

Report Summary

Performance

Accessibility

Best Practices

SEO

EasyPay — подключение к ЕРИП (Расчет) и приему онлайн-платежей банковскими картами

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

ssl.easypay.by

ssl.easypay.by

fonts.css

header.css

vk.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

ssl.easypay.by

ssl.easypay.by

fonts.css

header.css

vk.css

jquery-1.8.3.min.js

posts.js

bv.js

wz_dragdrop.js

vk.js

main.js

ussd_sender.js

jquery.placeholder.min.js

main.css

autocompleter.js

anythingslider.css

jquery.anythingslider.js

vk_icon.gif

vk.png

twitter.png

facebook.png

1450105810.gif

maestro.gif

transferbank.gif

currency.gif

transfer.gif

sms.gif

1424768026.gif

is_auto.gif

is_audio_video.gif

is_technics.gif

is_child.gif

is_cd_dvd.gif

is_home.gif

is_computer.gif

is_health.gif

is_furniture.gif

is_clothes.gif

is_equipment.gif

is_sport.gif

is_construction.gif

is_telephony.gif

is_photo.gif