Tools & Wizards About Us
epay.bg screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

epay.bg

ePay.bg

Page Load Speed

3.8 sec in total

First Response

471 ms

Resources Loaded

3.2 sec

Page Rendered

121 ms

epay.bg screenshot

About Website

Welcome to epay.bg homepage info - get ready to check EPay best content for Bulgaria right away, or after learning these important things about epay.bg

ePay.bg is the Bulgarian Internet payment system. It allows users to pay their utility bills, initiate bank transfers, order goods and services on the WEB and pay taxes on-line. All major debit and cr...

Visit epay.bg

Key Findings

We analyzed Epay.bg page load time and found that the first response time was 471 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

epay.bg performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

53/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.195

63/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

epay.bg

471 ms

517 ms

front

640 ms

bs3.epay.css

707 ms

bootstrap.epay.css

617 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 9% of them (3 requests) were addressed to the original Epay.bg, 91% (31 requests) were made to Online.epay.bg. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Online.epay.bg.

Page Optimization Overview & Recommendations

Page size can be reduced by 33.6 kB (7%)

Content Size

479.9 kB

After Optimization

446.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Epay.bg main page is 479.9 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. 25% of websites need less resources to load. Images take 382.9 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 25.7 kB

  • Original 31.5 kB
  • After minification 23.1 kB
  • After compression 5.8 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 8.4 kB, which is 27% 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 25.7 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 5.3 kB

  • Original 382.9 kB
  • After minification 377.6 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. EPay images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 92 B

  • Original 42.5 kB
  • After minification 42.5 kB
  • After compression 42.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. This website has mostly compressed JavaScripts.

CSS Optimization

-10%

Potential reduce by 2.4 kB

  • Original 22.9 kB
  • After minification 22.9 kB
  • After compression 20.5 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. Epay.bg has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 5 (19%)

Requests Now

27

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

epay.bg

epay.bg

471 ms

517 ms

front

front

640 ms

bs3.epay.css

bs3.epay.css

707 ms

bootstrap.epay.css

bootstrap.epay.css

617 ms

front.css

front.css

627 ms

ep_logo.im.19c59eb1c7253888ca4a547182b9bd36.png

ep_logo.im.19c59eb1c7253888ca4a547182b9bd36.png

628 ms

u_visa.im.d6c8a8baef7a9d3d7809ed610ce4bdc6.jpg

u_visa.im.d6c8a8baef7a9d3d7809ed610ce4bdc6.jpg

761 ms

front-banner-money-transfer.im.f7b5ca46edf270193ce456249dcaf4b3.jpg

front-banner-money-transfer.im.f7b5ca46edf270193ce456249dcaf4b3.jpg

890 ms

front-banner-10-digi.im.a49eb3f05d5795487fd5e31a395593a1.jpg

front-banner-10-digi.im.a49eb3f05d5795487fd5e31a395593a1.jpg

969 ms

front-banner-bs.im.0b1468331d4d9b218f39421669d8fdc0.jpg

front-banner-bs.im.0b1468331d4d9b218f39421669d8fdc0.jpg

976 ms

front-banner-tax.im.2805d4f52e21d95d7fdc322ab3cc2bc1.jpg

front-banner-tax.im.2805d4f52e21d95d7fdc322ab3cc2bc1.jpg

862 ms

front-banner-vinetka.im.e1da3e3b55dbf21c3d7432c648683016.jpg

front-banner-vinetka.im.e1da3e3b55dbf21c3d7432c648683016.jpg

936 ms

jquery-3.6.0.min.im.8fb8fee4fcc3cc86ff6c724154c49c42.js

jquery-3.6.0.min.im.8fb8fee4fcc3cc86ff6c724154c49c42.js

870 ms

bootstrap-3.4.1.min.im.2f34b630ffe30ba2ff2b91e3f3c322a1.js

bootstrap-3.4.1.min.im.2f34b630ffe30ba2ff2b91e3f3c322a1.js

982 ms

front.js

front.js

989 ms

n.png

n.png

1000 ms

h_1.im.42b0619fbeb270fa4f42b31ec154d8bc.png

h_1.im.42b0619fbeb270fa4f42b31ec154d8bc.png

1048 ms

h_4.im.a88246f83615eeace0c69584496a7c89.png

h_4.im.a88246f83615eeace0c69584496a7c89.png

1086 ms

h_3.im.81a35bd83c07be82de9cb165ef57de66.png

h_3.im.81a35bd83c07be82de9cb165ef57de66.png

1092 ms

h_2.im.2daf778ba4bb5e61f9f47e6e124cb5e8.png

h_2.im.2daf778ba4bb5e61f9f47e6e124cb5e8.png

1099 ms

ad1.im.0fb3eea40eec568abce340ea21965fa3.png

ad1.im.0fb3eea40eec568abce340ea21965fa3.png

1104 ms

ad2.im.1aa856cd440c1b6a7b9d94dbd8ccbf6a.png

ad2.im.1aa856cd440c1b6a7b9d94dbd8ccbf6a.png

1122 ms

ad3.im.cd0a1212d183efe3fce79ec7be5376cb.png

ad3.im.cd0a1212d183efe3fce79ec7be5376cb.png

1160 ms

app_store.im.364d36cce21b5b94b618376c41a8aaf6.png

app_store.im.364d36cce21b5b94b618376c41a8aaf6.png

1203 ms

app_google.im.29b6834f21c9ccd5a6cecd0a0d79b877.png

app_google.im.29b6834f21c9ccd5a6cecd0a0d79b877.png

1209 ms

app_store_hu.im.5321ededdca2e04528a84a6b4651b76f.png

app_store_hu.im.5321ededdca2e04528a84a6b4651b76f.png

1217 ms

ad4_vi_ma.im.1ad2998074d7078193b4ffb33aed87e8.png

ad4_vi_ma.im.1ad2998074d7078193b4ffb33aed87e8.png

1222 ms

head_bac.im.307ed4af9d729de7f0d2375a8b0115b7.png

head_bac.im.307ed4af9d729de7f0d2375a8b0115b7.png

521 ms

pane_bac.png

pane_bac.png

550 ms

Roboto-Regular.ttf

Roboto-Regular.ttf

685 ms

hel57.ttf

hel57.ttf

688 ms

PTS55F.ttf

PTS55F.ttf

836 ms

Roboto-Medium.ttf

Roboto-Medium.ttf

726 ms

Accessibility Review

epay.bg accessibility score

60

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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.

Best Practices

epay.bg best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

epay.bg SEO score

91

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    BG

  • Language Claimed

    BG

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epay.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it matches the claimed language. Our system also found out that Epay.bg 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

epay.bg

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