5.3 sec in total
743 ms
4.1 sec
429 ms
Welcome to fancythings.nl homepage info - get ready to check Fancythings best content right away, or after learning these important things about fancythings.nl
Zoekt u mooie sieraden voor uzelf? Of misschien sieraden voor een ander? Neem dan een kijkje in onze webwinkel. Hier vind je de leukste sieraden, accessoires, kinderkleding en nog veel meer!
Visit fancythings.nlWe analyzed Fancythings.nl page load time and found that the first response time was 743 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fancythings.nl performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value3.9 s
52/100
25%
Value3.6 s
87/100
10%
Value180 ms
91/100
30%
Value0
100/100
15%
Value4.0 s
88/100
10%
743 ms
274 ms
549 ms
194 ms
196 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 43% of them (30 requests) were addressed to the original Fancythings.nl, 14% (10 requests) were made to Static.xx.fbcdn.net and 13% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (980 ms) belongs to the original domain Fancythings.nl.
Page size can be reduced by 545.1 kB (24%)
2.3 MB
1.7 MB
In fact, the total size of Fancythings.nl main page is 2.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. 60% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 85.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. This page needs HTML code to be minified as it can gain 12.8 kB, which is 13% 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 85.0 kB or 85% of the original size.
Potential reduce by 9.2 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. Fancythings images are well optimized though.
Potential reduce by 235.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 235.9 kB or 68% of the original size.
Potential reduce by 215.0 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. Fancythings.nl needs all CSS files to be minified and compressed as it can save up to 215.0 kB or 83% of the original size.
Number of requests can be reduced by 19 (31%)
62
43
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fancythings. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
index.php
743 ms
v_60_ef7eb37f941d9fa2fe981b0504815f21_all.css
274 ms
v_34_f1fa4dff3f9debac14bb11cd3516e39b.js
549 ms
ptmfix.css
194 ms
custommaker.css
196 ms
customuser.css
194 ms
css
23 ms
css
34 ms
staticw2.yotpo.com
35 ms
analytics.js
29 ms
background.jpg
341 ms
32a946b07c08507d6021e426e14147ea.jpg
189 ms
my-shop-logo-1435074330.jpg
697 ms
98267bb7016cc6332ce013a3b943b96cdd901ea0_slidshow1.jpg
569 ms
df2b02e3b13afea31830414093ae8cc1ffb20529_slidshow2.jpg
536 ms
c7e0fe5c8a18aeae3462cc25d263e271fa850e2f_slidshow3.jpg
663 ms
5407e3467827f1193d2b4ee509bf87c8976b3a85_fotor01008143344.jpg
279 ms
ed5d053a604ef5bf5d2a2898efee0ad45b630665_banner-img11.jpg
366 ms
254-home_default.jpg
426 ms
939-home_default.jpg
453 ms
974-home_default.jpg
516 ms
497-home_default.jpg
544 ms
804-home_default.jpg
610 ms
969-home_default.jpg
635 ms
535-home_default.jpg
656 ms
848-home_default.jpg
653 ms
42bf1501523f66757df3394dc6c887f6efe44b7b_banner-img1.jpg
866 ms
23da8bc44777a91d442650ee0071159603e92fc6_banner-img3.jpg
807 ms
cc376be57822248f6d2acfde554ae271defdff4f_banner-img4.jpg
818 ms
6566f7afb53fdf74c20a2b5bc6075fcb6487009c_banner-img8.jpg
820 ms
51110b9598277f1938d6c800d86380386e64275a_banner-img7.jpg
842 ms
Logos.png
798 ms
55gTuvBwF0Wg7V2dgeeA_w.ttf
24 ms
fontawesome-webfont.woff
980 ms
ec.js
13 ms
all.js
157 ms
widget.js
41 ms
collect
11 ms
bx_loader.gif
792 ms
widget.css
98 ms
i
9 ms
batch
29 ms
144 ms
xd_arbiter.php
139 ms
xd_arbiter.php
248 ms
css
13 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
2 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
8 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
9 ms
ping
56 ms
like_box.php
150 ms
kyEKgjk51ZE.css
178 ms
xgj7bXhJNEH.css
220 ms
q68gy-v_YMF.js
302 ms
FJmpeSpHpjS.js
374 ms
0wM5s1Khldu.js
299 ms
1bNoFZUdlYZ.js
298 ms
1977103_600650320017642_1376067462_n.jpg
310 ms
11836930_855646767851328_3525471582851019166_n.jpg
521 ms
11207293_1636633023244574_1541848390885943737_n.jpg
477 ms
11037712_408819259299529_1257294509353528514_n.jpg
463 ms
10731168_10203119677413733_6577283571340631377_n.jpg
498 ms
1914554_10207651839445484_8875233307200551298_n.jpg
493 ms
12814254_239224473085977_3816602023381307807_n.jpg
466 ms
12088329_1613633382234127_1413856323188147583_n.jpg
549 ms
12524268_1564379797221530_2630430022406402864_n.jpg
507 ms
wL6VQj7Ab77.png
49 ms
s7jcwEQH7Sx.png
49 ms
I6-MnjEovm5.js
42 ms
pQrUxxo5oQp.js
83 ms
fancythings.nl accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Document doesn't have a <title> element
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
fancythings.nl 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
fancythings.nl SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
N/A
NL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fancythings.nl 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), while the claimed language is Dutch. Our system also found out that Fancythings.nl 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.
fancythings.nl
Open Graph description is not detected on the main page of Fancythings. 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: