5.4 sec in total
297 ms
4.4 sec
752 ms
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 297 ms and then it took 5.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.0 s
49/100
10%
Value4.0 s
49/100
25%
Value6.9 s
34/100
10%
Value1,220 ms
20/100
30%
Value0
100/100
15%
Value13.9 s
10/100
10%
297 ms
866 ms
297 ms
63 ms
25 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 4% of them (4 requests) were addressed to the original Flymee.jp, 89% (81 requests) were made to Static2.flymee.jp and 2% (2 requests) were made to Clarity.ms. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Static2.flymee.jp.
Page size can be reduced by 481.7 kB (13%)
3.6 MB
3.2 MB
In fact, the total size of Flymee.jp main page is 3.6 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. 65% of websites need less resources to load. Images take 2.8 MB which makes up the majority of the site volume.
Potential reduce by 210.2 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 80.8 kB, which is 34% 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 210.2 kB or 87% of the original size.
Potential reduce by 271.3 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. FLYMEe images are well optimized though.
Potential reduce by 210 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 0 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. Flymee.jp has all CSS files already compressed.
Number of requests can be reduced by 26 (30%)
88
62
The browser has sent 88 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 6 to 1 for JavaScripts and as a result speed up the page load time.
flymee.jp
297 ms
flymee.jp
866 ms
app.css
297 ms
a8sales.js
63 ms
js
25 ms
desktop_app.js
1042 ms
core.js
192 ms
6vo8fj0ysr
556 ms
header_01_logo.svg
193 ms
search_gray.svg
788 ms
fav_2.svg
180 ms
cart_2.svg
179 ms
64c3fc15fad35186dc480b4875ad1885.png
179 ms
d605adfd5cbccb3e538d4c003e15ea52.png
181 ms
df3a2bb372d51b58c6ecffbd428dfab6.png
180 ms
bc30fa5b4e78047d2f77fc78ecfbf43b.png
182 ms
1961b2149ee736ed14a56ffddbebf6de.png
182 ms
32a58d815e468fa795189f526261c183.png
219 ms
dba23f87bd807737314ebf6c289ba4b7.png
181 ms
8293038d9e2ac1d7a6165a65ebed9d20.png
798 ms
d2089f8d2ab7d1c022106ed320d22fcd.png
183 ms
81aaa89332b60519b54ca7e1d12e2f36.png
183 ms
7567f163ffb8728983b65271dee8c2f8.png
182 ms
a156c83a989f91c4ec40152475977000.png
184 ms
56769222e6b1fa460fbc2382f1117932.png
224 ms
6d37338a90419ad7c787e4dd9f084669.png
184 ms
461ccbf8cb4b9c24230e44e61a205996.png
216 ms
64ebc04777dd8452b9f1df4c2bef1c48.png
217 ms
c5862597936ee7949417d97ff2ae5c33.png
218 ms
5aeb0ad55e970a43f63ddc5deedb3b32.png
219 ms
609c66c77fc6ccb45e40af175a11979a.png
218 ms
87cad439ac116884f134d92771e1f8a3.jpg
219 ms
92c05bb9bc594b38d377fa9968b07e5a.jpg
220 ms
9640852b282d260aa1e0835f3dda6eb6.jpg
221 ms
80911e4419a8af005deaaf46ff8bf765.jpg
223 ms
e557413b34f0996269876cab5647ef78.jpg
222 ms
e4d6ba0733eb8592f15766c5844bffaf.jpg
223 ms
a752171c0065549301fadc6691932eb1.jpg
224 ms
36560095169d3c5f108589972ae7a09c.jpg
226 ms
efb0396a8df37902f83a8057fdd89224.jpg
225 ms
3b94299a7e2faf3d01dc6e161a5772ff.jpg
227 ms
attention_triangle_2.svg
225 ms
a6bf97c4b845710ff3443dab6fea243b.png
229 ms
4abd275e613e18d617c0236de135081b.png
230 ms
fbevents.js
20 ms
c64bdaff1deeeeaac35079d77dca4d08.png
64 ms
29607ba7ba3b8be3b63d39a8dc2bcc71.png
59 ms
151e48f9cf4e3930d9d9f0b7b8f3660b.png
57 ms
ce4abeea5cceb18f6efee24aa75e1bc0.jpg
58 ms
c2523d278b068085143252c79e5eaff9.png
59 ms
b226686d4acd32ff3d917562bad7f15d.jpg
57 ms
da053bf2c2afa0b6deae02c320e456aa.jpg
59 ms
28510b0b0b517165b306012da2d9b764.png
58 ms
78283d4b953b337eba124244c153639e.png
59 ms
42e7198c597eb0ee35a09a6d646fa7fc.jpg
59 ms
8edb260e65abf6527226e4efb4187d2b.jpg
58 ms
8e1d2af69171134b07b4ff6c4d57973e.png
61 ms
217481dc22a9d35ee3cd6d47783d6479.jpg
59 ms
ae9d554da57032ea2c411f86f95e7fef.jpg
59 ms
13b1a87b09a1460fd1229291d3f922ba.png
28 ms
d26bd13800d9a4a4e6188656fa39595b.jpg
28 ms
eb2180b8eb02632f5ea472e12351364d.png
29 ms
9bf51c3ca3f2fc7f4378a07adee0819b.jpg
28 ms
0dba56016c589fd3e617e56605de8d67.png
30 ms
2c754e640039380177338b627dcc3ec3.jpg
28 ms
f27b255205b39705b1a48585d74e1047.jpg
29 ms
4bf08136091c118a83d9052a21afb0e9.jpg
28 ms
201901211904478385.jpg
28 ms
201812111453241309.jpg
919 ms
201811121410269771.jpg
1249 ms
202206021420127259.jpg
898 ms
201902271623510597.jpg
955 ms
202405171944290648.jpg
1520 ms
201905290926178974.jpg
1192 ms
202211281823346533.jpg
1859 ms
201811171112547371.jpg
1681 ms
201811141348261801.jpg
1878 ms
201811201700089891.jpg
1819 ms
202302031041066972.jpg
1247 ms
202208311623476598.jpg
2025 ms
201909061926271928.jpg
2126 ms
202104070802595959.jpg
2438 ms
201810151305586331.jpg
2601 ms
201901151758129455.jpg
2474 ms
201812121144361883.jpg
2490 ms
6d023f6806932876a44f313e94c552c4.jpg
2024 ms
7862c67807992b29df4319bf420ffdfc.jpg
2026 ms
6973ec39045ba3a335b6d2a6ab61c677.jpg
2647 ms
c726d8f3ca9f8965e780f8cb4ad9092c.jpg
2123 ms
logo-flymee.svg
2124 ms
clarity.js
16 ms
flymee.jp 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.
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
Browser errors were logged to the console
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: