1.2 sec in total
100 ms
986 ms
70 ms
Click here to check amazing Flossyco content. Otherwise, check out these important facts you probably never knew about flossyco.com
Los Agneles based sincerely-selected contemporary concept store. Check our refined womenswear, shoes, bags, and acc at FLOSSY CO.
Visit flossyco.comWe analyzed Flossyco.com page load time and found that the first response time was 100 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
flossyco.com performance score
100 ms
75 ms
24 ms
27 ms
68 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Flossyco.com, 93% (150 requests) were made to Static.parastorage.com and 4% (6 requests) were made to Frog.wix.com. The less responsive or slowest element that took the longest time to load (314 ms) relates to the external source Static.wixstatic.com.
Page size can be reduced by 685.6 kB (62%)
1.1 MB
420.3 kB
In fact, the total size of Flossyco.com main page is 1.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 69.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 69.5 kB or 80% of the original size.
Potential reduce by 615.6 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 615.6 kB or 61% of the original size.
Potential reduce by 557 B
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. Flossyco.com has all CSS files already compressed.
Number of requests can be reduced by 153 (96%)
159
6
The browser has sent 159 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flossyco. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 149 to 1 for JavaScripts and as a result speed up the page load time.
flossyco.com
100 ms
www.flossyco.com
75 ms
require.min.js
24 ms
main-r.min.js
27 ms
bt
68 ms
21d6b0_043bd426ee744a6f35515f441f9af467_656.json.z
314 ms
21d6b0_814b232c3fa2c989db24ad44d231aafa_656.json.z
312 ms
ugc-viewer
50 ms
bt
49 ms
react-with-addons.min.js
23 ms
lodash.min.js
22 ms
wixCodeInit.min.js
22 ms
coreUtils.js
51 ms
coreUtils.min.js
49 ms
skins.min.js
74 ms
components.min.js
71 ms
core.min.js
72 ms
mobx.umd.min.js
48 ms
mobx-react.min.js
73 ms
TweenMax.min.js
73 ms
animations.min.js
72 ms
react-with-addons.min.js
74 ms
layout.min.js
76 ms
wixappsCore.min.js
74 ms
wixappsClassics.min.js
75 ms
container.min.js
75 ms
imageZoom.min.js
76 ms
mediaZoom.min.js
76 ms
imageZoomDisplayer.min.js
78 ms
matrixGallery.min.js
76 ms
slideShowGallery.min.js
78 ms
comboBoxInput.min.js
77 ms
dialogs.min.js
76 ms
table.min.js
78 ms
wixappsBuilder.min.js
79 ms
tpa.min.js
80 ms
dataFixer.min.js
78 ms
siteUtils.min.js
80 ms
image.min.js
78 ms
balata.min.js
79 ms
translationsUtils.min.js
81 ms
hammer.min.js
79 ms
utils.min.js
265 ms
fonts.min.js
264 ms
platformUtils-bundle.js
263 ms
loggingUtils.min.js
260 ms
imageClientApi.js
260 ms
swfobject.min.js
238 ms
santaProps.min.js
230 ms
displayer.min.js
230 ms
mousetrap.min.js
225 ms
DrawSVGPlugin.min.js
208 ms
react-dom.min.js
208 ms
ScrollToPlugin.min.js
208 ms
widgets.min.js
209 ms
react-dom-server.min.js
208 ms
imageCommon.min.js
207 ms
formCommon.min.js
207 ms
textCommon.min.js
205 ms
containerCommon.min.js
206 ms
socialCommon.min.js
206 ms
galleriesCommon.min.js
206 ms
buttonCommon.min.js
205 ms
compDesignUtils.min.js
204 ms
mediaCommon.min.js
205 ms
audioCommon.min.js
205 ms
skinExports.min.js
205 ms
compUtils.min.js
205 ms
mobileLayoutUtils.js
205 ms
pm-rpc.min.js
203 ms
tweenEngine.min.js
204 ms
multilingual.min.js
204 ms
render.min.js
204 ms
color.min.js
204 ms
zepto.min.js
204 ms
xss.min.js
202 ms
bluebird.min.js
203 ms
imageClientApi.min.js
200 ms
column.min.js
206 ms
siteBackground.min.js
206 ms
hoverBox.min.js
207 ms
mediaContainerFactory.min.js
206 ms
internalMarkings.min.js
205 ms
repeater.min.js
205 ms
zoomedImage.min.js
206 ms
menuButton.min.js
206 ms
messageView.min.js
206 ms
backgroundCommon.min.js
206 ms
bt
88 ms
css
88 ms
TweenMax.min.js
37 ms
svgShape.min.js
35 ms
adminLoginButton.min.js
38 ms
wTwitterFollow.min.js
37 ms
facebookComments.min.js
37 ms
verticalAnchorsMenu.min.js
37 ms
facebookShare.min.js
37 ms
vKShareButton.min.js
44 ms
youTubeSubscribeButton.min.js
46 ms
itunesButton.min.js
43 ms
skypeCallButton.min.js
44 ms
fileUploader.min.js
44 ms
pinItPinWidget.min.js
44 ms
popupCloseTextButton.min.js
45 ms
radioButton.min.js
48 ms
radioGroup.min.js
47 ms
documentMedia.min.js
47 ms
datePicker.min.js
47 ms
contactForm.min.js
45 ms
subscribeForm.min.js
54 ms
textArea.min.js
56 ms
loginSocialBar.min.js
58 ms
googleMap.min.js
56 ms
soundCloudWidget.min.js
55 ms
paypalButton.min.js
55 ms
imageButton.min.js
57 ms
linkBar.min.js
60 ms
spotifyPlayer.min.js
59 ms
spotifyFollow.min.js
57 ms
twitterFeed.min.js
58 ms
backToTopButton.min.js
60 ms
svgCommon.min.js
60 ms
facebookLike.min.js
61 ms
facebookLikeBox.min.js
62 ms
flickrBadgeWidget.min.js
62 ms
rssButton.min.js
62 ms
tinyMenu.min.js
33 ms
groupContainer.min.js
33 ms
wGooglePlusOne.min.js
34 ms
pinterestPinIt.min.js
35 ms
pinterestFollow.min.js
33 ms
wTwitterTweet.min.js
34 ms
audioPlayer.min.js
29 ms
loginButton.min.js
28 ms
htmlComponent.min.js
28 ms
deadComponent.min.js
28 ms
mediaPlayer.min.js
30 ms
mediaControls.min.js
28 ms
singleAudioPlayer.min.js
28 ms
quickActionBar.min.js
26 ms
boxSlideShowSlide.min.js
27 ms
stripSlideShowSlide.min.js
27 ms
page.min.js
28 ms
bgImageStrip.min.js
27 ms
popupContainer.min.js
36 ms
stripContainer.min.js
35 ms
stripColumnsContainer.min.js
35 ms
exitMobileModeButton.min.js
36 ms
tpaGalleries.min.js
35 ms
flashComponent.min.js
35 ms
stripSlideShow.min.js
35 ms
mobileActionsMenu.min.js
35 ms
verticalMenu.min.js
33 ms
disqusComments.min.js
34 ms
checkbox.min.js
33 ms
gridComponent.min.js
34 ms
languageSelector.min.js
34 ms
lodash.min.js
37 ms
bt
58 ms
languages.css
55 ms
bt
5 ms
flossyco.com SEO score
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flossyco.com 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Flossyco.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.
flossyco.com
Open Graph data is detected on the main page of Flossyco. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: