Tools & Wizards About Us
onpay.my screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

onpay.my

Onpay Solutions - OnPay

Page Load Speed

17.1 sec in total

First Response

4.2 sec

Resources Loaded

11.8 sec

Page Rendered

1.1 sec

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 4.2 sec and then it took 12.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

onpay.my performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

18/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value340 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value8.0 s

43/100

10%

Network Requests Diagram

onpay.my

4183 ms

onpay.my

1699 ms

bootstrap.min.css

95 ms

lightbox.css

124 ms

font-awesome.min.css

91 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 33% of them (28 requests) were addressed to the original Onpay.my, 14% (12 requests) were made to Google.com and 14% (12 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Onpay.my.

Page Optimization Overview & Recommendations

Page size can be reduced by 694.4 kB (46%)

Content Size

1.5 MB

After Optimization

825.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onpay.my 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. 60% of websites need less resources to load. Javascripts take 777.0 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 33.4 kB

  • Original 42.4 kB
  • After minification 36.1 kB
  • After compression 9.0 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 6.3 kB, which is 15% 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 33.4 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 13.1 kB

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

JavaScript Optimization

-67%

Potential reduce by 521.0 kB

  • Original 777.0 kB
  • After minification 774.7 kB
  • After compression 256.0 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 521.0 kB or 67% of the original size.

CSS Optimization

-82%

Potential reduce by 127.0 kB

  • Original 154.1 kB
  • After minification 153.0 kB
  • After compression 27.1 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 needs all CSS files to be minified and compressed as it can save up to 127.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (29%)

Requests Now

72

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

onpay.my

onpay.my

4183 ms

onpay.my

onpay.my

1699 ms

bootstrap.min.css

bootstrap.min.css

95 ms

lightbox.css

lightbox.css

124 ms

font-awesome.min.css

font-awesome.min.css

91 ms

jquery.min.js

jquery.min.js

166 ms

bootstrap.min.js

bootstrap.min.js

101 ms

jquery.easing.min.js

jquery.easing.min.js

162 ms

lightbox.min.js

lightbox.min.js

176 ms

jquery.validate.min.js

jquery.validate.min.js

216 ms

bootstrap-hover-dropdown.min.js

bootstrap-hover-dropdown.min.js

460 ms

onpay-logo.png

onpay-logo.png

942 ms

order-form-1.jpg

order-form-1.jpg

2083 ms

order-form-2.jpg

order-form-2.jpg

1609 ms

dashboard.jpg

dashboard.jpg

2083 ms

products.jpg

products.jpg

2228 ms

sales.jpg

sales.jpg

2505 ms

statistics.jpg

statistics.jpg

2152 ms

reports.jpg

reports.jpg

3598 ms

blast.jpg

blast.jpg

2759 ms

templates.jpg

templates.jpg

2997 ms

partner-badge.png

partner-badge.png

3032 ms

prima-odyssey.png

prima-odyssey.png

3157 ms

al-khaadem.png

al-khaadem.png

4078 ms

sifuadwords.png

sifuadwords.png

3725 ms

firdaus-azizi.png

firdaus-azizi.png

3816 ms

bydrazlan.jpg

bydrazlan.jpg

3841 ms

furqanworks.png

furqanworks.png

4361 ms

signoriz.png

signoriz.png

4205 ms

funemo.png

funemo.png

4282 ms

rajakamil.png

rajakamil.png

4302 ms

brc.png

brc.png

4358 ms

nasihat-niaga.png

nasihat-niaga.png

4511 ms

jeni.png

jeni.png

4617 ms

close.png

close.png

79 ms

loading.gif

loading.gif

81 ms

prev.png

prev.png

78 ms

next.png

next.png

81 ms

frenchstucco.png

frenchstucco.png

5755 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

173 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

201 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

226 ms

UC3ZEjagJi85gF9qFaBgIDTx0bvFePwcBpOqDg3uc64.woff

UC3ZEjagJi85gF9qFaBgIDTx0bvFePwcBpOqDg3uc64.woff

75 ms

2NBgzUtEeyB-Xtpr9bm1CZa6Tn9fxpDPuRSK4Gn5Ybw.woff

2NBgzUtEeyB-Xtpr9bm1CZa6Tn9fxpDPuRSK4Gn5Ybw.woff

75 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

11 ms

captcha

captcha

4924 ms

embed

embed

217 ms

js

js

86 ms

init_embed.js

init_embed.js

64 ms

common.js

common.js

53 ms

map.js

map.js

53 ms

google4.png

google4.png

82 ms

overlay.js

overlay.js

18 ms

util.js

util.js

78 ms

onion.js

onion.js

75 ms

search_impl.js

search_impl.js

76 ms

stats.js

stats.js

26 ms

openhand_8_8.cur

openhand_8_8.cur

46 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

53 ms

controls.js

controls.js

41 ms

transparent.png

transparent.png

112 ms

vt

vt

144 ms

vt

vt

280 ms

vt

vt

177 ms

vt

vt

208 ms

vt

vt

207 ms

vt

vt

175 ms

vt

vt

174 ms

vt

vt

226 ms

vt

vt

236 ms

vt

vt

230 ms

vt

vt

247 ms

css

css

160 ms

entity11.png

entity11.png

89 ms

mapcnt6.png

mapcnt6.png

61 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

44 ms

kh

kh

89 ms

kh

kh

101 ms

tmapctrl.png

tmapctrl.png

40 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

21 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

21 ms

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

21 ms

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

21 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

20 ms

Accessibility Review

onpay.my accessibility score

83

Accessibility Issues

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

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

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

onpay.my 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

Page has valid source maps

SEO Factors

onpay.my 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

    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 data is detected on the main page of On Pay. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: