121.4 sec in total
10.9 sec
102.5 sec
8 sec
Click here to check amazing 66 Taoba content. Otherwise, check out these important facts you probably never knew about 66taoba.com
亿康蚕丝蛋白面膜2折大促
Visit 66taoba.comWe analyzed 66taoba.com page load time and found that the first response time was 10.9 sec and then it took 110.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 115 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
66taoba.com performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value12.5 s
0/100
25%
Value17.7 s
0/100
10%
Value1,190 ms
21/100
30%
Value0.105
88/100
15%
Value11.8 s
17/100
10%
10924 ms
19730 ms
20277 ms
20277 ms
5255 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 96% of them (138 requests) were addressed to the original 66taoba.com, 1% (1 request) were made to S11.cnzz.com and 1% (1 request) were made to Oz.cnzz.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain 66taoba.com.
Page size can be reduced by 158.7 kB (58%)
273.3 kB
114.6 kB
In fact, the total size of 66taoba.com main page is 273.3 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 190.1 kB which makes up the majority of the site volume.
Potential reduce by 12.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 12.1 kB or 71% of the original size.
Potential reduce by 0 B
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. 66 Taoba images are well optimized though.
Potential reduce by 123.1 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 123.1 kB or 65% of the original size.
Potential reduce by 23.5 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. 66taoba.com needs all CSS files to be minified and compressed as it can save up to 23.5 kB or 78% of the original size.
Number of requests can be reduced by 21 (78%)
27
6
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 66 Taoba. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
66taoba.com
10924 ms
qdwap.css
19730 ms
jquery-1.7.2.min.js
20277 ms
area.js
20277 ms
jquery.cookie.js
5255 ms
time.js
1397 ms
index.css
11295 ms
jquery.js
20282 ms
time.lesser.js
10306 ms
PCASClass.js
12203 ms
ff_r1_c1.jpg
9580 ms
ff_r2_c1.jpg
17234 ms
ff_r3_c1.jpg
18657 ms
ff_r4_c1.jpg
19986 ms
dd.jpg
946 ms
goumailiucheng.jpg
4378 ms
1.jpg
19986 ms
8.jpg
10081 ms
3.jpg
19986 ms
4_r1_c1.jpg
19987 ms
4_r2_c1.jpg
19988 ms
4_r3_c1.jpg
19988 ms
4_r4_c1.jpg
19988 ms
4_r5_c1.jpg
19989 ms
4_r6_c1.jpg
19989 ms
5.jpg
19989 ms
6_r1_c1.jpg
19994 ms
6_r2_c1.jpg
19995 ms
6_r3_c1.jpg
19995 ms
6_r4_c1.jpg
19996 ms
6_r5_c1.jpg
19997 ms
6_r6_c1.jpg
19997 ms
6_r7_c1.jpg
19998 ms
6_r8_c1.jpg
19998 ms
7.jpg
20000 ms
9_r1_c1.jpg
20000 ms
9_r2_c1.jpg
20001 ms
9_r3_c1.jpg
20002 ms
9_r4_c1.jpg
20005 ms
9_r5_c1.jpg
20006 ms
10.jpg
20008 ms
11_r1_c1.jpg
20007 ms
11_r2_c1.jpg
20008 ms
11_r3_c1.jpg
20009 ms
wfdd_01.html
19992 ms
stat.php
2418 ms
11_r4_c1.jpg
19824 ms
11_r5_c1.jpg
20040 ms
stat.htm
247 ms
core.php
1427 ms
9.gif
10717 ms
pic1.gif
663 ms
12_r1_c1.jpg
19610 ms
12_r2_c1.jpg
20406 ms
12_r3_c1.jpg
19902 ms
app.gif
848 ms
12_r4_c1.jpg
19753 ms
12_r5_c1.jpg
20330 ms
13_r1_c1.jpg
13950 ms
13_r2_c1.jpg
19997 ms
13_r3_c1.jpg
19997 ms
13_r4_c1.jpg
19997 ms
13_r5_c1.jpg
19996 ms
14_r1_c1.jpg
19373 ms
14_r2_c1.jpg
19996 ms
14_r3_c1.jpg
19996 ms
14_r4_c1.jpg
19995 ms
15_r1_c1.jpg
19992 ms
15_r2_c1.jpg
19992 ms
15_r3_c1.jpg
19990 ms
15_r4_c1.jpg
19992 ms
15_r5_c1.jpg
19992 ms
15x_r1_c1.jpg
19992 ms
15x_r2_c1.jpg
19991 ms
15x_r3_c1.jpg
19991 ms
15x_r4_c1.jpg
19989 ms
15x_r5_c1.jpg
19990 ms
16_r1_c1.jpg
19990 ms
16_r2_c1.jpg
19990 ms
16_r3_c1.jpg
19987 ms
16_r4_c1.jpg
19986 ms
16_r5_c1.jpg
19986 ms
17_r1_c1.jpg
19985 ms
17_r2_c1.jpg
19985 ms
17_r3_c1.jpg
19985 ms
17_r4_c1.jpg
19984 ms
17_r5_c1.jpg
19984 ms
18.jpg
19983 ms
18x_r1_c1.jpg
19997 ms
18x_r2_c1.jpg
19996 ms
18x_r3_c1.jpg
19998 ms
18x_r4_c1.jpg
19998 ms
18x_r5_c1.jpg
20047 ms
18x2_r1_c1.jpg
9801 ms
18x2_r2_c1.jpg
10362 ms
18x2_r3_c1.jpg
19558 ms
18x2_r4_c1.jpg
19999 ms
19_r1_c1.jpg
19999 ms
19_r2_c1.jpg
20000 ms
19_r3_c1.jpg
20000 ms
19_r4_c1.jpg
19974 ms
20_r1_c1.jpg
19999 ms
20_r2_c1.jpg
20000 ms
20_r3_c1.jpg
20000 ms
20_r4_c1.jpg
19999 ms
21_r1_c1.jpg
19999 ms
21_r2_c1.jpg
19999 ms
21_r3_c1.jpg
19999 ms
22_r1_c1.jpg
20000 ms
22_r2_c1.jpg
20000 ms
22_r3_c1.jpg
20001 ms
22_r4_c1.jpg
19999 ms
23.jpg
19999 ms
24.jpg
19999 ms
25_r1_c1.jpg
19999 ms
25_r2_c1.jpg
19998 ms
25_r3_c1.jpg
19998 ms
25_r4_c1.jpg
19998 ms
26_r1_c1.jpg
19997 ms
26_r2_c1.jpg
19998 ms
26_r3_c1.jpg
19997 ms
26_r4_c1.jpg
19998 ms
27_r1_c1.jpg
19997 ms
27_r2_c1.jpg
19994 ms
27_r3_c1.jpg
19999 ms
27_r4_c1.jpg
19997 ms
29_r1_c1.jpg
19915 ms
29_r2_c1.jpg
19634 ms
29_r3_c1.jpg
20000 ms
29_r4_c1.jpg
19998 ms
30_r1_c1.jpg
19631 ms
30_r2_c1.jpg
11117 ms
30_r3_c1.jpg
12197 ms
30_r4_c1.jpg
19999 ms
30_r5_c1.jpg
18961 ms
30_r6_c1.jpg
19773 ms
31_r1_c1.jpg
19997 ms
31_r2_c1.jpg
19996 ms
31_r3_c1.jpg
19996 ms
31_r4_c1.jpg
19995 ms
31_r5_c1.jpg
19994 ms
ico1.png
19994 ms
ico2.png
19994 ms
ico3.png
19993 ms
66taoba.com accessibility score
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.
66taoba.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
66taoba.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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 doesn't use legible font sizes
N/A
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 66taoba.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that 66taoba.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.
66taoba.com
Open Graph description is not detected on the main page of 66 Taoba. 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: