6 sec in total
1.4 sec
4.2 sec
302 ms
Visit aeplan.co.jp now to see the best up-to-date Aeplan content for Japan and also check out these interesting facts you probably never knew about aeplan.co.jp
バイオテクノロジー・ライフサイエンス分野を中心としたコンベンション・学会運営、また 学会運営を軸とした広告代理店業を行っております。
Visit aeplan.co.jpWe analyzed Aeplan.co.jp page load time and found that the first response time was 1.4 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
aeplan.co.jp performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value6.8 s
7/100
25%
Value7.2 s
30/100
10%
Value1,290 ms
18/100
30%
Value0.069
96/100
15%
Value6.9 s
54/100
10%
1431 ms
383 ms
391 ms
29 ms
773 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 89% of them (63 requests) were addressed to the original Aeplan.co.jp, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Aeplan.co.jp.
Page size can be reduced by 99.0 kB (15%)
649.8 kB
550.8 kB
In fact, the total size of Aeplan.co.jp main page is 649.8 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. 20% of websites need less resources to load. Images take 507.3 kB which makes up the majority of the site volume.
Potential reduce by 15.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 15.8 kB or 75% of the original size.
Potential reduce by 13.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. Aeplan images are well optimized though.
Potential reduce by 57.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 57.1 kB or 54% of the original size.
Potential reduce by 12.7 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. Aeplan.co.jp needs all CSS files to be minified and compressed as it can save up to 12.7 kB or 75% of the original size.
Number of requests can be reduced by 29 (43%)
68
39
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aeplan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
aeplan.co.jp
1431 ms
index.css
383 ms
rhinoslider-1.05.css
391 ms
jquery.min.js
29 ms
rhinoslider-1.05.min.js
773 ms
mousewheel.js
389 ms
easing.js
590 ms
fadeover.js
569 ms
fb.js
577 ms
base.css
199 ms
common.css
427 ms
conversion.js
17 ms
bg_all.gif
391 ms
bg_head.png
205 ms
mainlogo1.png
375 ms
hdr_icon01.gif
193 ms
gnav01.png
195 ms
gnav02.png
201 ms
gnav03.png
386 ms
gnav04.png
388 ms
gnav05.png
388 ms
gnav06.png
393 ms
main01.jpg
1538 ms
main02.jpg
1340 ms
mpkRKLgIjdBQ_s.jpg
773 ms
mmenu_conv.jpg
960 ms
mmenu_ad.jpg
582 ms
mmenu_topics.jpg
786 ms
rtit01.gif
777 ms
YnxBPHVqYaXe_s.jpg
965 ms
SzzSIGeWtOEH_s.jpg
1165 ms
ZHQvxnTlvemk_s.jpg
1178 ms
zdfVGRHspRxY_s.jpg
1343 ms
EpCHzukrRtdS_s.jpg
1157 ms
umAOnPblAVxJ_s.jpg
1351 ms
hSgCgSDLlsCX_s.jpg
1359 ms
kEInEioMjTjU_s.jpg
1376 ms
LqGEVixrKFom_s.jpg
1530 ms
btn_topicslist.gif
1533 ms
ltit01.gif
1542 ms
btn_list.gif
1554 ms
bg_result.jpg
1572 ms
btn_res01.gif
1721 ms
btn_res02.gif
1721 ms
bnt_fb.gif
1724 ms
bnr_twitter.gif
1733 ms
bnr_gplus.gif
1745 ms
analytics.js
34 ms
48 ms
feed
296 ms
bnr_blog.jpg
1702 ms
collect
20 ms
44 ms
collect
55 ms
btn_pagetop.gif
1719 ms
bg_footer.gif
1720 ms
ftr_ae.gif
1719 ms
ftr_tit_tokyo.gif
1726 ms
btn_map.gif
1572 ms
ftr_ex_tokyo.gif
1584 ms
ftr_tit_osaka.gif
1712 ms
ftr_ex_osaka.gif
1719 ms
fm01.gif
1726 ms
fm02.gif
1729 ms
fm03.gif
1556 ms
fm04.gif
1393 ms
fm05.gif
1510 ms
fm06.gif
1512 ms
arrow_left.gif
1346 ms
arrow_right.gif
1348 ms
logo_no_ae.jpg
1176 ms
aeplan.co.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
aeplan.co.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
Browser errors were logged to the console
aeplan.co.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aeplan.co.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 Aeplan.co.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.
aeplan.co.jp
Open Graph description is not detected on the main page of Aeplan. 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: