5.1 sec in total
442 ms
4.3 sec
351 ms
Click here to check amazing FOOLPIN content for Taiwan. Otherwise, check out these important facts you probably never knew about foolpin.com
人生苦短,不值得浪費在不適合的商品。商業置入讓網路口碑變得不可信,負評網將透過社群的智慧,拼湊完全不同的觀點
Visit foolpin.comWe analyzed Foolpin.com page load time and found that the first response time was 442 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
foolpin.com performance score
442 ms
1700 ms
323 ms
536 ms
370 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 49% of them (39 requests) were addressed to the original Foolpin.com, 21% (17 requests) were made to Scontent.xx.fbcdn.net and 5% (4 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Foolpin.com.
Page size can be reduced by 853.2 kB (67%)
1.3 MB
424.0 kB
In fact, the total size of Foolpin.com main page is 1.3 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. HTML takes 578.7 kB which makes up the majority of the site volume.
Potential reduce by 524.0 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 524.0 kB or 91% of the original size.
Potential reduce by 7.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. FOOLPIN images are well optimized though.
Potential reduce by 189.8 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 189.8 kB or 64% of the original size.
Potential reduce by 131.8 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. Foolpin.com needs all CSS files to be minified and compressed as it can save up to 131.8 kB or 81% of the original size.
Number of requests can be reduced by 27 (37%)
73
46
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FOOLPIN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
foolpin.com
442 ms
www.foolpin.com
1700 ms
simplegrid.css
323 ms
bootstrap.min.css
536 ms
style.css
370 ms
fix.css
376 ms
jquery.min.js
31 ms
introDialog.js
473 ms
jquery-ui.js
9 ms
common.min.js
802 ms
function.js
580 ms
defaultApp.js
580 ms
chart.min.js
580 ms
main.min.js
649 ms
analytics.js
28 ms
FOOLPIN_LOGO.png
186 ms
indicator.gif
185 ms
986.jpg
178 ms
940.jpg
187 ms
1004.jpg
230 ms
234.jpg
462 ms
532.jpg
469 ms
582.jpg
470 ms
904.jpg
470 ms
1254.jpg
469 ms
1448.jpg
470 ms
1447.jpg
561 ms
1446.jpg
626 ms
1445.jpg
625 ms
%7B%7Bproduct.cover_path%7D%7D
711 ms
introDialog
704 ms
collect
25 ms
collect
64 ms
webfont.js
159 ms
counter.js
11 ms
fbds.js
196 ms
sdk.js
249 ms
atrk.js
136 ms
likerList.html
245 ms
1312.jpg
310 ms
1313.jpg
364 ms
css
48 ms
font-awesome.min.css
330 ms
product_default.jpg
407 ms
1441.jpg
417 ms
unknown.jpg
416 ms
1437.jpg
553 ms
1415.jpg
549 ms
1405.jpg
552 ms
29 ms
atrk.gif
72 ms
test.png
59 ms
33 ms
xd_arbiter.php
161 ms
xd_arbiter.php
298 ms
36ad37d47fb6e5ce8924c1b9ef64f372
78 ms
1472785_10200856760693864_794234773_n.jpg
304 ms
12734055_10204654626079760_3764734083082151944_n.jpg
263 ms
1460196_10200186252417948_6097073_n.jpg
214 ms
12507511_1228551470493521_5563445742623578408_n.jpg
213 ms
12897_550456614981136_417476978_n.jpg
273 ms
310268_102539586521249_782929018_n.jpg
291 ms
12745756_1114063555280567_3322811955345570192_n.jpg
238 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
24 ms
fontawesome-webfont.woff
556 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
38 ms
12512617_10153911659667028_3687311129643666733_n.jpg
393 ms
12688033_1051983671490924_4704057616418793151_n.jpg
241 ms
12743609_10206806643218039_8488130879747836496_n.jpg
244 ms
398156_2755195455985_698590223_n.jpg
295 ms
10522749_1212640075416217_8431675874924043004_n.jpg
421 ms
10252043_10203934557824861_3616498339570365658_n.jpg
277 ms
10250321_1050687734946619_6788537002842359374_n.jpg
199 ms
10403296_10152742131511444_4947755075311419547_n.jpg
193 ms
12644882_434781236720160_1087225972549839983_n.jpg
227 ms
11891257_1083164761695606_1469976718025173450_n.jpg
228 ms
3 ms
like.php
69 ms
rU2ubZ6l1Q5.js
296 ms
LVx-xkvaJ0b.png
327 ms
foolpin.com SEO score
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foolpin.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 Foolpin.com 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.
foolpin.com
Open Graph data is detected on the main page of FOOLPIN. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: