46.5 sec in total
1.4 sec
44.7 sec
429 ms
Click here to check amazing Fzlaa content. Otherwise, check out these important facts you probably never knew about fzlaa.com
qq个性头像大全-09-22年记录-历史百度权重3
Visit fzlaa.comWe analyzed Fzlaa.com page load time and found that the first response time was 1.4 sec and then it took 45.1 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 4 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
fzlaa.com performance score
name
value
score
weighting
Value1.5 s
96/100
10%
Value1.5 s
100/100
25%
Value5.6 s
53/100
10%
Value1,050 ms
25/100
30%
Value0.038
100/100
15%
Value9.3 s
31/100
10%
1421 ms
4505 ms
4495 ms
8862 ms
10083 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 69% of them (78 requests) were addressed to the original Fzlaa.com, 5% (6 requests) were made to Bdimg.share.baidu.com and 4% (5 requests) were made to Cpro.baidustatic.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source T11.baidu.com.
Page size can be reduced by 284.4 kB (31%)
904.2 kB
619.9 kB
In fact, the total size of Fzlaa.com main page is 904.2 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. 35% of websites need less resources to load. Images take 502.4 kB which makes up the majority of the site volume.
Potential reduce by 55.8 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 55.8 kB or 82% of the original size.
Potential reduce by 19.7 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. Fzlaa images are well optimized though.
Potential reduce by 194.7 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 194.7 kB or 62% of the original size.
Potential reduce by 14.1 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. Fzlaa.com needs all CSS files to be minified and compressed as it can save up to 14.1 kB or 72% of the original size.
Number of requests can be reduced by 22 (22%)
101
79
The browser has sent 101 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fzlaa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
fzlaa.com
1421 ms
www.fzlaa.com
4505 ms
index.css
4495 ms
jquery.min.js
8862 ms
jquery.js
10083 ms
jquery.lazyload.js
882 ms
o.js
721 ms
stat.php
1259 ms
head-bg.gif
384 ms
topbj.gif
3005 ms
logo.gif
1169 ms
sotu.gif
396 ms
dhbj.gif
397 ms
dhli.gif
719 ms
daizi.jpg
1079 ms
xinggan.jpg
1159 ms
heibai.jpg
743 ms
jingtai.jpg
1077 ms
keai.jpg
1158 ms
qinglvyidui.jpg
1415 ms
tuifei.jpg
1803 ms
oumei.jpg
1832 ms
lomo.jpg
1491 ms
gaoqing.jpg
1957 ms
jingdian.jpg
1777 ms
qqqun.jpg
1854 ms
weimei.jpg
2133 ms
shishang.jpg
3234 ms
huiyuan.jpg
3280 ms
abaose.jpg
2229 ms
qq2012.jpg
7139 ms
shuaige.jpg
2612 ms
1_1012015TQ623.jpg
6701 ms
1_1012015J54B0.jpg
5493 ms
1_10120153414062.png
17939 ms
1_10120152125341.png
15271 ms
1_10110119122021.jpg
4897 ms
1_10110114445433.jpg
11002 ms
1_101101064H4b.jpg
13313 ms
1_101101044Y912.jpg
10299 ms
1_1010005I152Q.png
15694 ms
1_10100055316129.jpg
11676 ms
1_101000502R344.jpg
15275 ms
kctm
976 ms
1_100Z20S643H.jpg
13802 ms
1_100Z20634G03.jpg
14129 ms
1_100Z20144LO.jpg
14751 ms
1_100Z200354T9.jpg
15308 ms
1_1012014Z3J09.jpg
15337 ms
1_1011011124Q14.jpg
15361 ms
kctm
1587 ms
shell_v2.js
495 ms
1_1011005FY194.jpg
17592 ms
1_10100049301M8.jpg
17498 ms
1_100422424bF0.jpg
16833 ms
stat.htm
263 ms
core.php
582 ms
1_1001214U1O38.jpg
16880 ms
1_10012155441359.jpg
16150 ms
1_09302004505Z1.jpg
16327 ms
1_092923115UX7.jpg
16658 ms
bds_s_v2.js
497 ms
pixel
21 ms
pixel
14 ms
gpixel
1559 ms
9.gif
895 ms
logger.js
498 ms
ad1.jpg
20305 ms
1_1011010030XR.jpg
17641 ms
1_100H15RD155.jpg
18463 ms
1_10062354122536.png
20229 ms
1_10052014553N2.jpg
17455 ms
adx.php
4399 ms
reduce_bd-logo1_oper.png
2525 ms
bdsstyle.css
258 ms
getnum
4017 ms
1_1004224523V26.jpg
17246 ms
1_1001215324c94.jpg
17521 ms
is.png
1722 ms
sc.png
1001 ms
u=631498227,3659795602&fm=76
5843 ms
u=1899850336,2704231226&fm=76
6469 ms
u=3310635140,934362708&fm=76
1539 ms
u=906352015,1016723364&fm=76
20471 ms
u=1265655567,1529096812&fm=76
4598 ms
u=295542087,2304134935&fm=76
1690 ms
u=676700972,4074251951&fm=76
9010 ms
1_0930200F4G34.jpg
18710 ms
app.gif
980 ms
1_092923121014Z.jpg
16804 ms
1_100F004201C8.jpg
17256 ms
1_10042240354260.jpg
17220 ms
1_100323333562T.jpg
16090 ms
1_100221061E226.jpg
16889 ms
1_093020151V3J.png
20379 ms
1_092H224213309.jpg
16247 ms
1_140926201825_1-lp.jpg
13564 ms
index-l1bj.gif
11725 ms
shouye.gif
11105 ms
newstt.gif
9471 ms
nestttt.gif
9233 ms
tjbj.gif
8608 ms
l2t.gif
7985 ms
bqt2.gif
8149 ms
txtxt.gif
8195 ms
closefeedback.min.js
494 ms
snippetcacher.php
1008 ms
reduce_promotion_oper.png
479 ms
bd_logo.png
491 ms
bg_rb.png
514 ms
o.htm
2876 ms
ac.js
474 ms
wh.js
722 ms
fzlaa.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
<frame> or <iframe> elements do not have a title
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
fzlaa.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fzlaa.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
ZH
N/A
GB2312
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fzlaa.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 Fzlaa.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.
fzlaa.com
Open Graph description is not detected on the main page of Fzlaa. 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: