43.1 sec in total
383 ms
41.2 sec
1.5 sec
Visit safe.baihe.com now to see the best up-to-date Safe Baihe content for United States and also check out these interesting facts you probably never knew about safe.baihe.com
百合网安全交友中心教你如何避免骗财骗色
Visit safe.baihe.comWe analyzed Safe.baihe.com page load time and found that the first response time was 383 ms and then it took 42.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 9 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
safe.baihe.com performance score
name
value
score
weighting
Value4.5 s
14/100
10%
Value10.9 s
0/100
25%
Value9.6 s
11/100
10%
Value550 ms
54/100
30%
Value0.043
99/100
15%
Value13.0 s
13/100
10%
383 ms
4133 ms
1022 ms
1831 ms
2128 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 5% of them (4 requests) were addressed to the original Safe.baihe.com, 16% (12 requests) were made to Images4.baihe.com and 13% (10 requests) were made to Images1.baihe.com. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Images4.baihe.com.
Page size can be reduced by 268.7 kB (46%)
589.4 kB
320.7 kB
In fact, the total size of Safe.baihe.com main page is 589.4 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 259.1 kB which makes up the majority of the site volume.
Potential reduce by 30.5 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 30.5 kB or 74% of the original size.
Potential reduce by 8.7 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. Safe Baihe images are well optimized though.
Potential reduce by 155.3 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 155.3 kB or 78% of the original size.
Potential reduce by 74.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. Safe.baihe.com needs all CSS files to be minified and compressed as it can save up to 74.2 kB or 83% of the original size.
Number of requests can be reduced by 23 (34%)
67
44
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Safe Baihe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
index.html
383 ms
public.css
4133 ms
safeCenter_v1.css
1022 ms
pop.css
1831 ms
tongji-1.0.1.min.js
2128 ms
jquery-1.8.3.min.js
19898 ms
baihe.js
6184 ms
BHHead.js
4794 ms
BHFooter.js
2438 ms
jquery.blockUI-2.42.js
4091 ms
popup.js
3031 ms
ntkfstat.js
1705 ms
loginByUserID
872 ms
safeTop.jpg
19984 ms
safeTel.jpg
1633 ms
mainTop.gif
2090 ms
pic04.jpg
2864 ms
pic08.jpg
3616 ms
pic12.jpg
2056 ms
6_online.gif
792 ms
pic05.jpg
2498 ms
pic06.jpg
2458 ms
pic07.jpg
19973 ms
pic17.jpg
2547 ms
pic16.jpg
4243 ms
pic18.jpg
2885 ms
rightTop.gif
2905 ms
rightBottom.gif
3028 ms
pic20130730.jpg
7077 ms
pic01.jpg
19937 ms
pic02.jpg
19936 ms
pic03.jpg
19935 ms
rightBottom.gif
2059 ms
rightTop.gif
2085 ms
pic13.jpg
2677 ms
mainBottom.gif
2011 ms
rightTop.gif
4043 ms
icon_01.gif
2012 ms
pic09.jpg
3806 ms
pic10.jpg
3842 ms
pic11.jpg
3601 ms
ad01.jpg
5130 ms
mainTop.gif
1383 ms
mainBottom.gif
19930 ms
pic14.jpg
1422 ms
newsPic1.jpg
2004 ms
newsPic2.jpg
2006 ms
newsPic3.jpg
2145 ms
newsPic4.jpg
3523 ms
head.gif
19924 ms
nav_code.gif
1380 ms
logo.gif
19909 ms
nav_bj_r.gif
1439 ms
nav_icon.gif
1442 ms
rightCenter.gif
2407 ms
safeDown.gif
2484 ms
mainCenter.gif
3268 ms
safeIcon.gif
2583 ms
icon_02.gif
2928 ms
icon_01a.gif
3302 ms
h.js
921 ms
tongduntoken.js
418 ms
ntkfstat.js
4257 ms
logo_footer.gif
3652 ms
clear.png
2419 ms
fm.js
658 ms
hm.gif
420 ms
logoInter.gif
648 ms
profile.json
1956 ms
t7.baihe.com
1039 ms
ntkfstat.js
5280 ms
atrk.js
112 ms
batch.html.php
2721 ms
loading.gif
713 ms
atrk.gif
100 ms
test.png
86 ms
index.php
4633 ms
safe.baihe.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
Links do not have a discernible name
safe.baihe.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
safe.baihe.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
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Safe.baihe.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 Safe.baihe.com 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.
safe.baihe.com
Open Graph description is not detected on the main page of Safe Baihe. 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: