Tools & Wizards About Us
revenue.com.my screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

revenue.com.my

Revenue Group Berhad - Digital services reinvented.

Page Load Speed

5.2 sec in total

First Response

923 ms

Resources Loaded

4 sec

Page Rendered

280 ms

revenue.com.my screenshot

About Website

Click here to check amazing Revenue content for Malaysia. Otherwise, check out these important facts you probably never knew about revenue.com.my

The expert in providing fully integrated payment platforms for any business.

Visit revenue.com.my

Key Findings

We analyzed Revenue.com.my page load time and found that the first response time was 923 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

revenue.com.my performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.7 s

0/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.231

54/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

revenue.com.my

923 ms

master.css

274 ms

header.css

525 ms

footer.css

526 ms

sidebar.css

538 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 46.7 kB (22%)

Content Size

217.3 kB

After Optimization

170.6 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Revenue.com.my main page is 217.3 kB. 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 10% of websites need less resources to load. Images take 184.7 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 6.6 kB

  • Original 10.0 kB
  • After minification 9.7 kB
  • After compression 3.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. 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 6.6 kB or 66% of the original size.

Image Optimization

-12%

Potential reduce by 21.4 kB

  • Original 184.7 kB
  • After minification 163.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. Obviously, Revenue needs image optimization as it can save up to 21.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-83%

Potential reduce by 18.7 kB

  • Original 22.7 kB
  • After minification 18.7 kB
  • After compression 3.9 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. Revenue.com.my needs all CSS files to be minified and compressed as it can save up to 18.7 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

44

After Optimization

33

  • Images
  • CSS

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

Network Requests Diagram

revenue.com.my

revenue.com.my

923 ms

master.css

master.css

274 ms

header.css

header.css

525 ms

footer.css

footer.css

526 ms

sidebar.css

sidebar.css

538 ms

content.css

content.css

544 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

610 ms

bodybarcolumn.jpg

bodybarcolumn.jpg

560 ms

logo.jpg

logo.jpg

281 ms

menu_bg.jpg

menu_bg.jpg

539 ms

btn1_b4.gif

btn1_b4.gif

308 ms

menu_separator.gif

menu_separator.gif

314 ms

btn2_b4.gif

btn2_b4.gif

271 ms

btn3_b4.gif

btn3_b4.gif

538 ms

btn4_b4.gif

btn4_b4.gif

552 ms

btn5_b4.gif

btn5_b4.gif

614 ms

bg.jpg

bg.jpg

619 ms

e_debit.jpg

e_debit.jpg

800 ms

dots

dots

802 ms

partner1_verifone.jpg

partner1_verifone.jpg

820 ms

integration3_tools.jpg

integration3_tools.jpg

832 ms

featuredicon.gif

featuredicon.gif

920 ms

revenue_logo_gold.png

revenue_logo_gold.png

924 ms

links_start.jpg

links_start.jpg

1070 ms

links_about_b4.jpg

links_about_b4.jpg

1075 ms

link_separator.jpg

link_separator.jpg

1089 ms

links_prodserv_b4.jpg

links_prodserv_b4.jpg

1101 ms

links_bizapp_b4.jpg

links_bizapp_b4.jpg

1226 ms

links_news_b4.jpg

links_news_b4.jpg

1232 ms

links_spacer.jpg

links_spacer.jpg

1331 ms

links_contact_b4.jpg

links_contact_b4.jpg

1336 ms

links_end.jpg

links_end.jpg

1357 ms

homeimg.jpg

homeimg.jpg

1622 ms

footerdiv_bg.jpg

footerdiv_bg.jpg

1821 ms

footerdiv_fg.jpg

footerdiv_fg.jpg

1830 ms

menushadow.png

menushadow.png

1577 ms

btn1_af.gif

btn1_af.gif

276 ms

btn2_af.gif

btn2_af.gif

273 ms

btn3_af.gif

btn3_af.gif

268 ms

btn5_af.gif

btn5_af.gif

306 ms

btn4_af.gif

btn4_af.gif

310 ms

links_prodserv_af.jpg

links_prodserv_af.jpg

272 ms

links_news_af.jpg

links_news_af.jpg

530 ms

links_contact_af.jpg

links_contact_af.jpg

541 ms

links_bizapp_af.jpg

links_bizapp_af.jpg

533 ms

dropdown_bg_01.gif

dropdown_bg_01.gif

544 ms

dropdown_bg_02.gif

dropdown_bg_02.gif

611 ms

Accessibility Review

revenue.com.my accessibility score

66

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 IDs are not unique

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

revenue.com.my best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

revenue.com.my SEO score

85

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

Links do not have descriptive text

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Revenue.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 Revenue.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.

Social Sharing Optimization

revenue.com.my

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