22.8 sec in total
642 ms
21.8 sec
343 ms
Welcome to hmus.net homepage info - get ready to check Hmus best content for Hong Kong right away, or after learning these important things about hmus.net
??缇?蹇??????婚?ㄤ?浜?缇??界航绾︼?浠?搴??㈢Н33000骞虫?硅?卞昂锛?涓虹?涓??板?虹?版????澶х????浜哄揩??浠?搴?锛?骞朵??ㄥ痉????锛?delaware锛???绋?宸??ユ??17000灏虹??瓒?澶у??浠?搴???杩??ラ?㈢Н杈惧??0000?卞昂.涓昏?缁??ョ??借?充腑?藉ぇ????棣?娓????版咕绌鸿??ㄥ?伴?ㄧ???╂????????...
Visit hmus.netWe analyzed Hmus.net page load time and found that the first response time was 642 ms and then it took 22.1 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.
hmus.net performance score
name
value
score
weighting
Value1.1 s
99/100
10%
Value3.5 s
64/100
25%
Value1.8 s
100/100
10%
Value140 ms
96/100
30%
Value0
100/100
15%
Value5.5 s
71/100
10%
642 ms
618 ms
184 ms
191 ms
80 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 75% of them (47 requests) were addressed to the original Hmus.net, 5% (3 requests) were made to Combo.b.qq.com and 3% (2 requests) were made to Wpa.b.qq.com. The less responsive or slowest element that took the longest time to load (15.2 sec) relates to the external source Tajs.qq.com.
Page size can be reduced by 320.0 kB (46%)
702.1 kB
382.1 kB
In fact, the total size of Hmus.net main page is 702.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. 25% of websites need less resources to load. Images take 557.6 kB which makes up the majority of the site volume.
Potential reduce by 26.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. 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.1 kB or 70% of the original size.
Potential reduce by 262.1 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, Hmus needs image optimization as it can save up to 262.1 kB or 47% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 26.6 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 26.6 kB or 26% of the original size.
Potential reduce by 5.2 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. Hmus.net needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 78% of the original size.
Number of requests can be reduced by 27 (50%)
54
27
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hmus. 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.
hmus.net
642 ms
main.css
618 ms
jquery.js
184 ms
main.js
191 ms
qq.js
80 ms
bg.gif
112 ms
topbg.gif
110 ms
logo.jpg
566 ms
top.jpg
570 ms
bt0.jpg
509 ms
bt11.jpg
288 ms
bt22.jpg
872 ms
bt33.jpg
509 ms
bt44.jpg
393 ms
bt88.jpg
481 ms
bt55.jpg
555 ms
bt66.jpg
590 ms
bt77.jpg
590 ms
image0.jpg
762 ms
tright.gif
650 ms
regist.gif
659 ms
title_yd.gif
672 ms
ydsearch.jpg
671 ms
verifycode_search.aspx
779 ms
search.gif
778 ms
title_news.gif
784 ms
title_bd.gif
785 ms
20130316101635191.png
856 ms
20120618032001031.gif
867 ms
20120626090005317.jpg
865 ms
20120626090032426.jpg
861 ms
20120626090118254.jpg
860 ms
20130317012510179.jpg
926 ms
logobt.jpg
1396 ms
btline.gif
936 ms
time0.asp
895 ms
VerifyCode.aspx
896 ms
login.gif
895 ms
Point_line_01.gif
953 ms
bottombg.gif
956 ms
z_stat.php
1338 ms
39297.js
75 ms
bg.gif
81 ms
wpa.php
1120 ms
qqtop.png
88 ms
index_31.gif
80 ms
stat.htm
321 ms
core.php
1466 ms
qqbo.gif
78 ms
9.gif
3811 ms
pic.gif
614 ms
VerifyCode.aspx
102 ms
wpa.php
604 ms
verifycode_search.aspx
137 ms
Panel.js
732 ms
localStorage.js
1788 ms
contains.js
267 ms
r.cgi
1100 ms
r.cgi
1094 ms
ta.php
592 ms
crmqq.php
15247 ms
wpa_first_heart_beat.php
1728 ms
app.gif
1013 ms
hmus.net 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
hmus.net 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
hmus.net SEO score
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
ZH
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hmus.net can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Hmus.net main page’s claimed encoding is gb2312. 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.
hmus.net
Open Graph description is not detected on the main page of Hmus. 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: