3.7 sec in total
893 ms
2.6 sec
212 ms
Visit faceville.net now to see the best up-to-date Faceville content and also check out these interesting facts you probably never knew about faceville.net
【信誉至上,等您来战
Visit faceville.netWe analyzed Faceville.net page load time and found that the first response time was 893 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
faceville.net performance score
893 ms
176 ms
261 ms
189 ms
190 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 31% of them (46 requests) were addressed to the original Faceville.net, 8% (12 requests) were made to Static.xx.fbcdn.net and 7% (11 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Faceville.net.
Page size can be reduced by 226.0 kB (33%)
677.5 kB
451.5 kB
In fact, the total size of Faceville.net main page is 677.5 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. 65% of websites need less resources to load. Images take 490.9 kB 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. 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 46.2 kB or 80% of the original size.
Potential reduce by 111.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. Obviously, Faceville needs image optimization as it can save up to 111.7 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 46.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 46.9 kB or 46% of the original size.
Potential reduce by 21.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. Faceville.net needs all CSS files to be minified and compressed as it can save up to 21.3 kB or 76% of the original size.
Number of requests can be reduced by 71 (57%)
125
54
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faceville. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
faceville.net
893 ms
reset.css
176 ms
style.css
261 ms
buton.css
189 ms
wp-recentcomments.css
190 ms
wpcf.css
199 ms
jquery.min.js
54 ms
sharebar.js
263 ms
wp-page-numbers.css
305 ms
cufon-yui.js
375 ms
anarschi.js
305 ms
aller.js
393 ms
wp-recentcomments.js
258 ms
css
23 ms
linkexe.png
677 ms
ap.png
148 ms
ustarka.png
236 ms
logo.png
278 ms
anasayfa.png
148 ms
exc.png
148 ms
fans.png
131 ms
about.png
207 ms
archive.png
251 ms
contact.png
269 ms
arka.png
249 ms
ust.png
672 ms
fb.png
339 ms
twit.png
342 ms
google.png
341 ms
Parrot-Tree-150x150.png
475 ms
kategori.png
444 ms
okunma.png
452 ms
yorumicon.png
451 ms
devaminioku.png
449 ms
cizgi.png
449 ms
kisisel.png
670 ms
internet.png
668 ms
guncel.png
667 ms
solenalt.png
565 ms
facebook.png
645 ms
twitter.png
669 ms
rss.png
692 ms
linkedin.png
747 ms
futiricon.png
750 ms
addme.png
733 ms
widgets.js
8 ms
l2632NY.png
114 ms
sosyalarka.png
712 ms
sagbaslikarka.png
793 ms
arrow.png
719 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
90 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
109 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
124 ms
plusone.js
166 ms
like.php
203 ms
futir.png
710 ms
classic.js
158 ms
ga.js
84 ms
faceville.net
1061 ms
likebox.php
115 ms
__utm.gif
30 ms
cb=gapi.loaded_0
68 ms
cb=gapi.loaded_1
95 ms
badge
216 ms
32 ms
hDvwL1_H7g-.css
97 ms
udqjbTyb5Ue.css
104 ms
FAHeNGXgPup.js
120 ms
FJmpeSpHpjS.js
118 ms
0wM5s1Khldu.js
110 ms
1bNoFZUdlYZ.js
113 ms
fy8tT2klpgR.js
184 ms
LVx-xkvaJ0b.png
96 ms
dpx.js
79 ms
postmessageRelay
149 ms
tpid=1EE70445FFA6E9562903883602400BCC
110 ms
p
97 ms
406384_392319560839673_22972813_n.jpg
79 ms
12033042_943519069053050_7782281914309375275_n.png
45 ms
11222947_133786643636859_7333076837951050861_n.jpg
63 ms
10273778_10201715963052922_5066843235946855811_n.jpg
100 ms
12688304_1104666396231645_8288138265911989288_n.jpg
63 ms
12072585_1139253049437986_4045728107856542720_n.jpg
61 ms
12301688_10208542009571718_6404550370962881718_n.jpg
62 ms
12088587_698562413578300_6452962796266239824_n.jpg
61 ms
wL6VQj7Ab77.png
19 ms
s7jcwEQH7Sx.png
19 ms
rs=AGLTcCOkK5aHiEAS5uN3kt57ijjQh5lvTQ
19 ms
rs=AGLTcCNgATaxVKcwjgmvzuf1yNIlELvHSg
57 ms
rs=AGLTcCMFKCZgdpFtQEwkPZPCbXNirfyl6A
124 ms
dpx
8 ms
photo.jpg
178 ms
aol
7 ms
3193398744-postmessagerelay.js
172 ms
rpc:shindig_random.js
77 ms
I6-MnjEovm5.js
106 ms
pQrUxxo5oQp.js
106 ms
mapuser
101 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
159 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
200 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
237 ms
125 ms
rs=AGLTcCMFKCZgdpFtQEwkPZPCbXNirfyl6A
34 ms
cb=gapi.loaded_0
32 ms
rs=AGLTcCMFKCZgdpFtQEwkPZPCbXNirfyl6A
27 ms
tc.js
13 ms
y_match
40 ms
p
60 ms
match_redirect
7 ms
29931
55 ms
v2
44 ms
match_redirect
4 ms
tpid=DA29559EFFA6E956AF48030402629A06
6 ms
lr
4 ms
dpx
4 ms
27519
54 ms
xrefid.xgi
14 ms
pixel
41 ms
generic
12 ms
i.match
156 ms
1407
234 ms
generic
6 ms
2964
30 ms
5386
142 ms
2831
179 ms
lr.gif
8 ms
4470
29 ms
pixel
36 ms
match_redirect
4 ms
sync
89 ms
3085
51 ms
52154.gif
7 ms
2981
52 ms
4448
235 ms
match_redirect
4 ms
DA29559EFFA6E956AF48030402629A06
32 ms
i.match
81 ms
match_redirect
4 ms
ProfilesEngineServlet
5 ms
ProfilesEngineServlet
16 ms
tap.php
11 ms
event
4 ms
4229
30 ms
exelate
3 ms
match_redirect
4 ms
ad516503a11cd5ca435acc9bb6523536
56 ms
engine
95 ms
35 ms
31 ms
18 ms
faceville.net SEO score
![]()
ZH
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faceville.net can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Faceville.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
faceville.net
Open Graph description is not detected on the main page of Faceville. 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: