101.4 sec in total
16.7 sec
83.8 sec
924 ms
Visit fblife.com now to see the best up-to-date Fblife content for United States and also check out these interesting facts you probably never knew about fblife.com
越野e族为您提供最新最专业的越野车及SUV动态,新车资讯,越野车SUV评测,汽车改装咨询,是中国越野车、SUV、越野、改装、旅行、赛事领域第一媒体与互动中心,路越远?心越近,越野e族。
Visit fblife.comWe analyzed Fblife.com page load time and found that the first response time was 16.7 sec and then it took 84.7 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 69 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
fblife.com performance score
16658 ms
4756 ms
3170 ms
20251 ms
3197 ms
Our browser made a total of 174 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Fblife.com, 57% (99 requests) were made to Img10.fblife.com and 22% (38 requests) were made to Static.fblife.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Img10.fblife.com.
Page size can be reduced by 7.1 MB (31%)
22.6 MB
15.5 MB
In fact, the total size of Fblife.com main page is 22.6 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. 35% of websites need less resources to load. Images take 15.3 MB which makes up the majority of the site volume.
Potential reduce by 1.4 MB
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 259.6 kB, which is 17% 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 1.4 MB or 89% of the original size.
Potential reduce by 1.2 MB
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. Fblife images are well optimized though.
Potential reduce by 2.6 MB
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 2.6 MB or 75% of the original size.
Potential reduce by 1.9 MB
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. Fblife.com needs all CSS files to be minified and compressed as it can save up to 1.9 MB or 84% of the original size.
Number of requests can be reduced by 32 (31%)
103
71
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fblife. 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 as a result speed up the page load time.
fblife.com
16658 ms
common.css
4756 ms
advert.css
3170 ms
min.js
20251 ms
jquery.easing.min.js
3197 ms
index.js
7400 ms
advert.js
5432 ms
userlogin.js
4902 ms
search.js
5199 ms
brandData.js
826 ms
seriesData.js
1377 ms
like.js
6167 ms
816 ms
812 ms
817 ms
815 ms
496 ms
518 ms
966 ms
645 ms
646 ms
341 ms
241 ms
479 ms
479 ms
489 ms
512 ms
553 ms
cert.js
20437 ms
certShow
4625 ms
z_stat.php
2122 ms
stats
7730 ms
1460113322.jpg
14630 ms
14600757998163.jpg
15066 ms
14600827954519.jpg
19981 ms
14600769903930.jpg
14413 ms
14600491742097.jpg
11653 ms
1460076855.jpg.300x200.jpg
18921 ms
1459820417.jpg.300x200.jpg
19981 ms
1460017862.jpg.120x80.jpg
19982 ms
1459388227.jpg.120x80.jpg
19220 ms
1457495596.jpg.300x200.jpg
16405 ms
1452483382.jpg.300x200.jpg
19982 ms
1460100293.jpg.180x120.jpg
19983 ms
1460097619.jpg.180x120.jpg
19984 ms
1460086640.jpg.180x120.jpg
19983 ms
1460085769.jpg.180x120.jpg
19984 ms
1460001546.jpg.180x120.jpg
19984 ms
1460000678.jpg.180x120.jpg
19985 ms
1459997542.jpg.180x120.jpg
19984 ms
1459998956.jpg.180x120.jpg
19985 ms
1459998887.jpg.180x120.jpg
19985 ms
1459937475.jpg.180x120.jpg
19986 ms
1460082538.jpg.339x317.jpg
19986 ms
1459993653.jpg.339x226.jpg
19986 ms
1459921951.jpg.339x226.jpg
19986 ms
1459906603.jpg.339x226.jpg
19987 ms
1459907252.jpg.339x226.jpg
19986 ms
1459828783.jpg.339x226.jpg
19986 ms
1459822211.jpg.339x226.jpg
19987 ms
1459474758.jpg.339x317.jpg
19987 ms
1459474216.jpg.339x226.jpg
19987 ms
1459391624.jpg.339x226.jpg
19987 ms
1459387562.jpg.339x226.jpg
19988 ms
1459321673.jpg.339x226.jpg
19988 ms
1459219389.jpg.339x226.jpg
19989 ms
1459218562.jpg.339x226.jpg
19988 ms
1459158956.jpg.339x317.jpg
19989 ms
b_ico.png
19989 ms
icon7-ezu.png
4924 ms
icon7-weixin.png
19989 ms
icon7-oldcar.png
6129 ms
ico_xq.png
1118 ms
zgqc.png
6695 ms
pinpai.png
3790 ms
imgloading.jpg
6070 ms
xyqy.jpg
19988 ms
cnnic.png
7215 ms
jyxwz.png
10650 ms
db_logo.jpg
8968 ms
nav_bg.gif
9588 ms
ico_xq01.png
19973 ms
493 ms
489 ms
dotted.png
10061 ms
dots.jpg
10710 ms
504 ms
b_ico.png
19624 ms
replay.png
12893 ms
opacity.png
13481 ms
b_fblog.jpg
14026 ms
b_gylog.jpg
18124 ms
icon_a.png
18647 ms
icon_b.png
19206 ms
icon_c.png
19564 ms
la.jpg
19564 ms
lb.jpg
19564 ms
lc.jpg
19565 ms
fc.png
19564 ms
by.jpg
19564 ms
1459144110.jpg.339x226.jpg
14782 ms
stat.htm
167 ms
core.php
909 ms
9.gif
857 ms
shell_v2.js
718 ms
ping_hotclick_min.js
1097 ms
analytics.js
13 ms
collect
23 ms
1458867463.jpg.339x226.jpg
17001 ms
logger.js
355 ms
bds_s_v2.js
1100 ms
1458867342.jpg.339x226.jpg
12118 ms
app.gif
1783 ms
1458785237.jpg.339x226.jpg
9608 ms
bdsstyle.css
358 ms
1458785085.jpg.339x226.jpg
15414 ms
1458715573.jpg.339x226.jpg
20059 ms
14422821306737.jpg
6338 ms
14419732349066.jpg
7410 ms
14416185462747.jpg
7327 ms
14419734679022.jpg
7650 ms
14419737608387.jpg
10813 ms
1441973861287.jpg
8291 ms
14419739769821.jpg
9731 ms
14428059776343.jpg
19995 ms
14428056139872.jpg
10620 ms
14564567687897.jpg
19995 ms
14250083377126.jpg
12577 ms
14467842786626.jpg
12529 ms
14268210652774.jpg
13239 ms
14237991214563.jpg
16295 ms
1456108999534.jpg
15452 ms
14358260479858.jpg
19993 ms
14581273732454.jpg
19993 ms
1460076855.jpg
19993 ms
1460016578.jpg
19994 ms
1460015656.jpg
19994 ms
1456716951.jpg
19994 ms
1456716878.jpg
19994 ms
1453693257.jpg
19994 ms
1453693203.jpg
19993 ms
14339168326543.jpg
19994 ms
14237545465706.jpg
19994 ms
1421139468.jpg
19993 ms
1421139280.jpg
19993 ms
14211989526185.jpg
19993 ms
14212064285246.jpg
19993 ms
1421139677.jpg
16199 ms
14212076118947.jpg
16220 ms
14212080543610.jpg
15350 ms
1455591472695.jpg
19533 ms
14211433591489.jpg
19672 ms
14340762532408.jpg
19590 ms
14212084496472.jpg
20347 ms
1421140952.jpg
14871 ms
14340762532185.jpg
19419 ms
14273347152130.jpg
14883 ms
14273347159277.jpg
16054 ms
14273347157821.jpg
17560 ms
14273347159435.jpg
16379 ms
1441512190974.jpg
20463 ms
14575929843301.jpg
20416 ms
14575935032991.jpg
19213 ms
1457593667785.jpg
19539 ms
1457593146600.jpg
16677 ms
14454118419148.png
12292 ms
1457593788289.jpg
19054 ms
14503255984904.jpg
17466 ms
14497269222043.jpg
19997 ms
14503257269270.jpg
16932 ms
145933094073487.jpg
19996 ms
145307852967312.jpg
19996 ms
143920317870185.jpg
18748 ms
145368446014035.jpg
19286 ms
fblife.com SEO score
N/A
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fblife.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 Fblife.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.
fblife.com
Open Graph description is not detected on the main page of Fblife. 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: