Tools & Wizards About Us
onpay.my screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

onpay.my

Onpay Solutions - OnPay

Page Load Speed

2.3 sec in total

First Response

18 ms

Resources Loaded

1.5 sec

Page Rendered

743 ms

onpay.my screenshot

About Website

Welcome to onpay.my homepage info - get ready to check On Pay best content for Malaysia right away, or after learning these important things about onpay.my

OnPay Solutions menyediakan satu penyelesaian yang sesuai untuk pemilik atau usahawan bisnes online untuk menguruskan bisnes dan jualan mereka dengan mudah.

Visit onpay.my

Key Findings

We analyzed Onpay.my page load time and found that the first response time was 18 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

onpay.my performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value4,370 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

onpay.my

18 ms

onpay.my

327 ms

jquery-3.7.0.min.js

51 ms

bootstrap.min.css

67 ms

bootstrap.bundle.min.js

95 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 67% of them (62 requests) were addressed to the original Onpay.my, 7% (6 requests) were made to Cdnjs.cloudflare.com and 5% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (779 ms) belongs to the original domain Onpay.my.

Page Optimization Overview & Recommendations

Page size can be reduced by 124.9 kB (6%)

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onpay.my main page is 2.3 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. Only a small number of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 121.4 kB

  • Original 138.1 kB
  • After minification 136.4 kB
  • After compression 16.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 121.4 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 588 B

  • Original 1.8 MB
  • After minification 1.8 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. On Pay images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 223.6 kB
  • After minification 223.6 kB
  • After compression 220.8 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

-0%

Potential reduce by 43 B

  • Original 62.6 kB
  • After minification 62.6 kB
  • After compression 62.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. Onpay.my has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (26%)

Requests Now

86

After Optimization

64

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of On 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 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

onpay.my

onpay.my

18 ms

onpay.my

onpay.my

327 ms

jquery-3.7.0.min.js

jquery-3.7.0.min.js

51 ms

bootstrap.min.css

bootstrap.min.css

67 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

95 ms

css

css

82 ms

jquery.mCustomScrollbar.min.css

jquery.mCustomScrollbar.min.css

81 ms

bootstrap.min.css

bootstrap.min.css

135 ms

font-awesome.min.css

font-awesome.min.css

131 ms

style-base.d1e73622.min.css

style-base.d1e73622.min.css

27 ms

jquery.min.js

jquery.min.js

167 ms

bootstrap.min.js

bootstrap.min.js

179 ms

vendors-base.03d56807.min.js

vendors-base.03d56807.min.js

41 ms

zooming.min.js

zooming.min.js

177 ms

conversion.js

conversion.js

187 ms

onpay-logo-white.png

onpay-logo-white.png

252 ms

gxcANZHe-5w

gxcANZHe-5w

348 ms

pink-tick.png

pink-tick.png

247 ms

google-play.png

google-play.png

248 ms

app-store.png

app-store.png

276 ms

app-gallery.png

app-gallery.png

277 ms

jumlah-pengguna.png

jumlah-pengguna.png

275 ms

jumlah-transaksi.png

jumlah-transaksi.png

277 ms

jumlah-jualan.png

jumlah-jualan.png

277 ms

durioo.png

durioo.png

276 ms

ezydurian.png

ezydurian.png

326 ms

lilcalips.png

lilcalips.png

322 ms

logo-academywire.png

logo-academywire.png

322 ms

byond-dark-logo.png

byond-dark-logo.png

323 ms

th.png

th.png

779 ms

iman-care.png

iman-care.png

334 ms

SM-MELINTANG-PUTIH.png

SM-MELINTANG-PUTIH.png

392 ms

logo-ombak-bk.png

logo-ombak-bk.png

390 ms

madad.png

madad.png

778 ms

buruj.jpeg

buruj.jpeg

390 ms

emraz-travel.jpg

emraz-travel.jpg

390 ms

logo-ptti-zoom.png

logo-ptti-zoom.png

418 ms

logo-phr.png

logo-phr.png

418 ms

gymfbads.png

gymfbads.png

417 ms

sales-page.png

sales-page.png

418 ms

wave.png

wave.png

622 ms

ejen.png

ejen.png

623 ms

integrasi.png

integrasi.png

622 ms

emel.png

emel.png

623 ms

high-volume.png

high-volume.png

625 ms

customer-service.png

customer-service.png

623 ms

equation-onpay.jpg

equation-onpay.jpg

625 ms

bell.png

bell.png

626 ms

invoice.png

invoice.png

626 ms

report.png

report.png

625 ms

affiliate.png

affiliate.png

626 ms

cart.png

cart.png

627 ms

analytics.js

analytics.js

324 ms

544 ms

fbevents.js

fbevents.js

252 ms

default

default

544 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

151 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

47 ms

website.png

website.png

396 ms

package-free.png

package-free.png

387 ms

package-tick.png

package-tick.png

385 ms

package-cross.png

package-cross.png

360 ms

package-basic.png

package-basic.png

359 ms

package-lite.png

package-lite.png

359 ms

package-premium.png

package-premium.png

502 ms

premium-agent.png

premium-agent.png

359 ms

lite-dropship.png

lite-dropship.png

359 ms

liza-asmadi.png

liza-asmadi.png

431 ms

aziz-mk.png

aziz-mk.png

429 ms

sophia-ruslan.png

sophia-ruslan.png

431 ms

amiruddin.png

amiruddin.png

426 ms

www-player.css

www-player.css

38 ms

www-embed-player.js

www-embed-player.js

61 ms

base.js

base.js

130 ms

dr_taufiq.png

dr_taufiq.png

390 ms

uztaz_hakim.png

uztaz_hakim.png

365 ms

footer-icon.png

footer-icon.png

364 ms

megaphone.png

megaphone.png

430 ms

tiktok.png

tiktok.png

338 ms

facebook.png

facebook.png

337 ms

instagram.png

instagram.png

338 ms

Ripple.gif

Ripple.gif

338 ms

collect

collect

321 ms

circle-tick.png

circle-tick.png

298 ms

ad_status.js

ad_status.js

161 ms

-iaWypUxMAwVmZo986mMThLjwUu_f6uBwRf76o5foO4.js

-iaWypUxMAwVmZo986mMThLjwUu_f6uBwRf76o5foO4.js

124 ms

embed.js

embed.js

46 ms

id

id

35 ms

js

js

154 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

30 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

40 ms

Create

Create

120 ms

Accessibility Review

onpay.my accessibility score

57

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-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

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

Impact

Issue

High

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

onpay.my best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

onpay.my SEO score

92

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

Language and Encoding

  • Language Detected

    MS

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onpay.my can be misinterpreted by Google and other search engines. Our service has detected that Malay 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 Onpay.my 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

onpay.my

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