14.4 sec in total
802 ms
13.1 sec
566 ms
Visit 411c.com now to see the best up-to-date 411 C content for China and also check out these interesting facts you probably never knew about 411c.com
Visit 411c.comWe analyzed 411c.com page load time and found that the first response time was 802 ms and then it took 13.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
411c.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value9.7 s
0/100
25%
Value8.4 s
19/100
10%
Value20 ms
100/100
30%
Value0.003
100/100
15%
Value7.2 s
51/100
10%
802 ms
791 ms
236 ms
441 ms
662 ms
Our browser made a total of 169 requests to load all elements on the main page. We found that 75% of them (126 requests) were addressed to the original 411c.com, 12% (20 requests) were made to T.ju33.com and 4% (7 requests) were made to Xplian.com. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source S6.xplian.com.
Page size can be reduced by 363.5 kB (12%)
3.1 MB
2.7 MB
In fact, the total size of 411c.com main page is 3.1 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. 55% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 46.2 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 8.2 kB, which is 15% 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 46.2 kB or 84% of the original size.
Potential reduce by 221.4 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. 411 C images are well optimized though.
Potential reduce by 79.5 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 79.5 kB or 61% of the original size.
Potential reduce by 16.3 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. 411c.com needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 79% of the original size.
Number of requests can be reduced by 30 (18%)
167
137
The browser has sent 167 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 411 C. 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 as a result speed up the page load time.
411c.com
802 ms
www.411c.com
791 ms
mm.css
236 ms
litfocus.css
441 ms
jquery_litfocus.js
662 ms
litfocus.js
447 ms
232x152.js
450 ms
960x90c.js
466 ms
960x90b.js
1164 ms
fumeiti1.js
654 ms
tongji.js
688 ms
1305550079-Njn8EY.jpg
233 ms
m_4.gif
220 ms
m_3.gif
219 ms
but1.gif
221 ms
m_6.gif
221 ms
m_16.gif
437 ms
navnbg.gif
439 ms
0-TXffXy.jpg
1547 ms
0-4hJK7X.jpg
1994 ms
0-i7LbTj.jpg
1632 ms
0-0mjK7a.jpg
1975 ms
0-AZlWUG.jpg
1758 ms
0-HF6StI.jpg
4462 ms
0-TXffXy.jpg
1768 ms
0-4hJK7X.jpg
1864 ms
0-i7LbTj.jpg
1980 ms
0-0mjK7a.jpg
1990 ms
0-AZlWUG.jpg
2097 ms
0-HF6StI.jpg
2416 ms
m_24.gif
2641 ms
0-EN6z5a.jpg
2212 ms
0-0vd5nv.jpg
2439 ms
0-7ygT0W.jpg
2332 ms
0-OoPy7i.jpg
2433 ms
0-LT69SP.jpg
2566 ms
0-NVYxFQ.jpg
3071 ms
0-KJ0FVX.jpg
2654 ms
0-7uhBT3.jpg
2881 ms
0-z2UcA7.jpg
3703 ms
0-UbTXxD.jpg
3519 ms
n_3.jpg
2874 ms
n_5.jpg
3963 ms
m_73.gif
3104 ms
0-LT69SP.jpg
4470 ms
0-vQSMpY.jpg
3531 ms
a.js
1078 ms
0-yP6qIe.jpg
3742 ms
0-rBHyqV.jpg
3999 ms
0-zf4OXW.jpg
4225 ms
0-tMoh8W.jpg
4183 ms
0-UYy6TJ.jpg
4618 ms
0-tGiuxc.jpg
4440 ms
0-JeavOC.jpg
4622 ms
m_68.gif
4190 ms
s.php
1640 ms
s.php
1833 ms
s.php
1822 ms
showpic.html
1730 ms
b.js
373 ms
analytics.js
4 ms
collect
13 ms
0-gkRR1I.jpg
3149 ms
0-4AUb6k.jpg
3286 ms
s.php
1205 ms
0-rw1YAs.jpg
3617 ms
0-rj1e2S.jpg
3161 ms
n_9.jpg
3431 ms
m1_9.jpg
3127 ms
0-AkyjOw.jpg
3377 ms
0-m8dWA5.jpg
3175 ms
0-icKa5y.jpg
3508 ms
0-5Lct1H.jpg
3668 ms
0-kFVjnO.jpg
3188 ms
n_12.jpg
3401 ms
0-PGnGYI.jpg
4255 ms
0-qoRw37.jpg
3875 ms
0-YO3eFI.jpg
3194 ms
0-T8XgiG.jpg
3373 ms
0-c9lQF1.jpg
3228 ms
0-rMyZua.jpg
3743 ms
public.css
366 ms
userpic.js
339 ms
globlepic.js
672 ms
makepic.js
2056 ms
kwpic.asp
889 ms
0-biV00m.jpg
3377 ms
0-SYFsli.jpg
3226 ms
c.js
527 ms
0-P0V13v.jpg
3308 ms
0-2i7bco.jpg
3235 ms
7.gif
2506 ms
1.gif
724 ms
11.gif
1076 ms
6.gif
1365 ms
2.gif
1366 ms
4.gif
1407 ms
2.gif
1089 ms
6.gif
1434 ms
2.gif
1456 ms
2.gif
1816 ms
6.gif
3051 ms
u_lm35189952.js
666 ms
0-DxkklW.jpg
3174 ms
0-cWsl2T.jpg
3693 ms
m_96_.gif
2870 ms
kw13.js
337 ms
0-LSb1uX.jpg
2860 ms
0-1cq2m6.jpg
2875 ms
0-AyT94c.jpg
3264 ms
0-8mby5v.jpg
2491 ms
n_14.jpg
2477 ms
0-UwSqSf.jpg
2799 ms
0-t6FAUg.jpg
2804 ms
0-Q8c2YP.jpg
2438 ms
0-yOdXQm.jpg
2667 ms
0-IKhGHH.jpg
2485 ms
0-5pYJMn.jpg
3498 ms
n_17.jpg
2788 ms
xplian1048.jpg
1753 ms
xplian1014.jpg
1714 ms
xplian1001.jpg
1785 ms
xplian1062.jpg
1856 ms
xplian1011.jpg
4580 ms
xplian1032.jpg
4977 ms
xplian1015.jpg
2840 ms
stat.php
599 ms
0-KJ0FVX.jpg
4786 ms
0-WWBHXx.jpg
2493 ms
0-lfLJOx.jpg
2926 ms
0-9LQN8C.jpg
3483 ms
0-ghSF5S.jpg
2479 ms
0-mSeeok.jpg
3006 ms
0-r3aEhc.jpg
2621 ms
0-9eFS5I.jpg
2818 ms
0-KiQyfg.jpg
2968 ms
stat.htm
167 ms
core.php
723 ms
0-KtjumB.jpg
2803 ms
0-LhP0EL.jpg
3069 ms
0-UueHmI.jpg
4006 ms
m_108_.gif
2787 ms
0-uaqhFj.jpg
2974 ms
0-Q2AjhH.jpg
3278 ms
0-CfKffN.jpg
2624 ms
0-7a46eo.jpg
2935 ms
n_19.jpg
3400 ms
0-q0fAkG.jpg
3198 ms
0-KrPjMo.jpg
3285 ms
0-q4tlIP.jpg
3749 ms
0-59z2rW.jpg
3576 ms
0-wowUk4.jpg
3648 ms
0-Tt9MeY.jpg
3557 ms
m_112.gif
3124 ms
bannerPoint.gif
3262 ms
m1_3.jpg
3243 ms
cen1_bg.jpg
3156 ms
cen1_right_bg.jpg
3422 ms
cen1_left_bg.jpg
3272 ms
bj01.gif
3227 ms
bj02.gif
3229 ms
bj03.gif
3118 ms
m_113.gif
3064 ms
m_116.gif
3086 ms
5.gif
1324 ms
7.gif
2222 ms
5.gif
361 ms
1.gif
2539 ms
3.gif
913 ms
411c.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
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
411c.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
411c.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 411c.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 411c.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.
411c.com
Open Graph description is not detected on the main page of 411 C. 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: