2.5 sec in total
13 ms
1.8 sec
673 ms
Click here to check amazing Thingd content. Otherwise, check out these important facts you probably never knew about thingd.com
Join me on Fancy! Discover amazing stuff, collect the things you love, buy it all in one place.
Visit thingd.comWe analyzed Thingd.com page load time and found that the first response time was 13 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
thingd.com performance score
13 ms
56 ms
303 ms
229 ms
248 ms
Our browser made a total of 137 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Thingd.com, 7% (9 requests) were made to Static-ec1.thefancy.com and 5% (7 requests) were made to Static-ec4.thefancy.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Thingd-media-ec4.thefancy.com.
Page size can be reduced by 1.1 MB (27%)
4.1 MB
3.0 MB
In fact, the total size of Thingd.com main page is 4.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. 65% of websites need less resources to load. Images take 2.7 MB which makes up the majority of the site volume.
Potential reduce by 106.5 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 106.5 kB or 81% of the original size.
Potential reduce by 22.3 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. Thingd images are well optimized though.
Potential reduce by 460.2 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 460.2 kB or 68% of the original size.
Potential reduce by 519.4 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. Thingd.com needs all CSS files to be minified and compressed as it can save up to 519.4 kB or 84% of the original size.
Number of requests can be reduced by 79 (61%)
129
50
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Thingd. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.thefancy.com
13 ms
fancy.com
56 ms
layout.v2.eb3c5e434fe8.css
303 ms
sign.v4.cbbde855fa36.css
229 ms
timeline.v2.76df00c440ec.css
248 ms
timeline_slideshow.9c5f419e7e37.css
222 ms
js
28 ms
namespace.min.fca096b206ae.js
227 ms
en.0eb2a47f4be1.js
244 ms
desktop.min.43148e95093d.js
288 ms
require-login.4de070dd246a.js
221 ms
main.min.v3.152bccf23db7.js
257 ms
nav_header.f84085b768c2.js
253 ms
nav_header_cart.90551882285b.js
255 ms
nav_header_search.43a8d14d0545.js
255 ms
user_card.4059da87230a.js
253 ms
google_connect.8cf8072796b6.js
225 ms
social_connect.c526e2c8b5f3.js
253 ms
password_strength.62d95c2d8402.js
256 ms
signup.3c917ef22e4f.js
255 ms
twitter_connect.b6d117305def.js
256 ms
facebook_connect.2730e492b7f1.js
235 ms
alertify.min.e3eb4cd0e37a.js
236 ms
spin.min.2ad3480baedc.js
253 ms
timeline_slideshow.new.9a036b29c8a5.js
250 ms
sale_page_helper.01a6acb2d1de.js
254 ms
comments.12bb45df6d9f.js
253 ms
home.featured.479867e6578f.js
249 ms
more-share.css
9 ms
more-share.js
13 ms
more-share.lagacy.js
12 ms
mixpanel-2-latest.min.js
138 ms
fbds.js
536 ms
blank.gif
26 ms
1108474634048638913_83ffcc3bc459.gif
1247 ms
1086339833716022577_e50732160c02.jpg
435 ms
1109367763287149047_e7313845a83a.jpg
433 ms
1106411775366011029_6d1dbc04a45a.jpg
435 ms
564748693568226645_ceb4dc3564cb.gif
1156 ms
blank.325472601571.gif
136 ms
386813495070429535_82d46aacbca5.jpg
425 ms
1067668548144340381_81e6d36b48d6.jpg
554 ms
1058618523368038330_dc298b901cc1.jpg
580 ms
934575176773802536_67f091cf5431.jpg
424 ms
1083914502979721257_99ca1b5952d7.jpg
532 ms
gtm.js
376 ms
analytics.js
342 ms
MasterTMS.min.js
353 ms
header_new.df841d28fb45.png
131 ms
1068779797716407579_a2a2cbd9385b.jpg
574 ms
navi.2b9a8d8a799a.png
114 ms
1089531631045188207_1c5baec432cd.jpg
562 ms
103332407721072789_2510b508788f.jpg
808 ms
1056576189872739184_5e12504ab07a.jpg
520 ms
1108474634048638913_83ffcc3bc459.gif
882 ms
1108474634048638913_83ffcc3bc459.gif
573 ms
1109367763287149047_e7313845a83a.jpg
619 ms
1109367763287149047_e7313845a83a.jpg
519 ms
1106411775366011029_6d1dbc04a45a.jpg
658 ms
1106411775366011029_6d1dbc04a45a.jpg
513 ms
1086339833716022577_e50732160c02.jpg
502 ms
1067668548144340381_81e6d36b48d6.jpg
709 ms
934575176773802536_67f091cf5431.jpg
501 ms
1083914502979721257_99ca1b5952d7.jpg
501 ms
1058618523368038330_dc298b901cc1.jpg
707 ms
564748693568226645_ceb4dc3564cb.gif
550 ms
386813495070429535_82d46aacbca5.jpg
501 ms
shop_buttons.ae44e16223ce.png
262 ms
1086339833716022577_e50732160c02.jpg
644 ms
1067668548144340381_81e6d36b48d6.jpg
500 ms
934575176773802536_67f091cf5431.jpg
574 ms
1083914502979721257_99ca1b5952d7.jpg
757 ms
1058618523368038330_dc298b901cc1.jpg
498 ms
386813495070429535_82d46aacbca5.jpg
559 ms
564748693568226645_ceb4dc3564cb.gif
923 ms
fancy-us
497 ms
client:plusone.js
394 ms
in.php
578 ms
271 ms
_featured_feed
226 ms
c.aspx
200 ms
collect
68 ms
tags
158 ms
conversion_async.js
149 ms
fbevents.js
188 ms
activityi;src=5110733;type=count0;cat=fancy0;ord=7290146228136;~oref=https%3A%2F%2Ffancy.com%2F
231 ms
t
477 ms
82 ms
sdk.js
289 ms
ld.js
152 ms
cb=gapi.loaded_0
60 ms
183 ms
106 ms
view
59 ms
198 ms
postmessageRelay
126 ms
cb=gapi.loaded_1
41 ms
194 ms
rum
374 ms
serve
291 ms
pixel
206 ms
75 ms
usersync
202 ms
Pug
200 ms
263 ms
Pug
204 ms
pixel
202 ms
u.php
184 ms
event
221 ms
140 ms
3193398744-postmessagerelay.js
135 ms
rpc:shindig_random.js
263 ms
42 ms
65 ms
xd_arbiter.php
251 ms
sd
7 ms
match
33 ms
match
61 ms
mapuser
8 ms
match
57 ms
match
67 ms
match
45 ms
tap.php
14 ms
match
22 ms
match
29 ms
match
21 ms
cm.gif
3 ms
cb=gapi.loaded_0
12 ms
rum
109 ms
auth
45 ms
match
29 ms
2637085964-postmessage.js
10 ms
beacon.riskified.com
34 ms
dis.aspx
64 ms
22 ms
image-l.gif
67 ms
xd_arbiter.php
76 ms
thingd.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Thingd.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Thingd.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.
thingd.com
Open Graph data is detected on the main page of Thingd. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: