4.9 sec in total
245 ms
4.4 sec
293 ms
Click here to check amazing Mobile Discuss content for Hong Kong. Otherwise, check out these important facts you probably never knew about mobile.discuss.com.hk
Visit mobile.discuss.com.hkWe analyzed Mobile.discuss.com.hk page load time and found that the first response time was 245 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
mobile.discuss.com.hk performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value11.7 s
0/100
25%
Value13.6 s
2/100
10%
Value3,480 ms
2/100
30%
Value0.076
95/100
15%
Value29.2 s
0/100
10%
245 ms
218 ms
438 ms
435 ms
437 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 23% of them (23 requests) were addressed to the original Mobile.discuss.com.hk, 60% (60 requests) were made to N2.hk and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source N2.hk.
Page size can be reduced by 213.7 kB (28%)
755.1 kB
541.5 kB
In fact, the total size of Mobile.discuss.com.hk main page is 755.1 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. 30% of websites need less resources to load. Images take 440.6 kB which makes up the majority of the site volume.
Potential reduce by 39.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 5.5 kB, which is 11% 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 39.1 kB or 78% of the original size.
Potential reduce by 5.0 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. Mobile Discuss images are well optimized though.
Potential reduce by 153.5 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 153.5 kB or 63% of the original size.
Potential reduce by 16.1 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. Mobile.discuss.com.hk needs all CSS files to be minified and compressed as it can save up to 16.1 kB or 79% of the original size.
Number of requests can be reduced by 35 (38%)
92
57
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobile Discuss. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
index.php
245 ms
index_rev09.js
218 ms
common_rev09.js
438 ms
menu.js
435 ms
style_section_digital.css
437 ms
searchbox.css
435 ms
servicemenu_100716.css
444 ms
ping_ud.js
457 ms
bg.jpg
2164 ms
login.gif
651 ms
d_down.gif
652 ms
d_btn_search.gif
654 ms
logo.gif
653 ms
nav_phone_on.gif
655 ms
nav_digital.gif
866 ms
nav_computer.gif
866 ms
album_left.jpg
872 ms
album_right.jpg
871 ms
blank.gif
871 ms
all_hott.gif
1081 ms
hot_product_top.gif
1083 ms
210082_ykcrsm_1.png
1087 ms
215796_i3na2b_1.jpg
1095 ms
221274_mi0zpg_1.jpg
1086 ms
216863_haa4p6_1.png
1295 ms
221273_u2uvfa_1.jpg
1296 ms
214547_s6jlvu_1.jpg
1303 ms
new_product_top.jpg
1303 ms
221689_2ki34t_1.jpg
1310 ms
221683_alrocc_1.jpg
1511 ms
221654_ey8ggs_1.jpg
1512 ms
content_top.gif
1520 ms
content_forum_mobile_on.gif
1520 ms
content_user.gif
1527 ms
content_wifi.gif
1727 ms
content_top2.gif
1728 ms
homepage_fw.gif
1735 ms
id_605.jpg
1737 ms
newest.gif
1744 ms
id_0.jpg
1942 ms
id_102.jpg
1942 ms
id_283.jpg
1950 ms
id_403.jpg
1950 ms
button1.gif
218 ms
d_logo.gif
218 ms
c_logo.gif
219 ms
a_logo.gif
220 ms
p_logo.gif
220 ms
j_logo.gif
220 ms
25577769_8186f7.jpg
433 ms
25577089_8f5055.jpg
435 ms
25562497_85715d.jpg
436 ms
25562497_218f6c.jpg
438 ms
25562497_fcf61e.jpg
442 ms
25562497_c4e2d9.jpg
440 ms
25562497_5a3e85.jpg
646 ms
beacon.js
9 ms
atrk.js
73 ms
top_box_bg.gif
1944 ms
af_tech_lr.html
446 ms
fline.gif
574 ms
portalbox_bg.gif
573 ms
ga.js
32 ms
atrk.gif
24 ms
test.png
75 ms
__utm.gif
12 ms
collect
56 ms
ga-audiences
31 ms
adj.php
481 ms
header.gif
1727 ms
main_top.gif
1512 ms
album_top.jpg
1519 ms
album_sub.jpg
1517 ms
album_bottom.jpg
1524 ms
pause.gif
1729 ms
pause.gif
1513 ms
pause_on.gif
1517 ms
play.gif
1519 ms
play_on.gif
1523 ms
dfp_forum.php
660 ms
bquery.js
940 ms
tab_on1a.jpg
1511 ms
hott_bg.jpg
1511 ms
hot_product_bg.jpg
1515 ms
new_product_bg.jpg
1515 ms
content_top_left.gif
1514 ms
content_top_right.gif
1513 ms
content_bg.gif
1512 ms
content_bottom.gif
1507 ms
main_bottom.gif
1513 ms
rta.js
48 ms
gpt.js
5 ms
pubads_impl_81.js
6 ms
ads
234 ms
container.html
18 ms
homepage_fw.gif
1082 ms
pause.gif
448 ms
pause_on.gif
638 ms
play.gif
637 ms
play_on.gif
633 ms
mobile.discuss.com.hk accessibility score
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
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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.
mobile.discuss.com.hk 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
mobile.discuss.com.hk SEO score
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
JA
N/A
BIG5
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobile.discuss.com.hk can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Mobile.discuss.com.hk main page’s claimed encoding is big5. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
mobile.discuss.com.hk
Open Graph description is not detected on the main page of Mobile Discuss. 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: