8.9 sec in total
697 ms
7.8 sec
448 ms
Visit ruian.com now to see the best up-to-date Ruian content for China and also check out these interesting facts you probably never knew about ruian.com
域名得天独厚,创办于1999年,是瑞安门户网站,人气旺盛,功能丰富,旗下『瑞安论坛』拥有瑞安说事、吹水泡泡、求职招聘等热门版块,更是瑞安市民交流的重要平台。
Visit ruian.comWe analyzed Ruian.com page load time and found that the first response time was 697 ms and then it took 8.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ruian.com performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value11.1 s
0/100
25%
Value9.6 s
11/100
10%
Value30 ms
100/100
30%
Value0.006
100/100
15%
Value7.6 s
46/100
10%
697 ms
1504 ms
479 ms
891 ms
696 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 76% of them (96 requests) were addressed to the original Ruian.com, 16% (20 requests) were made to Img3.ruian.com and 9% (11 requests) were made to Bbs.ruian.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Img3.ruian.com.
Page size can be reduced by 378.1 kB (29%)
1.3 MB
942.0 kB
In fact, the total size of Ruian.com main page is 1.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. 55% of websites need less resources to load. Images take 852.3 kB which makes up the majority of the site volume.
Potential reduce by 80.2 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 80.2 kB or 80% of the original size.
Potential reduce by 38.9 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. Ruian images are well optimized though.
Potential reduce by 179.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 179.9 kB or 67% of the original size.
Potential reduce by 79.0 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. Ruian.com needs all CSS files to be minified and compressed as it can save up to 79.0 kB or 79% of the original size.
Number of requests can be reduced by 34 (28%)
120
86
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ruian. 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.
ruian.com
697 ms
www.ruian.com
1504 ms
style_1_common.css
479 ms
style.css
891 ms
res_Focus.js
696 ms
common.js
1159 ms
portal.js
700 ms
logging.js
714 ms
md5.js
717 ms
jquery.min.js
1389 ms
guide-septAct.css
934 ms
guidetool.js
952 ms
ggcss.css
472 ms
jquery-3.4.1.min.js
1200 ms
ggcss.css
728 ms
background.png
1116 ms
c9d12bcf9985ca643603d379b8369a70.jpg
1260 ms
580278494c9b10b47824d81661e95d33.jpg
1085 ms
4d9fb69b637503b8d3525ba7f4d3ef77.jpg
1302 ms
c60ea21e5efd94fee89d6072aeed0c32.jpg
1143 ms
2cfb11ffa69739870a2a27a4eee5f111.jpg
1163 ms
64b4b91d6eb468bcf5318640853e8b47.jpg
1197 ms
be3dd253a363b154b268e9bc92cb8953.jpg
1291 ms
64d911a02a7ae44404633dbd21a340c9.jpg
1356 ms
02446276661753d27caf8dfaf49ec720.jpg
1377 ms
9a6fe5273dab6728a1992e189f5de677.jpg
1422 ms
b095667a3d803772f7358f5ea68ad514.jpg
1451 ms
e73322796b2fc6b9b0dfdbd558f03595.jpg
1499 ms
fb716442f344b23d30ed2063966c9699.jpg
1497 ms
7cc85d997a16d9065c64ffd83d1288a1.jpg
1580 ms
544c544f2f5f7935017fd9cdb63cce61.jpg
1589 ms
48e816663dd9702216f6f50b7ae9a13d.jpg
1647 ms
a4b01ae63d984b11c5a41a2c3796104e.jpg
1647 ms
ad7cd97d5f44f143e6e7b98d69643c3f.jpg
1692 ms
8f3b00020245d8bbaf90e558ccbbea57.jpg
1696 ms
dee570c2ebb9fa0fdcf8434988837897.jpg
2011 ms
qmenu.png
1158 ms
qq_login.gif
236 ms
tyjr_960x60.jpg
704 ms
job_960x60_.gif
713 ms
logo_portal.png
242 ms
zp_780x75.gif
674 ms
a1-3-3.gif
272 ms
jd_954x80.gif
451 ms
img8.jpg
480 ms
270x180.gif
499 ms
nsh_954x60.jpg
914 ms
06152540bac694bcc86309_176_120.jpg
727 ms
061025220e7e4771500642_176_120.jpg
738 ms
0611111539d705b0748036_176_120.jpg
896 ms
1111111111111111111.jpg
937 ms
2222222222222222222.jpg
950 ms
3333333333333333333.jpg
961 ms
3806823_103755468313_2.jpg
976 ms
5086922_105037667112_2.jpg
1119 ms
union-icon.gif
449 ms
jzsite.jpg
1376 ms
beian.png
1170 ms
end_lnk5.gif
1188 ms
end_lnk1.gif
1193 ms
end_lnk6.png
1213 ms
end_lnk9.jpg
1342 ms
end_lnk8.jpg
1406 ms
px.png
1133 ms
pn.png
1150 ms
bg.png
1198 ms
logo_portal.png
1191 ms
wlwm_960x403.jpg
1614 ms
cjy_mainnav.png
472 ms
cjy_mainnav.png
931 ms
daohang.png
1067 ms
search.png
1124 ms
close_big.png
1205 ms
leftbottom.png
244 ms
arr1.gif
1298 ms
boxbg1.gif
1309 ms
line1.gif
1341 ms
boxh3.gif
1364 ms
boxh1.gif
1360 ms
boxh4.gif
1391 ms
boxh2.gif
1490 ms
boxbg2.gif
1539 ms
boxh22.gif
1576 ms
scrolltop.png
976 ms
boxh23.gif
1447 ms
union-icon.gif
1455 ms
ico10.gif
1454 ms
leftbottom.png
1524 ms
line2.gif
1577 ms
lsIco.gif
1442 ms
rdlpIco.gif
1429 ms
fwcsHbg.gif
1434 ms
cjy_mainnav.png
680 ms
boxh8.gif
1446 ms
boxh7.gif
1502 ms
ico5.gif
1412 ms
mshdIco.gif
1436 ms
boxh9.gif
1427 ms
boxh11.gif
1432 ms
boxh10.gif
1450 ms
ico6.gif
1486 ms
boxbg4.gif
1421 ms
boxh16.gif
1413 ms
boxh17.gif
1409 ms
ico8.gif
1426 ms
xqIco.gif
1434 ms
boxh18.gif
1343 ms
boxh19.gif
1397 ms
boxh20.gif
1410 ms
ico9.gif
1404 ms
qzIco.gif
1429 ms
boxh21.gif
1437 ms
boxh5.gif
1344 ms
boxh6.gif
1399 ms
ico4.gif
1412 ms
style.css
1404 ms
shIco.gif
1433 ms
lyIco.gif
1437 ms
boxh27.gif
1343 ms
boxh24.gif
1401 ms
boxh25.gif
1410 ms
ico11.gif
1404 ms
rcIco.gif
1433 ms
jyIco.gif
1438 ms
zpIco.gif
1344 ms
boxh26.gif
1401 ms
leftbottom.png
1408 ms
ruian.com 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
Form elements do not have associated labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
ruian.com 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
ruian.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
ZH
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ruian.com 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 Ruian.com main page’s claimed encoding is gbk. 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.
ruian.com
Open Graph description is not detected on the main page of Ruian. 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: