18.2 sec in total
848 ms
16.9 sec
520 ms
Welcome to rhhz.net homepage info - get ready to check Rhhz best content for China right away, or after learning these important things about rhhz.net
Visit rhhz.netWe analyzed Rhhz.net page load time and found that the first response time was 848 ms and then it took 17.4 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.
rhhz.net performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value9.2 s
1/100
25%
Value16.3 s
0/100
10%
Value140 ms
95/100
30%
Value0.359
30/100
15%
Value24.4 s
0/100
10%
848 ms
2128 ms
1887 ms
1516 ms
1062 ms
Our browser made a total of 118 requests to load all elements on the main page. We found that 93% of them (110 requests) were addressed to the original Rhhz.net, 2% (2 requests) were made to Hm.baidu.com and 2% (2 requests) were made to Mathjax.xml-journal.net. The less responsive or slowest element that took the longest time to load (12.6 sec) belongs to the original domain Rhhz.net.
Page size can be reduced by 1.9 MB (43%)
4.3 MB
2.5 MB
In fact, the total size of Rhhz.net main page is 4.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. 60% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 126.9 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 46.5 kB, which is 32% 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 126.9 kB or 88% of the original size.
Potential reduce by 666.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. Obviously, Rhhz needs image optimization as it can save up to 666.2 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 822.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 822.9 kB or 76% of the original size.
Potential reduce by 243.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. Rhhz.net needs all CSS files to be minified and compressed as it can save up to 243.2 kB or 82% of the original size.
Number of requests can be reduced by 35 (31%)
114
79
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rhhz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
rhhz.net
848 ms
www.rhhz.net
2128 ms
bootstrap.min.css
1887 ms
base.css
1516 ms
media.css
1062 ms
style.css
1527 ms
head.min.js
1101 ms
jquery-3.6.3.min.js
1254 ms
template-web.js
1281 ms
dayjs.min.js
1533 ms
rhhz.js
1679 ms
logo.png
217 ms
logo2.png
224 ms
nav-arrow1.png
218 ms
tobottom.png
224 ms
bannerbg.jpg
3810 ms
wz1.png
218 ms
introduction_bg.jpg
1059 ms
introduction_com.png
1058 ms
introduction_lab.png
1279 ms
coreP.png
2357 ms
core1p.png
452 ms
core1.png
672 ms
core4p.png
901 ms
core4.png
1630 ms
core3p.png
1274 ms
core3.png
1273 ms
core2p.png
1497 ms
core2.png
1498 ms
service0.png
2761 ms
service1.jpg
1922 ms
service1_1.png
1713 ms
service2.jpg
2077 ms
service2_1.png
1939 ms
service4.jpg
2369 ms
service4_1.png
2165 ms
service3.jpg
2521 ms
service3_1.png
2380 ms
service5.jpg
3014 ms
service5_1.png
2604 ms
service6.jpg
3026 ms
service6_1.png
2740 ms
showBtn.png
2820 ms
fg.png
12576 ms
flogo.png
2977 ms
weixin2.png
3036 ms
weibo2.png
3140 ms
hm.js
1011 ms
MathJax.js
1902 ms
rh-public.js
1236 ms
rh-public.css
1243 ms
font-awesome.min.css
3024 ms
swiper.min.css
3026 ms
owl.carousel.css
3036 ms
iconfont.css
3197 ms
bootstrap.min.js
3449 ms
jquery.nicescroll.js
3426 ms
owl.carousel.js
3008 ms
jquery.colorbox.js
2735 ms
lozad.min.js
2795 ms
swiper.min.js
3678 ms
hm.gif
322 ms
mathjax-config.js
2623 ms
init.js
2967 ms
main.js
2793 ms
index.js
2804 ms
respond.js
2615 ms
base.js
3077 ms
floatwindow.js
2615 ms
article_cn.js
2538 ms
jquery.validate.js
2580 ms
user_validate.js
2468 ms
article_list.js
2730 ms
glyphicons-halflings-regular.woff
2441 ms
kongjian2.png
2434 ms
weixin3.png
2546 ms
addr.png
2431 ms
phone.png
2350 ms
email.png
2238 ms
qrcode.png
2362 ms
pic.gif
2326 ms
back_top.png
2195 ms
overlay.png
1285 ms
TeX-AMS-MML_SVG.js
2447 ms
tplData
851 ms
recommend
971 ms
push.js
1401 ms
getTodayCount
680 ms
getToken
590 ms
sowise-plugin.js
1745 ms
75296f0a-6e61-4bdd-98da-d839cd85f253.png
214 ms
cab20ade-996f-43e6-840b-b0f7892099b1.png
218 ms
c63db9e1-f860-4ee9-97a0-bb7d3ec49a17.png
213 ms
03d3d7df-1169-4e03-b18c-76377c235071.png
214 ms
e857fd33-7faa-4681-bab0-971204ffcc3d.png
359 ms
ce0a7d4d-e5bd-49a8-99a1-e5fd4adf47a9.png
423 ms
ae3b4380-7084-4c49-9c16-8a4ba99b84f5.png
423 ms
286c3975-e2ce-49bf-b8cb-44eae4fece11.png
427 ms
ecdbe87e-cb9a-403d-b8bc-433c4b8af964.png
432 ms
641054be-1940-4a51-8af9-268013b7c41e.png
573 ms
c912db72-1898-4770-a4ff-0ead577a8d35.png
636 ms
36ba3bc7-49a8-4b22-90a7-7a00e3f9ef0c.png
634 ms
60119549-b663-43ef-aaa6-ee5ff25651c5.png
645 ms
003014d3-8e5b-4636-ab3d-3a7fc8b0b9a0.png
648 ms
6e0a2a05-f494-4b33-9860-0af738ae18f2.png
789 ms
2598b0b1-cc06-4464-a29e-561ca71abe77.png
846 ms
9443f8e0-01a8-4d81-8fcf-3552d3155035.png
848 ms
158fd940-9d17-4929-87b7-c454abaec961.png
858 ms
b3c84070-cd23-4596-9cb3-884878c25ae0.png
862 ms
b607b8a1-8dd3-4eb4-b2bb-b157f2a8c2ad.png
1005 ms
e71e10ea-b4d1-4ac4-a519-827de12f8b2d.png
1325 ms
f03bbf31-53cf-4bd2-ae54-7d9c72efdc96.png
912 ms
bf33ec49-fdfd-4c95-961e-ee31c93296d7.png
1134 ms
0cdf5185-d615-4556-9123-ac34ed88f713.png
931 ms
c82bde27-a5ee-4cab-bd77-2e5a7600ae85.jpg
1284 ms
c45e03cd-eab8-4cde-b039-7fe2a9742df1.png
1542 ms
7d787397-155b-47ec-9798-71174611ceaa.jpg
1567 ms
c9b4e91f-db5f-45fc-ab49-033485be5194.jpg
1766 ms
rhhz.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.
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 IDs are not unique
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
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.
rhhz.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
rhhz.net 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
![]()
ZH
![]()
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rhhz.net can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Rhhz.net 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.
rhhz.net
Open Graph description is not detected on the main page of Rhhz. 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: