67.8 sec in total
10.5 sec
56.9 sec
351 ms
Click here to check amazing 136136 content for China. Otherwise, check out these important facts you probably never knew about 136136.com
Visit 136136.comWe analyzed 136136.com page load time and found that the first response time was 10.5 sec and then it took 57.3 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. Unfortunately, there were 23 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
136136.com performance score
name
value
score
weighting
Value3.9 s
26/100
10%
Value5.7 s
16/100
25%
Value8.5 s
17/100
10%
Value110 ms
97/100
30%
Value0.006
100/100
15%
Value7.8 s
45/100
10%
10549 ms
5365 ms
1358 ms
857 ms
1290 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 88% of them (106 requests) were addressed to the original 136136.com, 4% (5 requests) were made to Bdimg.share.baidu.com and 2% (3 requests) were made to Combo.b.qq.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain 136136.com.
Page size can be reduced by 213.0 kB (30%)
715.7 kB
502.7 kB
In fact, the total size of 136136.com main page is 715.7 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. 25% of websites need less resources to load. Images take 435.1 kB which makes up the majority of the site volume.
Potential reduce by 87.4 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 12.2 kB, which is 11% 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 87.4 kB or 82% of the original size.
Potential reduce by 44.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. 136136 images are well optimized though.
Potential reduce by 62.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 62.3 kB or 42% of the original size.
Potential reduce by 18.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. 136136.com needs all CSS files to be minified and compressed as it can save up to 18.4 kB or 76% of the original size.
Number of requests can be reduced by 34 (36%)
95
61
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 136136. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
136136.com
10549 ms
index2011new.css
5365 ms
main_style.css
1358 ms
select_style.css
857 ms
patch_style.css
1290 ms
jquery.js
12724 ms
css.css
1286 ms
cg_reset.css
2600 ms
photo.css
3034 ms
mainpage2010.js
2371 ms
jquery-1.2.6.pack.js
6906 ms
base.js
8890 ms
sea_select.js
3497 ms
change_images.js
5951 ms
dlu.js
6099 ms
swfobject.js
8498 ms
wpa.php
800 ms
296495.js
6751 ms
tooltip.js
20347 ms
top_bj.jpg
481 ms
20151016135346.jpg
19697 ms
logo.jpg
957 ms
menu_hover.jpg
388 ms
menu_link.jpg
382 ms
new_ico.gif
784 ms
menu_bj.jpg
791 ms
sea_input.jpg
2473 ms
sea_btn.jpg
1564 ms
tel.jpg
1185 ms
dian.gif
4834 ms
20160408103020.jpg
1571 ms
20151113095803.jpg
3177 ms
20160404104623.jpg
1959 ms
20160329112733.jpg
2345 ms
20160325103005.jpg
2731 ms
20131101174938.jpg
4373 ms
20160311201624.jpg
4286 ms
20160317200202.jpg
4785 ms
20150910191436.jpg
5394 ms
20150910184344.jpg
4848 ms
20150820165812.jpg
6385 ms
20151213102646.jpg
5307 ms
20150820163554.jpg
5801 ms
20150910184938.jpg
5784 ms
20150410164549.jpg
5779 ms
20140917101220.jpg
6545 ms
20151107112722.jpg
6262 ms
20151007101826.jpg
6276 ms
20110504113019.gif
13604 ms
20160406092901.jpg
6752 ms
20160408101410.jpg
9282 ms
20160408095755.jpg
7312 ms
20160408100902.jpg
11423 ms
20110603170721.jpg
7687 ms
Panel.js
892 ms
localStorage.js
928 ms
20110908114342.jpg
7720 ms
20110607143012.jpg
8487 ms
20110616210106.jpg
15945 ms
20110614125926.jpg
9654 ms
20110601132434.jpg
10397 ms
20110603140054.jpg
11008 ms
contains.js
973 ms
20110601150533.jpg
11196 ms
20110602114006.jpg
12397 ms
20130115150841.jpg
16456 ms
20130115140934.jpg
14482 ms
r.cgi
2332 ms
ta.php
588 ms
crmqq.php
19689 ms
wpa_first_heart_beat.php
1583 ms
20140528115144.jpg
16599 ms
20140528114314.jpg
20220 ms
20140528114217.jpg
16587 ms
icon_0.gif
772 ms
20140528114040.jpg
19512 ms
20140528113953.jpg
20405 ms
20140527102908.jpg
17449 ms
20140527102824.jpg
19669 ms
20140527102730.jpg
19864 ms
20140527102628.jpg
18016 ms
20110617223836.jpg
19282 ms
20110602220410.jpg
19222 ms
20110606225910.jpg
19148 ms
yqlj.jpg
19175 ms
20121204105616.jpg
19884 ms
20110316123418.gif
20422 ms
20110215134003.jpg
19061 ms
20110222221756.jpg
19334 ms
20110316122950.gif
20140 ms
20110426090234.gif
19933 ms
20121204093834.jpg
20370 ms
20121204162408.jpg
19981 ms
20121204164904.jpg
19593 ms
20121204165513.jpg
19821 ms
20121225084530.jpg
19373 ms
20121227220428.jpg
20257 ms
20140826174001.jpg
19506 ms
20150727234235.jpg
18177 ms
top.jpg
18099 ms
lm_bj1.jpg
20310 ms
lm_bj11.jpg
20081 ms
111.jpg
19733 ms
lm_bj3.jpg
18688 ms
lm_bj2.jpg
18200 ms
shell_v2.js
547 ms
red_qiu.jpg
18398 ms
logger.js
226 ms
bds_s_v2.js
672 ms
bdsstyle.css
280 ms
r0.gif
257 ms
news_bj.jpg
19663 ms
bar.jpg
16648 ms
icon.png
20373 ms
sicon.png
17155 ms
tit_inner.png
15496 ms
photo_bg.jpg
14855 ms
photo.jpg
20001 ms
li_bg.jpg
15156 ms
yqlj_bj.jpg
14041 ms
select_bj.jpg
14050 ms
136136.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
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
136136.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
136136.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 136136.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 136136.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.
136136.com
Open Graph description is not detected on the main page of 136136. 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: