89.8 sec in total
4.4 sec
84.9 sec
401 ms
Welcome to haisan.cn homepage info - get ready to check Haisan best content right away, or after learning these important things about haisan.cn
找旅游策划、旅游景区策划、旅游规划设计公司,没有考察过【海森文旅】请勿拍板!旅游实战策划,落地设计运营。专注旅游项目策划、旅游规划设计、景区改造升级……
Visit haisan.cnWe analyzed Haisan.cn page load time and found that the first response time was 4.4 sec and then it took 85.4 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 92 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
haisan.cn performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value4.5 s
38/100
25%
Value16.5 s
0/100
10%
Value10 ms
100/100
30%
Value0
100/100
15%
Value3.1 s
95/100
10%
4447 ms
14222 ms
4115 ms
9876 ms
8724 ms
Our browser made a total of 183 requests to load all elements on the main page. We found that 70% of them (128 requests) were addressed to the original Haisan.cn, 9% (16 requests) were made to Qiao.baidu.com and 7% (12 requests) were made to P9.qiao.baidu.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain Haisan.cn.
Page size can be reduced by 597.5 kB (34%)
1.8 MB
1.2 MB
In fact, the total size of Haisan.cn main page is 1.8 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. 30% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 73.0 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 73.0 kB or 83% of the original size.
Potential reduce by 122.6 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, Haisan needs image optimization as it can save up to 122.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 344.8 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 344.8 kB or 77% of the original size.
Potential reduce by 57.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. Haisan.cn needs all CSS files to be minified and compressed as it can save up to 57.0 kB or 82% of the original size.
Number of requests can be reduced by 45 (53%)
85
40
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Haisan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
haisan.cn
4447 ms
14222 ms
common.css
4115 ms
wrapper.css
9876 ms
jquery-1.11.3.js
8724 ms
min_contentslider.js
4046 ms
jquery.SuperSlide.js
4516 ms
Marquee.js
4962 ms
utils.js
361 ms
nav.js
359 ms
index.js
403 ms
iview.fade.min.js
704 ms
jquery.easing.js
703 ms
conversion.js
26 ms
headbg.jpg
402 ms
logo.jpg
396 ms
ico_sliding.png
1141 ms
1_1607243411.jpg
20094 ms
1_0927028541.jpg
20093 ms
1_1607249692.jpg
20094 ms
1_1607249833.jpg
20096 ms
1_1607249224.jpg
20097 ms
2-151201093G2U3.jpg
12387 ms
2-15121GI2515J.jpg
20102 ms
2-151221111HJ96.jpg
20103 ms
2-15121Q01540B5.jpg
20105 ms
2-150F312054G54.jpg
20107 ms
2-15121Q04331U7.jpg
20110 ms
2-151225102923551.jpg
20111 ms
3-1411031610431E.jpg
20112 ms
1-140Z6120122Z4.jpg
20112 ms
3-141103154R4337.jpg
20112 ms
3-141223213333640.jpg
20113 ms
2-15091014414K09.jpg
20113 ms
2-151222142159247.jpg
20114 ms
2-150F21A44SH-lp.jpg
20114 ms
2-151105094Z2330.jpg
20114 ms
1-140Z1115233233.jpg
20116 ms
2-151116092033531.jpg
20115 ms
2-151123110H0P2.jpg
20116 ms
3-1412110ZK9C5.jpg
20117 ms
1-140Z3114415B4-lp.jpg
20118 ms
2-16010516191T36.jpg
20119 ms
2-150F3154A32T.jpg
20118 ms
2-150F21HZW15-lp.jpg
20119 ms
1-14091916002U95-lp.jpg
20121 ms
2-15122409304BZ.jpg
20122 ms
2-16021P9500T22.jpg
20123 ms
3-141103154050I3-lp.jpg
20124 ms
2-160203115535426.jpg
20097 ms
h.js
724 ms
3-141103153013310.jpg
19741 ms
2-1410311AH0V6.jpg
19738 ms
lxb.js
1602 ms
b.js
634 ms
analytics.js
18 ms
130 ms
stat.php
1319 ms
hm.gif
341 ms
collect
20 ms
collect
131 ms
146 ms
3-1412241216102X.jpg
19951 ms
bsl.js
901 ms
stat.htm
214 ms
core.php
842 ms
Enter.php
2125 ms
main_icon_invite_mess_api.js
2957 ms
main.css
860 ms
fix.css
720 ms
version.js
1051 ms
log.gif
392 ms
_l.js
860 ms
9.gif
1089 ms
pic1.gif
593 ms
log.gif
384 ms
1001.css
1413 ms
app.gif
1196 ms
6.png
2556 ms
close.png
526 ms
bpa.js
5622 ms
log.gif
948 ms
log.gif
1028 ms
08.jpg
2460 ms
m-webim-lite.css
385 ms
m-webim-lite.js
1482 ms
Refresh.php
581 ms
14.png
1801 ms
icon.png
730 ms
14_left.png
747 ms
14_close.png
836 ms
stat.gif
1097 ms
mess-text.png
1043 ms
messbtn.png
1637 ms
mess.gif
1402 ms
btn.png
1425 ms
bpaId
937 ms
Refresh.php
485 ms
2-15121Q12P0958.jpg
19703 ms
Refresh.php
543 ms
2-16031PUTG47.jpg
15209 ms
2-16032914435R02.jpg
8664 ms
1-140G6114922528-lp.jpg
6299 ms
1-14091F910535P-lp.jpg
9184 ms
3-14122416452L00.jpg
19401 ms
1-140Z61124102G.png
19989 ms
3-141011164H1434.jpg
19987 ms
2-16012314220U55.jpg
17560 ms
3-1412110Z53U29.jpg
16333 ms
2-16011509451B22.jpg
19982 ms
2-151130161513T3.jpg
19982 ms
1-1409201I3204K-lp.jpg
18307 ms
2-15111GF01YQ.jpg
19983 ms
2-151225140Z33S.jpg
19984 ms
2-150F21H244W9-lp.jpg
19984 ms
3-141224160Z2315.jpg
19984 ms
1-14091ZT624L4-lp.jpg
19984 ms
2-160104111PE01.jpg
19984 ms
3-14111G10625V7.jpg
19984 ms
1-140Z6113423Z1.jpg
19987 ms
2-150F3151925311.jpg
19987 ms
2-150G315392G14-lp.jpg
19987 ms
2-150F3154613615.jpg
19986 ms
2-150F3121529627.jpg
19986 ms
2-1511040933564Y.jpg
19987 ms
3-1410130ZJ31R.jpg
19986 ms
1-140Z216401c10-lp.jpg
19984 ms
2_1051216551.jpg
19985 ms
2-1512211513061b.jpg
19982 ms
1-140G6111220V9-lp.jpg
19982 ms
1_1423405731.jpg
19982 ms
2-151221112301U9.jpg
19982 ms
1_1858543483.jpg
19982 ms
1_1355354331.jpg
19979 ms
1_1635129112.jpg
20002 ms
Refresh.php
502 ms
1_1858547401.jpg
19697 ms
Refresh.php
520 ms
1_1858546994.jpg
15655 ms
1_1130061762.jpg
16659 ms
1_1635127641.jpg
13252 ms
Refresh.php
352 ms
1_1858541062.jpg
13072 ms
%E7%BE%8E%E7%9A%84%E5%9C%B0%E4%BA%A7.jpg
19645 ms
%E5%AF%8C%E7%91%9E%E9%9B%86%E5%9B%A2.jpg
14856 ms
Refresh.php
528 ms
%E6%A8%AA%E5%BA%97%E5%BD%B1%E8%A7%86%E5%9F%8E.jpg
12311 ms
%E9%B2%81%E5%95%86%E9%9B%86%E5%9B%A2.jpg
15523 ms
%E4%B8%AD%E5%9B%BD%E4%B8%AD%E9%93%81%E4%BA%8C%E5%B1%80%E9%9B%86%E5%9B%A2.jpg
15688 ms
%E6%AD%A6%E6%B1%89%E4%B8%87%E8%B1%AA%E9%9B%86%E5%9B%A2.jpg
17257 ms
%E6%81%92%E5%A4%A7%E5%9C%B0%E4%BA%A7%E9%9B%86%E5%9B%A2.png
19993 ms
%E9%A6%99%E6%B8%AF%E4%B8%AD%E6%97%85%E9%9B%86%E5%9B%A2.png
19991 ms
%E9%87%8D%E5%BA%86%E4%BA%A4%E9%80%9A%E6%97%85%E6%B8%B8%E6%8A%95%E8%B5%84%E9%9B%86%E5%9B%A2.png
19991 ms
%E9%A6%99%E6%B1%9F%E9%9B%86%E5%9B%A2.png
19992 ms
%E5%A4%A9%E7%91%9E%E9%9B%86%E5%9B%A2.png
19992 ms
%E6%9B%99%E5%85%89%E6%B1%BD%E8%BD%A6%E9%9B%86%E5%9B%A2.png
19992 ms
%E8%8B%8F%E9%AB%98%E6%96%B0%E9%9B%86%E5%9B%A2.png
19992 ms
%E4%BA%91%E5%8D%97%E6%97%85%E6%8A%95%E9%9B%86%E5%9B%A2.png
19992 ms
%E4%BA%91%E5%8D%97%E8%B7%AF%E7%BA%A2%E5%AE%9E%E4%B8%9A%E9%9B%86%E5%9B%A2.png
19991 ms
%E6%B5%99%E6%B1%9F%E5%8D%A1%E6%A3%AE%E5%9B%BD%E9%99%85.jpg
19991 ms
%E9%87%91%E9%B9%85%E9%9B%86%E5%9B%A2.png
19991 ms
qy1.gif
19990 ms
qy2.gif
19991 ms
qy3.gif
19991 ms
qy4.gif
19991 ms
qy5.gif
19992 ms
qy6.gif
19992 ms
1_0921588301.JPG
19992 ms
1_1024323581.jpg
19992 ms
titlebg.gif
19993 ms
arrow3.png
19992 ms
kuang.jpg
19992 ms
dote.gif
19991 ms
icon14.jpg
19990 ms
da1.jpg
19999 ms
Refresh.php
514 ms
indexP1bg.png
19679 ms
title2.gif
15635 ms
title.gif
15052 ms
index_focus_bg.png
19998 ms
Refresh.php
465 ms
Refresh.php
1589 ms
Refresh.php
483 ms
haisan.cn 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
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.
haisan.cn 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
Page has valid source maps
haisan.cn 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
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Haisan.cn 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 Haisan.cn 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.
haisan.cn
Open Graph description is not detected on the main page of Haisan. 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: