10.4 sec in total
764 ms
9.5 sec
190 ms
Welcome to ifec-jp.com homepage info - get ready to check Ifec Jp best content right away, or after learning these important things about ifec-jp.com
生命(いのち)ある地球との調和と共生「International Flower Essence Conference 2014 in Japan」国際フラワーエッセンスコンファレンス日本にて開催!世界各国のエッセンスプロデューサーが一堂に集まります。
Visit ifec-jp.comWe analyzed Ifec-jp.com page load time and found that the first response time was 764 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
ifec-jp.com performance score
name
value
score
weighting
Value2.2 s
76/100
10%
Value4.2 s
45/100
25%
Value3.7 s
85/100
10%
Value40 ms
100/100
30%
Value0
100/100
15%
Value3.7 s
90/100
10%
764 ms
335 ms
514 ms
364 ms
34 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 56% of them (60 requests) were addressed to the original Ifec-jp.com, 20% (22 requests) were made to Static.xx.fbcdn.net and 19% (20 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (6.4 sec) relates to the external source External.xx.fbcdn.net.
Page size can be reduced by 64.6 kB (11%)
569.4 kB
504.9 kB
In fact, the total size of Ifec-jp.com main page is 569.4 kB. 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 451.6 kB which makes up the majority of the site volume.
Potential reduce by 10.8 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 10.8 kB or 76% of the original size.
Potential reduce by 8.5 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. Ifec Jp images are well optimized though.
Potential reduce by 32.1 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 32.1 kB or 37% of the original size.
Potential reduce by 13.2 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. Ifec-jp.com needs all CSS files to be minified and compressed as it can save up to 13.2 kB or 77% of the original size.
Number of requests can be reduced by 40 (38%)
106
66
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ifec Jp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
ifec-jp.com
764 ms
screen.css
335 ms
ifec_com.css
514 ms
ifec_top.css
364 ms
jquery.min.js
34 ms
carousel.js
364 ms
base.css
183 ms
common.css
169 ms
header.html
189 ms
footer.html
174 ms
navi_blank.jpg
183 ms
navi_home.jpg
184 ms
navi_what.jpg
167 ms
navi_introduce.jpg
334 ms
navi_schedule.jpg
342 ms
navi_tickets.jpg
351 ms
navi_accses.jpg
364 ms
navi_movie.jpg
363 ms
img_topbg_ver2.jpg
907 ms
img_catch1.gif
501 ms
bnr_introduce.gif
512 ms
bnr_tickets.gif
523 ms
bnr_topinfo.gif
547 ms
face_andreas.jpg
543 ms
face_sabina.jpg
666 ms
face_ian.jpg
681 ms
face_tanmaya.jpg
698 ms
face_steve.jpg
723 ms
face_isha.jpg
731 ms
face_ruth.jpg
832 ms
face_ann.jpg
850 ms
face_lila_2.jpg
871 ms
face_jane.jpg
904 ms
face_sky.jpg
917 ms
face_sandra.jpg
1001 ms
face_julian.jpg
1020 ms
face_lucy.jpg
1086 ms
face_maryanne.jpg
1094 ms
img_essence.jpg
1094 ms
icon_note.gif
1101 ms
img_topbg_orei.jpg
1162 ms
analytics.js
27 ms
prev.gif
1126 ms
next.gif
1154 ms
collect
14 ms
likebox.php
345 ms
ifec_footer.css
1246 ms
footer.js
1248 ms
bnr_head_logo.jpg
1245 ms
download.gif
1246 ms
download_eng.gif
1243 ms
410ucuAGgaJ.css
284 ms
tSbl8xBI27R.css
355 ms
Czh0gDTFcBt.css
424 ms
Ek6lpayKeeB.css
557 ms
EHcHntQ3U3v.css
495 ms
Xn9s9VoXEK-.css
488 ms
EoarYgA68t4.css
563 ms
q68gy-v_YMF.js
619 ms
FJmpeSpHpjS.js
640 ms
0wM5s1Khldu.js
576 ms
1bNoFZUdlYZ.js
577 ms
njO1TPvGzoR.js
663 ms
1QuX41zDRrx.js
666 ms
Oagsvfb4VWi.js
696 ms
LTv6ZK-5zxz.js
824 ms
1FCa-btixu2.js
695 ms
10401413_714511981942717_4102604200222227136_n.png
527 ms
safe_image.php
4011 ms
safe_image.php
6444 ms
1461815_613864332007483_465063711_n.png
654 ms
11933482_522502271236052_3345841226218644816_n.jpg
785 ms
12072759_10153303666299022_7417024703491603195_n.jpg
712 ms
11143556_687261928073697_6645143917576809630_n.jpg
772 ms
12313971_511431225690817_2133789926173277422_n.jpg
741 ms
1977084_1706727749570029_7089190944441222656_n.jpg
711 ms
10678863_659789920785193_3305145090727387349_n.jpg
779 ms
625564_333161710108599_1278064694_n.jpg
837 ms
12540914_1542247762753752_8066437196786071335_n.jpg
779 ms
12227168_1523317941317929_4075199798153604560_n.jpg
847 ms
1376537_1379271498976596_92927031_n.jpg
838 ms
12642938_1026003174126928_615073240553151419_n.jpg
904 ms
12631558_1026003357460243_589953142896942578_n.jpg
905 ms
10264541_1026004204126825_9128833081508962890_n.jpg
922 ms
12642743_1026005050793407_1315272817415412190_n.jpg
1064 ms
1508021_758516480852025_5279909715213997428_n.jpg
1046 ms
10346108_758516550852018_8526274525098943007_n.jpg
1026 ms
10421473_758516620852011_4464961118992832952_n.jpg
1163 ms
10405584_748816251822048_7366639251087167697_n.jpg
1093 ms
wL6VQj7Ab77.png
87 ms
s7jcwEQH7Sx.png
90 ms
QDwYpIaRyfG.png
87 ms
K00K-UgnsKu.png
88 ms
ifec_logo.jpg
187 ms
icon_square.gif
175 ms
icon_circle.gif
182 ms
icon_square_s.gif
183 ms
I6-MnjEovm5.js
69 ms
pQrUxxo5oQp.js
136 ms
bnr_introduce_off.gif
355 ms
bnr_tickets_off.gif
360 ms
bnr_info_off.gif
354 ms
navi_home_over.jpg
353 ms
navi_what_over.jpg
355 ms
navi_introduce_over.jpg
366 ms
navi_schedule_over.jpg
514 ms
navi_tickets_over.jpg
527 ms
navi_accses_over.jpg
529 ms
ifec-jp.com 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
ifec-jp.com 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
Browser errors were logged to the console
ifec-jp.com SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ifec-jp.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ifec-jp.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.
ifec-jp.com
Open Graph description is not detected on the main page of Ifec Jp. 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: