3.6 sec in total
426 ms
2.5 sec
698 ms
Click here to check amazing Fantasyard content for United States. Otherwise, check out these important facts you probably never knew about fantasyard.com
Austrian rhinestone pin brooch, cufflinks, butterfly, flower, octopus, insect, animal, peacock, crown, spider, bug, frog, cross, free shipping
Visit fantasyard.comWe analyzed Fantasyard.com page load time and found that the first response time was 426 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
fantasyard.com performance score
name
value
score
weighting
Value1.9 s
88/100
10%
Value8.5 s
2/100
25%
Value4.0 s
81/100
10%
Value550 ms
54/100
30%
Value0.1
89/100
15%
Value6.7 s
56/100
10%
426 ms
39 ms
38 ms
32 ms
43 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that all of those requests were addressed to Fantasyard.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fantasyard.com.
Page size can be reduced by 166.6 kB (6%)
2.8 MB
2.6 MB
In fact, the total size of Fantasyard.com main page is 2.8 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. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 162.9 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 21.5 kB, which is 11% 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 162.9 kB or 84% of the original size.
Potential reduce by 1.1 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. Fantasyard images are well optimized though.
Potential reduce by 219 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 2.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. Fantasyard.com has all CSS files already compressed.
Number of requests can be reduced by 38 (53%)
72
34
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fantasyard. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
www.fantasyard.com
426 ms
constants.js
39 ms
pubsub.js
38 ms
global.js
32 ms
preloads.js
43 ms
load_feature-9f951eb7d8d53973c719de211f807d63af81c644e5b9a6ae72661ac408d472f6.js
39 ms
storefront-80e528be853eac23af2454534897ca9536b1d3d04aa043b042f34879a3c111c8.js
43 ms
features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js
49 ms
scripts.js
94 ms
base.css
65 ms
details-disclosure.js
61 ms
details-modal.js
87 ms
cart-notification.js
109 ms
search-form.js
87 ms
section-image-banner.css
86 ms
component-card.css
90 ms
component-price.css
84 ms
component-rte.css
93 ms
component-rating.css
122 ms
collage.css
118 ms
component-modal-video.css
107 ms
section-multicolumn.css
138 ms
section-footer.css
133 ms
predictive-search.js
119 ms
trekkie.storefront.99bdfbca815ea24ab1705979a783df6e7810b51d.min.js
122 ms
shop_events_listener-61fa9e0a912c675e178777d2b27f6cbd482f8912a6b0aa31fa3515985a8cd626.js
122 ms
shopify-boomerang-1.0.0.min.js
121 ms
fantasyard_pink_logo.png
117 ms
wallpaper_pink_acabd662-848a-414e-89ba-2660553b651c.jpg
141 ms
1005331-3.jpg
410 ms
1005331-6.jpg
111 ms
101092310001.jpg
123 ms
1010923-2.jpg
368 ms
1013372-04.jpg
192 ms
1013372-03.jpg
193 ms
101337110001.jpg
193 ms
101337110003.jpg
200 ms
101265210001.jpg
252 ms
101265210002.jpg
237 ms
1012501-1.jpg
454 ms
1012501-4.jpg
263 ms
101188410001.jpg
305 ms
101-188D-1000C.jpg
316 ms
101110210001.jpg
327 ms
1011102-2.jpg
640 ms
1010841-2.jpg
629 ms
1010841-1.jpg
651 ms
1010331-1.jpg
650 ms
1010331-4.jpg
758 ms
101009110001.jpg
540 ms
101-009A-1000A.jpg
617 ms
1004714-3.jpg
902 ms
1004714-1.jpg
898 ms
1013372-04.jpg
678 ms
1000012-3_91d9173b-cc43-478b-a968-1b236c7aee17.jpg
704 ms
1005331-3.jpg
669 ms
100230110001_1.jpg
949 ms
100109110001_1.jpg
1097 ms
1002091-1_1.jpg
748 ms
component-predictive-search.css
32 ms
component-list-menu.css
22 ms
component-search.css
71 ms
component-menu-drawer.css
26 ms
component-cart-notification.css
28 ms
component-cart-items.css
26 ms
component-loading-overlay.css
23 ms
component-slider.css
24 ms
template-collection.css
32 ms
component-deferred-media.css
55 ms
component-newsletter.css
28 ms
component-list-payment.css
32 ms
component-list-social.css
25 ms
disclosure.css
65 ms
fantasyard.com 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.
fantasyard.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
fantasyard.com SEO score
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fantasyard.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Fantasyard.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.
fantasyard.com
Open Graph data is detected on the main page of Fantasyard. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: