27 sec in total
180 ms
16.9 sec
9.9 sec
Visit qqanhe.com now to see the best up-to-date Qqanhe content and also check out these interesting facts you probably never knew about qqanhe.com
qqanhe.com is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, qqanhe.com has it all. We hope you find what ...
Visit qqanhe.comWe analyzed Qqanhe.com page load time and found that the first response time was 180 ms and then it took 26.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
qqanhe.com performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.008
100/100
15%
Value0
0/100
10%
180 ms
446 ms
73 ms
140 ms
209 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Qqanhe.com, 43% (40 requests) were made to Img.sewozyimg.com and 10% (9 requests) were made to Bbnhj.xyz. The less responsive or slowest element that took the longest time to load (15.5 sec) relates to the external source Gif.naigou1002.top.
Page size can be reduced by 65.5 kB (13%)
516.9 kB
451.4 kB
In fact, the total size of Qqanhe.com main page is 516.9 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. 50% of websites need less resources to load. Images take 410.2 kB which makes up the majority of the site volume.
Potential reduce by 17.3 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 17.3 kB or 97% of the original size.
Potential reduce by 32.5 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. Qqanhe images are well optimized though.
Potential reduce by 4.2 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 4.2 kB or 11% of the original size.
Potential reduce by 11.4 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. Qqanhe.com needs all CSS files to be minified and compressed as it can save up to 11.4 kB or 23% of the original size.
Number of requests can be reduced by 11 (14%)
76
65
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Qqanhe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.qqanhe.com
180 ms
push.js
446 ms
common.js
73 ms
tj.js
140 ms
jlys.js
209 ms
jlys_data.php
65 ms
21348005.js
1170 ms
21443133.js
1187 ms
www.bbnhj.xyz
294 ms
bootstrap.min.css
139 ms
jquery.js
222 ms
swiper.min.css
131 ms
style.css
203 ms
white.css
136 ms
mm-content.css
136 ms
21285005.js
813 ms
21443133.js
1316 ms
92f0c144d76dd785f7c04f84ae149b33.gif
584 ms
95ca29ec3907b3bf2d8a24b35e3eda22.gif
592 ms
6fb5deabda1e984b6bd49b2baa8dfa10.gif
593 ms
ec9fcd758df74f805f29f72e8545d13b.gif
592 ms
835bbf32ebfc4e9d988f5d2f98ba1edb.gif
1392 ms
4fe2b2a7d33f4c66a1aa0bd1ae2b2824.gif
1696 ms
19b6f6f7a0104969a9685d8312488c35.gif
1386 ms
7f4326a942de44468e832f3775975026.gif
1203 ms
b8fc5ca26e9547efb1b641fd1d9065dd.gif
1386 ms
41a28e3efa3841c89761a8f637921969.gif
1248 ms
e27e16f06bd973f89ff8eb016904fb5c.gif
606 ms
03950120009rs7dn26B5E.gif
364 ms
b3e29dd487b2b.gif
1691 ms
1241242.gif
15496 ms
112.ww
190 ms
031815-80.gif
231 ms
960-160.gif
756 ms
logo.png
115 ms
0394n12000a0asaa74C95.gif
228 ms
52324facff4bd070699ce4cddb8e2c5d.gif
558 ms
64C6B5C6-A2D6-14969-34-2CA235499B78.alpha
1149 ms
hm.js
1628 ms
00D6AFAD-D8C6-18348-33-FBD7FDAC0E68.alpha
98 ms
0
2002 ms
eJPhNcDFC-InwPfQVknGM.gif
3293 ms
9689f7dc80fe4ebd91ca55e7ca4ee253.gif
1097 ms
16e2be51f887ea3432540e2b5d45fff3.jpg
558 ms
100bd534cc4944ea28792de61411b5a3.jpg
771 ms
300-200.gif
991 ms
sv
250 ms
pv.php
934 ms
bb1fb4727d6d8c2cad1fc8a47b2c37a0.jpg
649 ms
f9b448e1adaf49d4850aa813048501be.jpg
755 ms
3785d034783354ebd944180bcf63a85c.jpg
734 ms
37904de5d78438659eb948841c8bf398.jpg
729 ms
0dd6bcb786d6fc8e50edc17afac7e57b.jpg
735 ms
7fb7835ae054d910536b441b572eab0f.jpg
728 ms
7ad8172fab81746276d0fe5dd3dd154e.jpg
735 ms
eed759338243713409b86150de7e9eea.jpg
857 ms
9262d56bb710ef28a69f020da44e714b.jpg
856 ms
05745a66cc72a5d335c7b2a55cc18eeb.jpg
856 ms
daaa13bec55bfdc8f030ac3838eda5a7.jpg
856 ms
20007f4f1fa82ffd39ab3027b6e1dfb8.jpg
828 ms
69dad00129632d8977cd162d0bf22162.jpg
828 ms
e26337020741ffacdfb6558eb248d816.jpg
927 ms
f13a4f6afff0392e347f879d761d2e9b.jpg
925 ms
308a633fbce972dfab92a003d017aae3.jpg
925 ms
deeda5c3943854c0939aef090b77fb6f.jpg
925 ms
fd74e532e85435126f87457d7fa8271f.jpg
920 ms
4545e3785bada9573f6954c235164240.jpg
925 ms
256cc0e58774b663d5a00f56c5d79c5f.jpg
987 ms
09d8704665b8929db746658f23255b88.jpg
992 ms
4298f457244e3d04ef55ffaa7d55755c.jpg
993 ms
643d998641c70a45d1fffdc81e9bc610.jpg
994 ms
69927880d0e0ed442a89fe6dd23862dc.jpg
994 ms
e4606ff41fe055f30aa042c50ca5c37e.jpg
991 ms
64069da63eb965efd510f820a39df0e3.jpg
1041 ms
74d1f49867e7011e2a1b844cd6604e44.jpg
1046 ms
a5d203acdba01f48c7166ddf4fb7dd13.jpg
1043 ms
363c7da259e45f0cbdbeebf9d4f54f8c.jpg
1045 ms
621598019dc705de6c82e238e2cd8f66.jpg
1045 ms
62a1094dd0fe1650e7fd58cdf875e7e9.jpg
1043 ms
6c99e6b8693fc290cc419aa90f944495.jpg
1101 ms
8044c40e7f5f2da07985ab366882e070.jpg
1153 ms
49b92e51c05f128356d4e898e2727ba0.jpg
1154 ms
b4c1697e21f5f6a05a2976dadc83eaf8.jpg
1154 ms
446226583f32aaf36779c9c3953b6cb2.jpg
190 ms
sv
348 ms
pv.php
831 ms
font_593233_jsu8tlct5shpk3xr.woff
324 ms
e6325b2564c9b22f4fb2f614779259ed.jpg
750 ms
f4b1e944b5e42c6adfa55c94e06b9e41.jpg
565 ms
13d5a4a6b91f3f274a2b145b0963f6e0.jpg
488 ms
baac5dcbedd1e6578242f5095404e2e9.jpg
485 ms
hm.gif
399 ms
qqanhe.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
<frame> or <iframe> elements do not have a title
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
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.
qqanhe.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
qqanhe.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
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qqanhe.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 Qqanhe.com main page’s claimed encoding is . 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.
qqanhe.com
Open Graph description is not detected on the main page of Qqanhe. 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: