7.4 sec in total
1.2 sec
5.9 sec
305 ms
Click here to check amazing Fluxy content. Otherwise, check out these important facts you probably never knew about fluxy.jp
誕生日用の花束をお探しならバースデーフラワーショップの代官山FLUXYへどうぞ
Visit fluxy.jpWe analyzed Fluxy.jp page load time and found that the first response time was 1.2 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fluxy.jp performance score
1226 ms
347 ms
368 ms
581 ms
410 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 84% of them (94 requests) were addressed to the original Fluxy.jp, 6% (7 requests) were made to Static.xx.fbcdn.net and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Fluxy.jp.
Page size can be reduced by 224.4 kB (12%)
1.8 MB
1.6 MB
In fact, the total size of Fluxy.jp main page is 1.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. 50% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 42.7 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 42.7 kB or 83% of the original size.
Potential reduce by 4.4 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. Fluxy images are well optimized though.
Potential reduce by 135.0 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 135.0 kB or 68% of the original size.
Potential reduce by 42.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. Fluxy.jp needs all CSS files to be minified and compressed as it can save up to 42.3 kB or 86% of the original size.
Number of requests can be reduced by 48 (44%)
110
62
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fluxy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
fluxy.jp
1226 ms
common.css
347 ms
jquery.lightbox-0.5.css
368 ms
css.js
581 ms
navi.js
410 ms
win_op.js
419 ms
site.js
688 ms
roll.js
549 ms
css_browser_selector.js
609 ms
jquery.js
1476 ms
jquery.lightbox-0.5.js
910 ms
bsn.Crossfader.js
737 ms
import.css
422 ms
conversion.js
20 ms
s_retargeting.js
523 ms
main.css
561 ms
index.css
184 ms
products.css
173 ms
under.css
204 ms
under02.css
327 ms
mypage.css
345 ms
window.css
366 ms
bg.jpg
274 ms
logo.jpg
231 ms
tel_fluxy.jpg
255 ms
nav01_on.jpg
471 ms
nav_shadow.jpg
249 ms
arrow.jpg
242 ms
white.jpg
444 ms
pink.jpg
461 ms
red.jpg
442 ms
yellow.jpg
474 ms
other.jpg
467 ms
nav204_on.jpg
624 ms
nav203_on.jpg
629 ms
nav202_on.jpg
659 ms
nav201_on.jpg
650 ms
a_banner.jpg
1221 ms
b_banner.jpg
896 ms
youto_ttl.jpg
807 ms
cat_bottom.jpg
823 ms
style_ttl.jpg
834 ms
patissere.jpg
1053 ms
uca.jpg
1149 ms
uca01.jpg
1197 ms
okuranaito.jpg
1207 ms
kuno.jpg
1106 ms
hanaya6.jpg
1450 ms
facebook_qr_fluxy.gif
1376 ms
top_banner03.jpg
2237 ms
kanreki_banner.jpg
2177 ms
newflower_ttl.jpg
1583 ms
01271820_4d4138d620071.jpg
1967 ms
01271543_4d41140e8e20a.jpg
1832 ms
01251730_4d3e8a22b19d4.jpg
2232 ms
01251741_4d3e8cc1bbbdb.jpg
2149 ms
birthday_ttl.jpg
2041 ms
analytics.js
22 ms
07201507_4c453d20661ca.jpg
2343 ms
all.js
16 ms
79 ms
collect
47 ms
134 ms
likebox.php
190 ms
xd_arbiter.php
35 ms
xd_arbiter.php
73 ms
112 ms
07201454_4c453a1c7634f.jpg
2247 ms
07201446_4c45381e220e6.jpg
2299 ms
07201511_4c453df50edbe.jpg
2320 ms
detail_line.jpg
2192 ms
news_ttl.jpg
2144 ms
ebiMDO3r-8l.css
19 ms
q68gy-v_YMF.js
25 ms
FJmpeSpHpjS.js
46 ms
0wM5s1Khldu.js
60 ms
1bNoFZUdlYZ.js
63 ms
I6-MnjEovm5.js
8 ms
pQrUxxo5oQp.js
4 ms
footer_ttl01.gif
2142 ms
footer_ttl02.gif
2160 ms
footer_ttl03.gif
2179 ms
footer_ttl04.gif
2212 ms
headerbg.jpg
2261 ms
nav02_on.jpg
2284 ms
blogroll01_on.jpg
2143 ms
nav03_on.jpg
2144 ms
nav04_on.jpg
2181 ms
nav05_on.jpg
2223 ms
nav2_bg.jpg
2104 ms
container_bg.jpg
2129 ms
side_banner01.jpg
2117 ms
cat_bg.jpg
2051 ms
main_bg.jpg
1975 ms
newflower01.jpg
1980 ms
footer_ttlbg.gif
1991 ms
footer.jpg
1972 ms
basis_on.jpg
187 ms
product_on.jpg
191 ms
customer_on.jpg
226 ms
order_on.jpg
187 ms
sales_on.jpg
179 ms
mail_on.jpg
195 ms
contents_on.jpg
362 ms
mainpage_on.gif
368 ms
sitecheck_on.gif
369 ms
logout.gif
375 ms
btn_search_on.jpg
392 ms
btn_regist_on.jpg
454 ms
btn_csv_on.jpg
533 ms
arrow_left.jpg
565 ms
arrow_right.jpg
551 ms
fluxy.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fluxy.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Fluxy.jp 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.
fluxy.jp
Open Graph description is not detected on the main page of Fluxy. 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: