Tools & Wizards About Us
epay.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

epay.com

Epay is a Global Payment Gateways Solutions Provider-epay.com

Page Load Speed

2.7 sec in total

First Response

214 ms

Resources Loaded

1.8 sec

Page Rendered

635 ms

epay.com screenshot

About Website

Visit epay.com now to see the best up-to-date Epay content for Hong Kong and also check out these interesting facts you probably never knew about epay.com

Epay provides customized payment services for global enterprises, including API gateways, currencies exchange and settlements, etc.

Visit epay.com

Key Findings

We analyzed Epay.com page load time and found that the first response time was 214 ms and then it took 2.5 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

epay.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value1,440 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.684

7/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

epay.com

214 ms

www.epay.com

468 ms

69d14277e1c82f2d.css

197 ms

248021b85e64a650.css

188 ms

polyfills-c67a75d1b6f99dc8.js

296 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that all of those requests were addressed to Epay.com and no external sources were called. The less responsive or slowest element that took the longest time to load (772 ms) belongs to the original domain Epay.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 504.0 kB (24%)

Content Size

2.1 MB

After Optimization

1.6 MB

  • HTML
  • Images

In fact, the total size of Epay.com main page is 2.1 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. 60% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 65.6 kB

  • Original 90.1 kB
  • After minification 90.1 kB
  • After compression 24.5 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 65.6 kB or 73% of the original size.

Image Optimization

-22%

Potential reduce by 438.3 kB

  • Original 2.0 MB
  • After minification 1.6 MB

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, Epay needs image optimization as it can save up to 438.3 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 18 (25%)

Requests Now

72

After Optimization

54

  • Images
  • JavaScript
  • CSS

The browser has sent 72 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 from 19 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

epay.com

epay.com

214 ms

www.epay.com

www.epay.com

468 ms

69d14277e1c82f2d.css

69d14277e1c82f2d.css

197 ms

248021b85e64a650.css

248021b85e64a650.css

188 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

296 ms

webpack-dcddc1c35aae785f.js

webpack-dcddc1c35aae785f.js

193 ms

framework-2ff63dc0032ac97d.js

framework-2ff63dc0032ac97d.js

315 ms

main-c717370c03f63c87.js

main-c717370c03f63c87.js

314 ms

_app-5581a626d9303e3a.js

_app-5581a626d9303e3a.js

499 ms

29107295-4a69275373f23f88.js

29107295-4a69275373f23f88.js

350 ms

1633-aabd311ffeef6193.js

1633-aabd311ffeef6193.js

348 ms

7483-30d431ecfc5a8b6d.js

7483-30d431ecfc5a8b6d.js

350 ms

149-3552f5d1b545b6f1.js

149-3552f5d1b545b6f1.js

351 ms

6394-f709475e7c5759e7.js

6394-f709475e7c5759e7.js

350 ms

1350-7c57e674e50eff7a.js

1350-7c57e674e50eff7a.js

351 ms

2138-d5188657be967ebb.js

2138-d5188657be967ebb.js

389 ms

9597-dec9df9f86e06608.js

9597-dec9df9f86e06608.js

390 ms

5349-ce181c4ddfb9f8bd.js

5349-ce181c4ddfb9f8bd.js

391 ms

2570-c4e73fa257b2ad5e.js

2570-c4e73fa257b2ad5e.js

392 ms

%5B%5B...slug%5D%5D-94ed05a9ddfe26c7.js

%5B%5B...slug%5D%5D-94ed05a9ddfe26c7.js

392 ms

_buildManifest.js

_buildManifest.js

453 ms

_ssgManifest.js

_ssgManifest.js

454 ms

new_epay_logo_en-US.png

new_epay_logo_en-US.png

455 ms

hot.svg

hot.svg

494 ms

getImg

getImg

649 ms

icon1.png

icon1.png

764 ms

solution_icon1.png

solution_icon1.png

535 ms

solution_icon2.png

solution_icon2.png

536 ms

solution_icon3.png

solution_icon3.png

555 ms

Asia.png

Asia.png

616 ms

Asia.png

Asia.png

772 ms

alipay.png

alipay.png

580 ms

OXXO.png

OXXO.png

618 ms

boletol.png

boletol.png

645 ms

fasapay.png

fasapay.png

678 ms

itau.png

itau.png

683 ms

livpay.png

livpay.png

709 ms

ccb.png

ccb.png

709 ms

bbva.png

bbva.png

562 ms

baloto.png

baloto.png

563 ms

pix.png

pix.png

548 ms

rapipago.png

rapipago.png

470 ms

bancoRepublica.png

bancoRepublica.png

464 ms

perfectMoney.png

perfectMoney.png

472 ms

z2u.png

z2u.png

486 ms

nestbrowser.png

nestbrowser.png

494 ms

GCash.png

GCash.png

496 ms

bKash.png

bKash.png

497 ms

liebao.png

liebao.png

523 ms

papaya.png

papaya.png

533 ms

IP2.png

IP2.png

510 ms

luban.png

luban.png

517 ms

ROLA_IP.png

ROLA_IP.png

519 ms

Volet.png

Volet.png

519 ms

home_download-en-US.png

home_download-en-US.png

605 ms

appleStore.png

appleStore.png

494 ms

googlePay2.png

googlePay2.png

508 ms

warningl.png

warningl.png

515 ms

footer_logo.png

footer_logo.png

478 ms

_error-eff6c8535787d329.js

_error-eff6c8535787d329.js

476 ms

facebook@2x.png

facebook@2x.png

470 ms

Twitter@2x.png

Twitter@2x.png

530 ms

Linkedin@2x.png

Linkedin@2x.png

513 ms

Youtube@2x.png

Youtube@2x.png

487 ms

button_icon_1.png

button_icon_1.png

452 ms

button_icon_3.png

button_icon_3.png

451 ms

button_icon_2.png

button_icon_2.png

431 ms

earth-full@2x.png

earth-full@2x.png

438 ms

yonghu@2x.png

yonghu@2x.png

415 ms

bizhonghuishuai@2x.png

bizhonghuishuai@2x.png

415 ms

icon_cny_active.png

icon_cny_active.png

407 ms

icon_receive_default.png

icon_receive_default.png

423 ms

icon_remit_default.png

icon_remit_default.png

398 ms

nationality_17_1x.png

nationality_17_1x.png

400 ms

Accessibility Review

epay.com 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.

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

epay.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

epay.com SEO score

85

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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