7.2 sec in total
579 ms
6.3 sec
328 ms
Visit whohaa.com now to see the best up-to-date WhoHAA content for Malaysia and also check out these interesting facts you probably never knew about whohaa.com
WhoHAA let you earn Free Points from our sponsors and use it to redeem our items for FREE!
Visit whohaa.comWe analyzed Whohaa.com page load time and found that the first response time was 579 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
whohaa.com performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value4.6 s
34/100
25%
Value4.1 s
79/100
10%
Value360 ms
72/100
30%
Value0.067
97/100
15%
Value6.7 s
56/100
10%
579 ms
595 ms
258 ms
488 ms
491 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 59% of them (74 requests) were addressed to the original Whohaa.com, 16% (20 requests) were made to Static.xx.fbcdn.net and 7% (9 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Whohaa.com.
Page size can be reduced by 935.1 kB (40%)
2.3 MB
1.4 MB
In fact, the total size of Whohaa.com 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 26.5 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 26.5 kB or 78% of the original size.
Potential reduce by 114.8 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. WhoHAA images are well optimized though.
Potential reduce by 725.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 725.0 kB or 82% of the original size.
Potential reduce by 68.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. Whohaa.com needs all CSS files to be minified and compressed as it can save up to 68.9 kB or 84% of the original size.
Number of requests can be reduced by 40 (33%)
123
83
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WhoHAA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
whohaa.com
579 ms
www.whohaa.com
595 ms
whohaa_main.css
258 ms
jquery-ui-whohaa.css
488 ms
carousel.css
491 ms
showcase.css
497 ms
showhide.css
500 ms
colorbox.css
501 ms
pagination.css
511 ms
jquery-1.9.1.js
1701 ms
jquery-ui-1.10.2.custom.js
1721 ms
jquery.carouFredSel-6.2.0-packed.js
992 ms
jquery.colorbox-min.js
746 ms
jquery.mousewheel.min.js
752 ms
jquery.aw-showcase.js
767 ms
showHide.js
998 ms
analytics.js
134 ms
all.js
134 ms
widgets.js
186 ms
whohaa_logoi.png
1025 ms
country_malaysia.png
292 ms
icon_twitter.png
331 ms
icon_facebook.png
330 ms
slider_1.jpg
1036 ms
slider_3.jpg
785 ms
btn_slide_next.png
493 ms
btn_slide_pre.png
546 ms
sepbar.png
543 ms
title_earnpoints.png
782 ms
title_redeem.png
1014 ms
1371614168838.jpg
1015 ms
14086786850988.jpg
1035 ms
14086785297697.jpg
1033 ms
13971863179702.jpg
1283 ms
13965884806872.jpg
1282 ms
13965879880591.jpg
1294 ms
13965876256323.jpg
1272 ms
13965820468745.jpg
1279 ms
13965801867369.jpg
1273 ms
14168052119791.jpg
1999 ms
14086787977931.jpg
1518 ms
14086786604217.jpg
1526 ms
13971864196571.jpg
1774 ms
13965885740536.jpg
1536 ms
13965880552765.jpg
1543 ms
13965877588939.jpg
1761 ms
13965822396211.jpg
1775 ms
13965817477145.jpg
2046 ms
13862139689614.jpg
1793 ms
13830187199882.jpg
2005 ms
14129090720786.jpg
2020 ms
14129089321746.jpg
2023 ms
13965829660651.jpg
2044 ms
13965886427054.jpg
2238 ms
13965883861283.jpg
2247 ms
plusone.js
151 ms
collect
35 ms
likebox.php
366 ms
cb=gapi.loaded_0
13 ms
cb=gapi.loaded_1
56 ms
fastbutton
157 ms
152 ms
xd_arbiter.php
109 ms
xd_arbiter.php
207 ms
13965878621869.jpg
1984 ms
postmessageRelay
52 ms
13965818376128.jpg
1951 ms
13692092910287.jpg
1974 ms
3193398744-postmessagerelay.js
35 ms
rpc:shindig_random.js
29 ms
rs=AGLTcCNFg9Lxr6A_1qJE1FafaQPPaU_lFQ
16 ms
cb=gapi.loaded_0
54 ms
cb=gapi.loaded_0
46 ms
cb=gapi.loaded_1
47 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
73 ms
13692091799315.jpg
1808 ms
hDvwL1_H7g-.css
85 ms
56WNbrUYLbL.css
107 ms
yZ--Yu0PDbV.css
127 ms
QD6_ejUFoCN.css
170 ms
xxJgcoj8mOR.css
179 ms
q68gy-v_YMF.js
179 ms
FJmpeSpHpjS.js
237 ms
0wM5s1Khldu.js
139 ms
1bNoFZUdlYZ.js
134 ms
njO1TPvGzoR.js
157 ms
1QuX41zDRrx.js
226 ms
Oagsvfb4VWi.js
250 ms
LTv6ZK-5zxz.js
259 ms
1FCa-btixu2.js
256 ms
13716116154914.jpeg
1948 ms
13965842311055.jpg
1956 ms
13751593909223.jpg
2234 ms
1004886_545574628837128_1629914648_n.jpg
235 ms
safe_image.php
258 ms
safe_image.php
336 ms
13716406742455.jpg
1668 ms
1544599_622637521130838_804195010_n.jpg
241 ms
1379841_10150004552801901_469209496895221757_n.jpg
257 ms
12193363_1019017454808127_5352539455431208496_n.jpg
276 ms
12715711_820866704709531_7051384998196647859_n.jpg
274 ms
10440750_994277590633836_4903273647566566823_n.jpg
302 ms
1922460_1406567686275198_330795272_n.jpg
300 ms
12360299_988647654529821_1335241547075437695_n.jpg
341 ms
1004886_545574628837128_1629914648_n.jpg
285 ms
wL6VQj7Ab77.png
152 ms
s7jcwEQH7Sx.png
153 ms
QDwYpIaRyfG.png
153 ms
K00K-UgnsKu.png
153 ms
13716351000924.jpg
1539 ms
title_specialbuy.png
1548 ms
index_specialbuy.jpg
1958 ms
50000_ani.gif
1955 ms
bottom_howitworks.png
1745 ms
btn_top.png
1767 ms
I6-MnjEovm5.js
21 ms
pQrUxxo5oQp.js
35 ms
whohaa_logo2.png
1543 ms
icon_plus.png
1754 ms
icon_arrow.png
1773 ms
btn_earnpoints.png
1791 ms
btn_redeembuy.png
1935 ms
icon_twitter_b.png
1939 ms
icon_facebook_b.png
1745 ms
overlay.png
1750 ms
xd_arbiter.php
38 ms
whohaa.com 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
Heading elements are not in a sequentially-descending order
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
whohaa.com 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
whohaa.com SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whohaa.com 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 Whohaa.com 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.
whohaa.com
Open Graph data is detected on the main page of WhoHAA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: