11.8 sec in total
529 ms
10.4 sec
892 ms
Visit f-e-i.jp now to see the best up-to-date F E I content for Japan and also check out these interesting facts you probably never knew about f-e-i.jp
横浜と六本木でギャラリー、アートミュージアムを展開しています。コレクション展や企画展の他、貸しギャラリーとしても利用できます。
Visit f-e-i.jpWe analyzed F-e-i.jp page load time and found that the first response time was 529 ms and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
f-e-i.jp performance score
name
value
score
weighting
Value6.0 s
4/100
10%
Value16.6 s
0/100
25%
Value18.2 s
0/100
10%
Value780 ms
37/100
30%
Value0
100/100
15%
Value8.7 s
36/100
10%
529 ms
780 ms
319 ms
323 ms
344 ms
Our browser made a total of 179 requests to load all elements on the main page. We found that 53% of them (95 requests) were addressed to the original F-e-i.jp, 37% (67 requests) were made to Maps.google.com and 4% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain F-e-i.jp.
Page size can be reduced by 706.9 kB (17%)
4.1 MB
3.4 MB
In fact, the total size of F-e-i.jp main page is 4.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. 70% of websites need less resources to load. Images take 3.2 MB which makes up the majority of the site volume.
Potential reduce by 117.6 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 117.6 kB or 90% of the original size.
Potential reduce by 55.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. F E I images are well optimized though.
Potential reduce by 486.5 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 486.5 kB or 68% of the original size.
Potential reduce by 46.9 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. F-e-i.jp needs all CSS files to be minified and compressed as it can save up to 46.9 kB or 85% of the original size.
Number of requests can be reduced by 70 (40%)
173
103
The browser has sent 173 CSS, Javascripts, AJAX and image requests in order to completely render the main page of F E I. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
f-e-i.jp
529 ms
www.f-e-i.jp
780 ms
normalize.css
319 ms
common.css
323 ms
perfect-scrollbar.css
344 ms
index.css
358 ms
jquery2.js
547 ms
TweenMax.min.js
561 ms
CustomEase.js
674 ms
jquery.gsap.min.js
685 ms
smart-crossfade.js
681 ms
common.js
671 ms
perfect-scrollbar.jquery.js
864 ms
jquery.inview.min.js
890 ms
SplitText.min.js
1009 ms
js
24 ms
googlemap.js
1026 ms
index.js
1026 ms
mv_anim_title.png
179 ms
mv1.jpg
1133 ms
mv2.jpg
1021 ms
mv3.jpg
1369 ms
mv_title.png
353 ms
nav_bg.png
381 ms
side_ac_btn.png
536 ms
side_c_btn.png
694 ms
inner_sns1.png
723 ms
sns_musium.png
900 ms
sns_gallery.png
1083 ms
sns_hfg.png
1071 ms
inner_sns2.png
1247 ms
art1_bg.jpg
2040 ms
common_fac1.png
1427 ms
art1_sec1_logo.png
1446 ms
fb3c9a896e168280021797292db503e9-270x123.jpg
1472 ms
common_fac2.png
1617 ms
art1_sec2_logo.png
1700 ms
common_fac3.png
1766 ms
art1_sec3_logo.png
1798 ms
art2_ph.jpg
1979 ms
art2_name.png
1936 ms
art2_sign.png
2061 ms
art3_sec1_bg.jpg
2243 ms
common_logo1.png
2139 ms
art3_sec1_ph1.jpg
2481 ms
art3_sec1_ph2.jpg
2617 ms
art3_sec2_bg.jpg
2582 ms
common_logo2.png
2380 ms
art3_sec2_ph1.jpg
2777 ms
art3_sec2_ph2.jpg
3148 ms
art3_sec3_bg.jpg
3002 ms
common_logo3.png
2844 ms
art3_sec3_ph1.jpg
3288 ms
art3_sec3_ph2.jpg
3484 ms
art4_sec1_logo1.png
2962 ms
art4_sec1_logo2.png
2826 ms
art4_sec1_logo3.png
3018 ms
a.png
2946 ms
b.png
2801 ms
c.png
2810 ms
d.png
2716 ms
e.png
2726 ms
f.png
2767 ms
g.png
2757 ms
h.png
2729 ms
i.png
2625 ms
j.png
2615 ms
k.png
2684 ms
l.png
2711 ms
m.png
2690 ms
n.png
2565 ms
o.png
2488 ms
p.png
2557 ms
q.png
2635 ms
r.png
2539 ms
s.png
2523 ms
t.png
2474 ms
u.png
2482 ms
v.png
2554 ms
w.png
2510 ms
x.png
2444 ms
y.png
2365 ms
z.png
2264 ms
art7_bg.jpg
3648 ms
art5_sec1_bg.jpg
2423 ms
art5_ph1.jpg
2420 ms
art5_sec2_bg.jpg
2335 ms
art5_ph2.jpg
2354 ms
art5_sec3_bg.jpg
2195 ms
art5_ph3.jpg
2662 ms
art6_sec1_ph1.jpg
2677 ms
art6_sec2_ph1.jpg
2672 ms
art6_sec3_ph1.jpg
2645 ms
common.js
8 ms
util.js
25 ms
stats.js
7 ms
AuthenticationService.Authenticate
287 ms
map.js
7 ms
marker.js
71 ms
onion.js
52 ms
openhand_8_8.cur
31 ms
ViewportInfoService.GetViewportInfo
197 ms
controls.js
26 ms
ViewportInfoService.GetViewportInfo
189 ms
ViewportInfoService.GetViewportInfo
186 ms
transparent.png
41 ms
css
35 ms
google4.png
64 ms
map_icon1.png
217 ms
map_icon2.png
346 ms
map_icon3.png
347 ms
mapcnt6.png
64 ms
sv5.png
65 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
41 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
48 ms
Hgo13k-tfSpn0qi1SFdUfbO3LdcAZYWl9Si6vvxL-qU.woff
49 ms
d-6IYplOFocCacKzxwXSOLO3LdcAZYWl9Si6vvxL-qU.woff
48 ms
tmapctrl.png
63 ms
vt
96 ms
vt
122 ms
vt
93 ms
vt
105 ms
vt
97 ms
vt
160 ms
vt
185 ms
vt
194 ms
vt
189 ms
vt
197 ms
vt
286 ms
vt
306 ms
vt
277 ms
vt
295 ms
vt
311 ms
vt
310 ms
vt
406 ms
vt
406 ms
vt
442 ms
vt
464 ms
tmapctrl4.png
37 ms
google_white5.png
38 ms
vt
522 ms
vt
437 ms
vt
584 ms
vt
474 ms
vt
510 ms
vt
514 ms
vt
515 ms
vt
550 ms
vt
618 ms
vt
606 ms
vt
620 ms
vt
589 ms
vt
662 ms
vt
719 ms
vt
707 ms
vt
679 ms
vt
679 ms
vt
644 ms
vt
727 ms
vt
750 ms
vt
750 ms
vt
681 ms
vt
703 ms
vt
688 ms
vt
753 ms
vt
735 ms
vt
700 ms
vt
687 ms
vt
724 ms
vt
690 ms
vt
711 ms
vt
699 ms
vt
645 ms
vt
668 ms
vt
644 ms
vt
657 ms
vt
718 ms
vt
588 ms
vt
616 ms
f-e-i.jp accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
f-e-i.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
f-e-i.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise F-e-i.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 F-e-i.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.
f-e-i.jp
Open Graph data is detected on the main page of F E I. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: