3.7 sec in total
404 ms
2.2 sec
1 sec
Welcome to api.epay.com homepage info - get ready to check Api Epay best content for Hong Kong right away, or after learning these important things about api.epay.com
Epay provides customized payment services for global enterprises, including API gateways, currencies exchange and settlements, etc.
Visit api.epay.comWe analyzed Api.epay.com page load time and found that the first response time was 404 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
api.epay.com performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value21.1 s
0/100
25%
Value18.3 s
0/100
10%
Value14,920 ms
0/100
30%
Value0.387
27/100
15%
Value28.4 s
0/100
10%
404 ms
747 ms
204 ms
198 ms
407 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Api.epay.com, 97% (65 requests) were made to Epay.com and 1% (1 request) were made to . The less responsive or slowest element that took the longest time to load (805 ms) relates to the external source Epay.com.
Page size can be reduced by 100.7 kB (7%)
1.5 MB
1.4 MB
In fact, the total size of Api.epay.com main page is 1.5 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 28.7 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 28.7 kB or 81% of the original size.
Potential reduce by 72.1 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. Api Epay images are well optimized though.
Number of requests can be reduced by 17 (27%)
64
47
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Api 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 18 to 1 for JavaScripts and as a result speed up the page load time.
api.epay.com
404 ms
www.epay.com
747 ms
8ccddd85c1c85bf3.css
204 ms
0a7260978f45940a.css
198 ms
polyfills-5cd94c89d3acac5f.js
407 ms
webpack-34ed88c8fb79ea8d.js
405 ms
framework-2ff63dc0032ac97d.js
436 ms
main-0ee3153e1b82aec9.js
444 ms
_app-b36798d5b874768e.js
522 ms
29107295-4a69275373f23f88.js
433 ms
1633-f243ec16f272e386.js
434 ms
4480-ef8fa27650998948.js
449 ms
8893-1dd42d67e61d8b75.js
449 ms
1350-9188bacf94809edb.js
450 ms
4373-df29113cf0893791.js
452 ms
495-e7a7c3cd57c782a3.js
451 ms
9415-c988fc1c1c15b9dd.js
454 ms
5385-239137b2768a3f67.js
453 ms
%5B%5B...slug%5D%5D-93c9b51ef03dc28d.js
454 ms
_buildManifest.js
456 ms
_ssgManifest.js
455 ms
_middlewareManifest.js
488 ms
logo.png
489 ms
hot.svg
616 ms
getImg
805 ms
getImg
621 ms
getImg
676 ms
banner_notice.png
616 ms
icon1.png
637 ms
solution_icon1.png
605 ms
solution_icon2.png
606 ms
solution_icon3.png
644 ms
GME.png
658 ms
CZB.png
670 ms
alipay.png
694 ms
OXXO.png
716 ms
boletol.png
725 ms
dooPrime.png
729 ms
DRS.png
585 ms
fasapay.png
381 ms
honeycam.png
384 ms
changer.png
381 ms
itau.png
397 ms
livpay.png
404 ms
ccb.png
402 ms
juba.png
435 ms
bbva.png
427 ms
baloto.png
437 ms
pix.png
454 ms
rapipago.png
464 ms
PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA
7 ms
bancoRepublica.png
463 ms
perfectMoney.png
486 ms
z2u.png
517 ms
home_download-en-US.png
644 ms
ios@2x.png
521 ms
googleplay@2x.png
520 ms
footer_logo.png
487 ms
facebook@2x.png
512 ms
Twitter@2x.png
424 ms
Linkedin@2x.png
430 ms
Youtube@2x.png
420 ms
button_icon_1.png
418 ms
button_icon_3.png
468 ms
icon_cny_active.png
478 ms
icon_receive_default.png
457 ms
icon_remit_default.png
439 ms
api.epay.com accessibility score
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
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
api.epay.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
api.epay.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Api.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 Api.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.
api.epay.com
Open Graph data is detected on the main page of Api Epay. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: