5.9 sec in total
715 ms
4.9 sec
195 ms
Welcome to meiji.com homepage info - get ready to check Meiji best content for Japan right away, or after learning these important things about meiji.com
明治ホールディングスWebサイト。グループの基本情報や投資家向け情報からイノベーションの状況、未来に向けたさまざまな取り組み内容まで、明治グループおよび明治ホールディングスの最新情報をお届けしています。
Visit meiji.comWe analyzed Meiji.com page load time and found that the first response time was 715 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 70% of websites can load faster.
meiji.com performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value8.8 s
1/100
25%
Value6.9 s
33/100
10%
Value940 ms
29/100
30%
Value0.376
28/100
15%
Value9.5 s
30/100
10%
715 ms
822 ms
306 ms
653 ms
351 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 81% of them (51 requests) were addressed to the original Meiji.com, 10% (6 requests) were made to Navicast.jp and 8% (5 requests) were made to Meiji.co.jp. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Meiji.co.jp.
Page size can be reduced by 154.1 kB (29%)
532.9 kB
378.8 kB
In fact, the total size of Meiji.com main page is 532.9 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. 25% of websites need less resources to load. Images take 319.5 kB which makes up the majority of the site volume.
Potential reduce by 16.3 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 2.7 kB, which is 12% 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 16.3 kB or 74% of the original size.
Potential reduce by 990 B
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. Meiji images are well optimized though.
Potential reduce by 106.3 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 106.3 kB or 69% of the original size.
Potential reduce by 30.4 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. Meiji.com needs all CSS files to be minified and compressed as it can save up to 30.4 kB or 81% of the original size.
Number of requests can be reduced by 31 (51%)
61
30
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Meiji. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
meiji.com
715 ms
www.meiji.com
822 ms
reset.css
306 ms
style.css
653 ms
gnavi.css
351 ms
footer.css
350 ms
top.css
353 ms
common.js
457 ms
styleswitcher.js
457 ms
swfobject.js
522 ms
s_code.js
567 ms
jquery.js
1611 ms
i_search_assist.js
1179 ms
search_tool.js
1514 ms
NavicastApi.js
787 ms
footer_main.css
180 ms
bg_top.jpg
184 ms
bg_top_content.jpg
333 ms
logo.gif
221 ms
hd_link.gif
222 ms
btn_search.gif
193 ms
header_fontsize.jpg
335 ms
header_fontsize_s.jpg
354 ms
header_fontsize_m.jpg
373 ms
header_fontsize_l.jpg
375 ms
jp_swf_substitution.jpg
1261 ms
gnavi.jpg
941 ms
ic_out.gif
488 ms
ti_new.jpg
517 ms
table_text_rss_off.gif
547 ms
ar_list.jpg
548 ms
tag_update.gif
640 ms
ar_1.jpg
682 ms
ti_pres.jpg
720 ms
tp_pr_hldgs.jpg
722 ms
tag_tse.gif
794 ms
tag_notice.gif
843 ms
tp_pr_meiji.jpg
892 ms
tp_pr_pharma.jpg
895 ms
bn_2020_off.gif
947 ms
bn_su17_off.gif
1006 ms
bn_pst_off.gif
1066 ms
bn_lib_off.gif
1069 ms
bn_ind_off.gif
1090 ms
bn_sp_off.gif
1100 ms
side_ti_gr.gif
1168 ms
bn_group_meiji.jpg
1252 ms
bn_group_mspharma.jpg
1253 ms
ft_link.gif
1250 ms
ft_line.jpg
1254 ms
ft_logo.gif
1299 ms
ft_copy.gif
1218 ms
s54244914830196
82 ms
ac.css
18 ms
jquery-ui-1.8.2.custom.min.js
6 ms
NavicastTmg.php
201 ms
print.css
156 ms
NavicastApi2.php
200 ms
NavicastApi2.php
723 ms
fsize_s.css
156 ms
fsize_l.css
156 ms
NavicastApi2.php
202 ms
2.002.js
595 ms
meiji.com 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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
Links do not have a discernible name
meiji.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
meiji.com 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
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Meiji.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 Meiji.com main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
meiji.com
Open Graph description is not detected on the main page of Meiji. 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: