6.7 sec in total
625 ms
4.1 sec
1.9 sec
Click here to check amazing FLYMEe content for Japan. Otherwise, check out these important facts you probably never knew about flymee.jp
日本最大級・正規取扱ブランド数No.1の家具通販・インテリア通販。国内外のデザイナーズ家具をはじめ、ソファー、チェア、テーブル、ベッド、収納家具、カーテン、ラグ、照明から食器・時計などインテリア雑貨まで様々な家具・インテリアが揃う通販サイトです。
Visit flymee.jpWe analyzed Flymee.jp page load time and found that the first response time was 625 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
flymee.jp performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value8.5 s
1/100
25%
Value9.3 s
12/100
10%
Value670 ms
45/100
30%
Value0
100/100
15%
Value13.4 s
11/100
10%
625 ms
293 ms
302 ms
449 ms
297 ms
Our browser made a total of 107 requests to load all elements on the main page. We found that 87% of them (93 requests) were addressed to the original Flymee.jp, 3% (3 requests) were made to Google-analytics.com and 2% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Flymee.jp.
Page size can be reduced by 749.7 kB (44%)
1.7 MB
953.5 kB
In fact, the total size of Flymee.jp main page is 1.7 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 940.0 kB which makes up the majority of the site volume.
Potential reduce by 293.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. This page needs HTML code to be minified as it can gain 150.2 kB, which is 47% 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 293.7 kB or 92% of the original size.
Potential reduce by 133.9 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. Obviously, FLYMEe needs image optimization as it can save up to 133.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 161.7 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 161.7 kB or 64% of the original size.
Potential reduce by 160.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. Flymee.jp needs all CSS files to be minified and compressed as it can save up to 160.3 kB or 84% of the original size.
Number of requests can be reduced by 37 (36%)
103
66
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FLYMEe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
flymee.jp
625 ms
reset.css
293 ms
common.css
302 ms
contents.css
449 ms
table.css
297 ms
popup.css
305 ms
ranking.css
313 ms
print.css
438 ms
payment.css
443 ms
button_new.css
456 ms
crossSlide.css
458 ms
showcase.css
468 ms
jquery-1.11.3.min.js
731 ms
jquery-migrate-1.2.1.min.js
584 ms
jquery.easing.1.3.min.js
587 ms
jquery.mousewheel.min.js
588 ms
jquery-color.js
588 ms
placeholder.js
617 ms
win_op.js
751 ms
site.js
751 ms
jquery.aw-showcase.js
750 ms
jquery.tile.min.js
749 ms
jquery.lazyload.min.js
769 ms
ld.js
21 ms
jquery.smooth_scroll.js
870 ms
crossSlide.js
883 ms
jquery.pause.min.js
884 ms
494 ms
s_retargeting.js
624 ms
event
18 ms
event
456 ms
fbds.js
48 ms
flymeelogo_180.png
357 ms
search_button.jpg
366 ms
12211722_5677b6ace1cb8.jpg
383 ms
12211722_5677b6b53d1d1.jpg
383 ms
12211722_5677b6be9bd03.jpg
382 ms
12211723_5677b71748e52.jpg
357 ms
12211723_5677b71f829ea.jpg
386 ms
12211729_5677b864bf323.jpg
388 ms
12211729_5677b8701c81e.jpg
471 ms
12211729_5677b87d1497b.jpg
445 ms
12211729_5677b886c2876.jpg
445 ms
12211730_5677b89004ed7.jpg
445 ms
12211730_5677b89ad790e.jpg
456 ms
12211730_5677b8a52bf33.jpg
457 ms
12211736_5677b9f7661fb.jpg
591 ms
12211730_5677b8b72261d.jpg
594 ms
12211735_5677b9eee1912.jpg
593 ms
12211736_5677ba04e3e28.jpg
604 ms
12211736_5677ba1f1c2af.jpg
608 ms
12211736_5677ba15b309e.jpg
624 ms
12211737_5677ba33d6bc5.jpg
737 ms
12211736_5677ba28951af.jpg
738 ms
loading.gif
742 ms
top-ranking.gif
750 ms
12061915_56640aac7d6d5.jpg
750 ms
05261915_556447d422c42.jpg
780 ms
04251842_535a2e1652828.jpg
883 ms
12061912_56640a08df1a8.jpg
883 ms
10111902_561a33cb2c82e.jpg
884 ms
12021036_565e4b11575f6.jpg
900 ms
04132115_534a7fe71e001.jpg
900 ms
04262242_535bb7dac9a2e.jpg
936 ms
08161709_53ef11b288ee9.jpg
1029 ms
analytics.js
36 ms
05012251_53625147277ae.jpg
1028 ms
09011344_55e52d304120b.jpg
1027 ms
10211032_5626eb1692bea.jpg
1033 ms
linkid.js
226 ms
80 ms
12061733_5482bf646fa02.jpg
697 ms
03091751_54fd5f117d404.jpg
728 ms
12061913_56640a51513da.jpg
808 ms
01182200_569ce2014fc11.jpg
804 ms
10282347_508d4578e7d16.jpg
803 ms
05041958_53661d3dab908.jpg
814 ms
09011653_55e5596b2e196.jpg
814 ms
collect
35 ms
10111331_5619e62b17173.jpg
859 ms
collect
62 ms
12061735_5482bfe0a35cf.jpg
887 ms
imageloader-mini.gif
888 ms
dot.gif
898 ms
logo_mini_gray.png
891 ms
amex_bonus_150.png
890 ms
heart_wh_28.png
943 ms
ga-audiences
35 ms
key_wh_28.png
886 ms
cart_wh_28.png
885 ms
question_wh_28.png
882 ms
arrow_right_s.png
887 ms
arrow_right_g.png
886 ms
facebook-gray-45.png
942 ms
cs_journal_standard_furniture_02.jpg
1327 ms
cs_calligaris13.jpg
1473 ms
cs_crash_gate_05.jpg
1176 ms
dis.aspx
351 ms
5 ms
12061915_56640aac7a256.jpg
150 ms
12072243_52a326031acd4.jpg
161 ms
01210939_56a028cca2712.jpg
150 ms
02061442_5111ed328c57a.jpg
160 ms
07152101_55a64ba867d4d.jpg
158 ms
07132123_55a3adcfa178f.jpg
160 ms
03091751_54fd5f1179a8e.jpg
297 ms
01091806_5690cd86f1dbb.jpg
295 ms
flymee.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
flymee.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
flymee.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flymee.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 Flymee.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.
flymee.jp
Open Graph data is detected on the main page of FLYMEe. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: