25.5 sec in total
2.2 sec
22.7 sec
719 ms
Visit webcash.com.my now to see the best up-to-date Webcash content for Malaysia and also check out these interesting facts you probably never knew about webcash.com.my
Go cashless everywhere now with the new Kiple Visa Prepaid Card. Spend and get better rewards when you sign up with KipleUNI Student ID.
Visit webcash.com.myWe analyzed Webcash.com.my page load time and found that the first response time was 2.2 sec and then it took 23.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
webcash.com.my performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value10.7 s
0/100
25%
Value22.8 s
0/100
10%
Value3,020 ms
2/100
30%
Value0.112
86/100
15%
Value36.9 s
0/100
10%
2158 ms
2724 ms
1168 ms
1592 ms
2800 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 92% of them (55 requests) were addressed to the original Webcash.com.my, 3% (2 requests) were made to Stats.g.doubleclick.net and 2% (1 request) were made to Seal.verisign.com. The less responsive or slowest element that took the longest time to load (14 sec) belongs to the original domain Webcash.com.my.
Page size can be reduced by 378.1 kB (25%)
1.5 MB
1.1 MB
In fact, the total size of Webcash.com.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. 40% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 20.2 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 5.4 kB, which is 22% 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 20.2 kB or 81% of the original size.
Potential reduce by 126.2 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, Webcash needs image optimization as it can save up to 126.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 118.3 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 118.3 kB or 62% of the original size.
Potential reduce by 113.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. Webcash.com.my needs all CSS files to be minified and compressed as it can save up to 113.5 kB or 82% of the original size.
Number of requests can be reduced by 11 (19%)
59
48
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Webcash. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
index.php
2158 ms
bootstrap-min.css
2724 ms
jquery_notification.css
1168 ms
bootstrap-responsive-min.css
1592 ms
jquery_latest_min.js
2800 ms
jquery.yiiactiveform_min.js
1236 ms
bootstrap.min.js
2455 ms
placeholder_min.js
2343 ms
jquery_notification.js
2449 ms
bootstrap-hover-dropdown.min.js
2735 ms
global_v3_min.js
3489 ms
getseal
413 ms
loader_min.js
3584 ms
ajaxloader_min.js
3884 ms
login_min.js
4027 ms
captcha.php
2919 ms
refresh_icon.png
2905 ms
captcha.php
2933 ms
webcash-logo-gw.png
2914 ms
12.jpg
6295 ms
captcha.php
3284 ms
79.png
4906 ms
77.png
8404 ms
78.png
7605 ms
69.jpg
9868 ms
63.png
6340 ms
75.png
9526 ms
service_wcacount.png
7554 ms
service-fdtransfer.png
7569 ms
service-wcpoints.png
8691 ms
service-pastensell.png
8684 ms
service-sdaccount.png
12530 ms
service-wctopup.png
9588 ms
service-wcgateway.png
9824 ms
phonepayment-service.png
10598 ms
54.jpg
10988 ms
1358847755.png
10726 ms
1358847721.jpg
11276 ms
60.png
11278 ms
1358844708.jpg
12123 ms
1358844816.jpg
12370 ms
1358844837.jpg
12682 ms
1358844886.jpg
12682 ms
1358844911.jpg
12884 ms
1358844940.jpg
13613 ms
1358844986.jpg
13795 ms
1358845141.jpg
13948 ms
getseal
364 ms
dot_clear.gif
2579 ms
1358845158.jpg
14030 ms
dc.js
372 ms
1369033561.jpg
14047 ms
1358845004.gif
13593 ms
__utm.gif
2044 ms
1373363953.gif
12178 ms
1373364005.gif
12000 ms
64.gif
12144 ms
86.png
12159 ms
88.jpg
12197 ms
webcash-footer-iso.png
11964 ms
webcash.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.
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
Links do not have a discernible name
webcash.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
webcash.com.my SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webcash.com.my 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 Webcash.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.
webcash.com.my
Open Graph description is not detected on the main page of Webcash. 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: