28.2 sec in total
510 ms
16.6 sec
11 sec
Click here to check amazing Why Mobile content for Singapore. Otherwise, check out these important facts you probably never knew about whymobile.com
WhyMobile is Singapore's top 10 online mobile phone handphone electronics store. We offer cheap reliable online shopping prices for mobile phones, handphones, cell phones, LTE 4G 5G in Singapore along...
Visit whymobile.comWe analyzed Whymobile.com page load time and found that the first response time was 510 ms and then it took 27.6 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.
whymobile.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value7.2 s
5/100
25%
Value7.2 s
30/100
10%
Value480 ms
59/100
30%
Value0.021
100/100
15%
Value6.5 s
58/100
10%
510 ms
675 ms
1113 ms
711 ms
1111 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 63% of them (50 requests) were addressed to the original Whymobile.com, 4% (3 requests) were made to Code.jquery.com and 4% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source Code.jquery.com.
Page size can be reduced by 288.6 kB (33%)
862.3 kB
573.7 kB
In fact, the total size of Whymobile.com main page is 862.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. 55% of websites need less resources to load. Images take 512.5 kB which makes up the majority of the site volume.
Potential reduce by 34.1 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 7.3 kB, which is 17% 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 34.1 kB or 81% of the original size.
Potential reduce by 39.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. Why Mobile images are well optimized though.
Potential reduce by 173.9 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 173.9 kB or 69% of the original size.
Potential reduce by 41.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. Whymobile.com needs all CSS files to be minified and compressed as it can save up to 41.5 kB or 73% of the original size.
Number of requests can be reduced by 27 (35%)
78
51
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Why Mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
home.php
510 ms
style.css
675 ms
jquery-ui.css
1113 ms
all.js
711 ms
jquery-1.12.4.min.js
1111 ms
jquery-ui.min.js
3524 ms
script.js
969 ms
admanager.js
932 ms
print.css
2882 ms
bounce
329 ms
766 ms
bodybg.gif
801 ms
top10_award_jan_jun_2011.png
736 ms
menubg.gif
737 ms
trans.gif
962 ms
newproducts.gif
961 ms
usedproducts.gif
1010 ms
sell.gif
1029 ms
accessories.gif
1540 ms
repair.gif
1521 ms
ourstore.gif
1521 ms
blank.gif
1521 ms
butt_fb.gif
1522 ms
butt_cart.gif
1522 ms
offer.gif
1511 ms
APL-IPADP105-4G256GB
1474 ms
APL-IPHONE7P-128
1568 ms
APL-IPHONE7-128
1568 ms
SAM-S8PLUS
1568 ms
BB-KEYONE
1384 ms
HTC-U11
1428 ms
SAM-S8
1428 ms
SAM-S7E32
1429 ms
SER-XZS
1430 ms
HUA-MATE9
1158 ms
HUA-P10
1157 ms
SAM-S732
1206 ms
SAM-J7PRO
1206 ms
XIAO-MIMAX2-64
1190 ms
MOTO-360-2G-42
1209 ms
LG-STYLUS3
1210 ms
XIAO-MIPAD2
1209 ms
ASUS-ZENFONE3-MAX553
1209 ms
SAM-J3PRO
1425 ms
XIAO-REDMINOTE-4
1205 ms
SAM-TABA-7.0
1930 ms
XIAO-REDMI4A
1925 ms
ASUS-ZENFONE-GO16
1889 ms
LEN-A1000
1790 ms
new.gif
1534 ms
XIAO-MI6
1534 ms
SGP-I7AF360
1486 ms
LEN-A6600
1432 ms
SAM-J7P
1044 ms
rta.js
572 ms
615 ms
innity_728x90.js
129 ms
728x90.gif
493 ms
analytics.js
493 ms
heading_blue_bg.gif
493 ms
heading_blue_left.gif
1344 ms
heading_blue_right.gif
1344 ms
dot.gif
1344 ms
417 ms
optimize.innity.com
477 ms
sync
2107 ms
ttj
189 ms
ttj
557 ms
async_usersync.html
1075 ms
ga.js
904 ms
fbevents.js
2439 ms
0sTQzbapM8j.js
2315 ms
0sTQzbapM8j.js
3202 ms
like.php
2530 ms
__utm.gif
1343 ms
1878451662393304
460 ms
0zf7krTbbuX.js
962 ms
lH1ibRl5GKq.png
775 ms
collect
778 ms
129 ms
whymobile.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
whymobile.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
whymobile.com 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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whymobile.com 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 Whymobile.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.
whymobile.com
Open Graph description is not detected on the main page of Why Mobile. 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: