32.8 sec in total
3 sec
29.4 sec
422 ms
Click here to check amazing 168 W content. Otherwise, check out these important facts you probably never knew about 168w.cc
1688货源网-13-21年记录-历史百度权重4-外链超多
Visit 168w.ccWe analyzed 168w.cc page load time and found that the first response time was 3 sec and then it took 29.8 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 was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
168w.cc performance score
name
value
score
weighting
Value0.6 s
100/100
10%
Value0.6 s
100/100
25%
Value1.0 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.6 s
100/100
10%
3043 ms
915 ms
516 ms
530 ms
550 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 55% of them (85 requests) were addressed to the original 168w.cc, 8% (13 requests) were made to Cpro.baidustatic.com and 7% (11 requests) were made to Pos.baidu.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source T11.baidu.com.
Page size can be reduced by 620.2 kB (47%)
1.3 MB
704.0 kB
In fact, the total size of 168w.cc 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. 50% of websites need less resources to load. Javascripts take 690.9 kB which makes up the majority of the site volume.
Potential reduce by 106.1 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 106.1 kB or 82% of the original size.
Potential reduce by 35.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. 168 W images are well optimized though.
Potential reduce by 446.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 446.9 kB or 65% of the original size.
Potential reduce by 31.6 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. 168w.cc needs all CSS files to be minified and compressed as it can save up to 31.6 kB or 77% of the original size.
Number of requests can be reduced by 52 (35%)
147
95
The browser has sent 147 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 168 W. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
168w.cc
3043 ms
uaredirect.js
915 ms
piwYGYYqeZ.css
516 ms
style.css
530 ms
index.css
550 ms
catalog.css
544 ms
lang.js
493 ms
config.js
493 ms
jquery.js
768 ms
common.js
755 ms
page.js
762 ms
qy.js
781 ms
c.js
996 ms
slide.js
735 ms
zgd.js
247 ms
index.js
747 ms
marquee.js
744 ms
i.js
725 ms
f.js
1026 ms
f.js
1747 ms
head_bg.png
473 ms
10-55-00-46-1.jpg
1675 ms
qq_ico.jpg
711 ms
ww_ico.gif
892 ms
16-41-55-50-1.gif
923 ms
16-16-39-57-1.jpg
1398 ms
16-42-58-85-1.png
981 ms
12-04-12-95-1.gif
1671 ms
11-39-39-47-1.gif
1856 ms
15-54-47-54-1.gif
1445 ms
help.gif
1949 ms
11-41-16-15-1.jpg
4118 ms
09-27-14-59-1.jpg
3182 ms
10-47-14-40-15181.jpg.thumb.jpg
2209 ms
08-31-55-65-15181.jpg.thumb.jpg
2620 ms
17-41-36-14-0.jpg.thumb.jpg
2852 ms
750x55.gif
3473 ms
18-31-52-90-1.jpg.thumb.jpg
2600 ms
12-57-33-58-15291.jpg.thumb.jpg
3632 ms
20-22-51-48-10433.jpg.thumb.jpg
3649 ms
20-26-29-96-10433.jpg.thumb.jpg
3630 ms
10-03-15-49-10433.jpg.thumb.jpg
4191 ms
00-57-41-24-5721.jpg.thumb.jpg
4417 ms
20-40-45-84-15555.jpg.thumb.jpg
4585 ms
15-17-02-83-15563.jpg.thumb.jpg
4117 ms
14-46-51-64-15386.jpg.thumb.jpg
4503 ms
14-46-27-10-15577.jpg.thumb.jpg
4360 ms
13-56-16-19-15581.jpg.thumb.jpg
4833 ms
220x65.gif
5375 ms
16-59-05-33-1.jpg
5350 ms
16-56-33-43-1.jpg
5167 ms
15-57-31-91-1.jpg
5477 ms
15-55-11-47-1.jpg
4834 ms
15-42-30-55-1.jpg
5611 ms
ycum
3971 ms
ycum
830 ms
ycum
964 ms
blank
11 ms
15-12-43-13-1.jpg
5415 ms
stat.php
1506 ms
16-15-11-50-1.jpg
5671 ms
16-11-14-76-1.jpg
5843 ms
16-01-30-68-1.jpg
5395 ms
15-57-52-40-1.jpg
5540 ms
15-43-43-33-1.jpg
5605 ms
15-55-24-87-1.png
5892 ms
ycum
406 ms
ycum
2775 ms
15-38-55-79-1.png
5181 ms
16-23-39-69-1.jpg
5191 ms
16-19-15-24-1.jpg
5186 ms
14-59-31-23-1.jpg
5708 ms
17-00-27-30-1.png
4928 ms
14-49-56-81-1.png
5838 ms
stat.htm
197 ms
core.php
3083 ms
16-28-17-84-1.png
4667 ms
16-21-14-77-1.png
4897 ms
15-59-36-90-1.jpg
4714 ms
15-53-22-82-1.jpg
4991 ms
15-28-07-65-1.jpg
4662 ms
15-26-10-82-1.gif
4845 ms
16-44-02-35-1.jpg
4773 ms
17-21-34-18-1.jpg
4833 ms
16-34-35-71-1.jpg
5077 ms
pixel
48 ms
adx.php
1567 ms
reduce_bd-logo1_oper.png
525 ms
u=1716177312,2500053663&fm=76
5001 ms
u=923453326,2270382662&fm=76
19899 ms
u=590989199,3867807151&fm=76
11667 ms
sync.htm
565 ms
u=3118428872,3071454351&fm=76
3276 ms
pixel
16 ms
gpixel
514 ms
17-40-35-20-1.jpg
5460 ms
10-44-26-12-1.jpg
4000 ms
09-32-12-89-1.jpg
5168 ms
ycum
512 ms
ico_wap.gif
4713 ms
qy_s_bg.gif
5256 ms
spacer.gif
4210 ms
qy_menu.gif
4867 ms
sync_pos.htm
1166 ms
cpro.js
723 ms
icon_14px.png
543 ms
adx.php
1041 ms
haed_list.gif
4620 ms
qy_i_bg.gif
4736 ms
9.gif
2003 ms
hm.js
1002 ms
li_dot.gif
4621 ms
qy_cat.gif
4584 ms
box_head_bg.gif
4581 ms
closefeedback.min.js
511 ms
sync2r.htm
2465 ms
i_left.png
4060 ms
chart.png
4317 ms
hm.gif
355 ms
reduce_promotion_oper.png
487 ms
bd_logo.png
486 ms
bg_rb.png
520 ms
app.gif
1942 ms
ui
8317 ms
ycum
447 ms
ls.js
348 ms
ls_flowbar.js
382 ms
ycum
2954 ms
ycum
499 ms
home
894 ms
adx.php
3102 ms
icon_12px.png
505 ms
adx.php
991 ms
jquery_a4373ccd.js
645 ms
tpl_flowbarimgtext.js
595 ms
u=2732562711,943280703&fm=96
2193 ms
u=1414147889,2421145276&fm=96
2392 ms
arrow_left_60_e700a3bb.png
307 ms
nextprev_0d964fdd.png
278 ms
b_613fef8e.png
552 ms
u=2540860109,3209402315&fm=96
1091 ms
u=2944575757,2063077824&fm=96
6091 ms
u=2375485475,712335504&fm=96
898 ms
u=2790168706,99235444&fm=96
970 ms
ui
466 ms
cookie_iframe.html
381 ms
eye.php
2515 ms
closefeedback.min.js
581 ms
o.htm
871 ms
hm.gif
955 ms
wh.js
979 ms
ac.js
785 ms
fp.htm
457 ms
ui
438 ms
168w.cc 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
168w.cc best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
168w.cc SEO score
EN
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 168w.cc can be misinterpreted by Google and other search engines. Our service has detected that English 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 168w.cc 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.
168w.cc
Open Graph description is not detected on the main page of 168 W. 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: