26.6 sec in total
899 ms
24.6 sec
1.2 sec
Visit revpay.com.my now to see the best up-to-date R E V Pay content for Malaysia and also check out these interesting facts you probably never knew about revpay.com.my
Visit revpay.com.myWe analyzed Revpay.com.my page load time and found that the first response time was 899 ms and then it took 25.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
revpay.com.my performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value8.7 s
1/100
25%
Value7.2 s
30/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value5.9 s
65/100
10%
899 ms
2298 ms
1717 ms
817 ms
167 ms
Our browser made a total of 72 requests to load all elements on the main page. We found that 94% of them (68 requests) were addressed to the original Revpay.com.my, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (17.8 sec) belongs to the original domain Revpay.com.my.
Page size can be reduced by 248.4 kB (11%)
2.2 MB
2.0 MB
In fact, the total size of Revpay.com.my main page is 2.2 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. 40% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 45.4 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 17.0 kB, which is 33% 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 45.4 kB or 88% of the original size.
Potential reduce by 91.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. R E V Pay images are well optimized though.
Potential reduce by 74.6 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 74.6 kB or 67% of the original size.
Potential reduce by 37.0 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. Revpay.com.my needs all CSS files to be minified and compressed as it can save up to 37.0 kB or 87% of the original size.
Number of requests can be reduced by 18 (26%)
68
50
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of R E V 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 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
revpay.com.my
899 ms
revpay.com.my
2298 ms
master.css
1717 ms
tooltipster.css
817 ms
css
167 ms
css
208 ms
revPay_logo.png
1135 ms
farmer.png
4759 ms
mechanic.png
3259 ms
tuitionteacher.png
2733 ms
ceo.png
4732 ms
take_tour.png
2098 ms
revpay_expressplus_greysign.png
2565 ms
revpay_expressplus_bluesign.png
2922 ms
debit.png
3153 ms
signup.png
3595 ms
api.png
3470 ms
express_plus.png
3850 ms
top_box.png
4025 ms
express.png
4354 ms
tick.png
4451 ms
signup_pointer.png
4519 ms
submit.png
5015 ms
jquery-1.8.0.min.js
6300 ms
jquery.easing.1.3.js
5334 ms
jquery.tooltipster.min.js
5347 ms
jquery.infieldlabel.min.js
5092 ms
init.js
5305 ms
signin.png
5824 ms
signupnow.png
5900 ms
body_bg.jpg
4929 ms
background.jpg
5207 ms
wall_lighting.png
6085 ms
revpay_wall.png
6023 ms
header_bar.jpg
5503 ms
top_nav_bg.png
6021 ms
btn_login.jpg
5909 ms
btn_signup.jpg
6072 ms
menu_board.png
7512 ms
btn_home.png
7053 ms
btn_revex.png
7183 ms
btn_revexplus.png
7201 ms
btn_revapi.png
7200 ms
riJWcvd3sYdxJpiCWZvUGC3USBnSvpkopQaUR-2r7iU.ttf
67 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
99 ms
steelfish_rg-webfont.woff
7188 ms
btn_revdebit.png
7621 ms
btn_pricing.png
7444 ms
btn_contacts.png
7277 ms
repay_intro.png
17823 ms
learnmore_pointer.png
6791 ms
next.png
6942 ms
checkerbox_bg.jpg
7747 ms
back.png
6992 ms
expressflow.png
8895 ms
repay_expressplusintro.png
15465 ms
expressplusflow.png
9313 ms
repay_apiintro.png
10026 ms
apiflow.png
13814 ms
repay_debitintro.png
14561 ms
debitflow.png
12164 ms
top_shadow.png
10069 ms
tag.png
11296 ms
list_dot.png
12097 ms
mid_box.png
12606 ms
floor_shadow.png
12459 ms
info_paper_mid.jpg
13460 ms
info_paper_top.jpg
13666 ms
info_paper_bottom.jpg
13575 ms
farmer_sit.png
14904 ms
overlay.png
13458 ms
footer_bg.jpg
13242 ms
revpay.com.my accessibility score
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
[id] attributes on active, focusable elements are not unique
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
<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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
revpay.com.my best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
revpay.com.my SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Revpay.com.my can be misinterpreted by Google and other search engines. Our service has detected that English 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 Revpay.com.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.
revpay.com.my
Open Graph description is not detected on the main page of R E V 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: