11.5 sec in total
772 ms
10.6 sec
132 ms
Visit fhi.co.jp now to see the best up-to-date Fhi content for Japan and also check out these interesting facts you probably never knew about fhi.co.jp
株式会社SUBARU(スバル)の企業情報をご紹介しています。投資家情報やCSRについてご紹介しております。
Visit fhi.co.jpWe analyzed Fhi.co.jp page load time and found that the first response time was 772 ms and then it took 10.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fhi.co.jp performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value37.3 s
0/100
25%
Value7.1 s
31/100
10%
Value230 ms
86/100
30%
Value1.633
0/100
15%
Value28.7 s
0/100
10%
772 ms
680 ms
520 ms
370 ms
368 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 96% of them (110 requests) were addressed to the original Fhi.co.jp, 2% (2 requests) were made to Cdnjs.cloudflare.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.9 sec) belongs to the original domain Fhi.co.jp.
Page size can be reduced by 1.4 MB (50%)
2.7 MB
1.4 MB
In fact, the total size of Fhi.co.jp main page is 2.7 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. 45% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 13.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 3.0 kB, which is 18% 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 13.3 kB or 78% of the original size.
Potential reduce by 1.2 MB
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. Obviously, Fhi needs image optimization as it can save up to 1.2 MB or 48% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 76.8 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 76.8 kB or 57% of the original size.
Potential reduce by 64.8 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. Fhi.co.jp needs all CSS files to be minified and compressed as it can save up to 64.8 kB or 84% of the original size.
Number of requests can be reduced by 53 (47%)
113
60
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fhi. 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 10 to 1 for CSS and as a result speed up the page load time.
fhi.co.jp
772 ms
common.css
680 ms
index.css
520 ms
styleswitcher.js
370 ms
rollover.js
368 ms
ga.js
377 ms
jquery.min.js
8 ms
underscore-min.js
11 ms
indexCMS.js
175 ms
mainimage.js
218 ms
ga.js
53 ms
bg_h2.gif
445 ms
site_title.gif
175 ms
bg_headNavi_01.gif
186 ms
head_navi_01.gif
187 ms
head_navi_02.gif
176 ms
head_navi_03.gif
171 ms
head_navi_04.gif
190 ms
bg_headNavi_02.gif
342 ms
head_navi_05.gif
346 ms
txt_search.gif
348 ms
bg_glovalNavi.gif
369 ms
glovalnavi_01.gif
370 ms
main_bg.png
378 ms
main_txt01.png
679 ms
btn1_1.png
518 ms
btn1_2.png
521 ms
btn1_3.png
555 ms
btn1_4.png
554 ms
btn1_5.png
566 ms
btn1_6.png
690 ms
btn1_7.png
694 ms
btn1_8.png
1105 ms
btn1_9.png
1103 ms
glovalnavi_02.gif
753 ms
main_txt02.png
850 ms
btn2_8.png
1034 ms
btn2_1.png
1038 ms
btn2_2.png
1313 ms
btn2_3.png
1524 ms
btn2_4.png
1547 ms
btn2_5.png
1555 ms
btn2_6.png
1652 ms
btn2_7.png
1655 ms
glovalnavi_03.gif
1502 ms
main_txt03.png
1691 ms
btn3_1.png
3204 ms
__utm.gif
11 ms
btn3_2.png
2947 ms
btn3_3.png
3494 ms
btn3_4.png
2818 ms
btn3_5.png
2949 ms
btn3_6.png
3231 ms
btn3_7.png
3598 ms
btn3_8.png
4601 ms
glovalnavi_04.gif
2962 ms
main_txt04.png
3181 ms
btn4_1.png
3286 ms
btn4_2.png
3217 ms
btn4_3.png
5050 ms
btn4_4.png
4304 ms
btn4_5.png
4815 ms
btn4_6.png
3662 ms
btn4_7.png
4306 ms
glovalnavi_05.gif
3724 ms
main_txt05.png
3900 ms
btn5_1.png
4447 ms
btn5_2.png
4928 ms
btn5_3.png
6070 ms
btn_english.gif
4094 ms
main01.jpg
5916 ms
main02.jpg
5320 ms
main03.jpg
5467 ms
main04.jpg
5936 ms
main05.jpg
5545 ms
main06.jpg
5999 ms
main07.jpg
5883 ms
main08.jpg
6857 ms
bg_ctTop.gif
5488 ms
btn_print.gif
5567 ms
txt_font.gif
5632 ms
spacer.gif
5332 ms
btn_font_small.gif
5199 ms
btn_font_medium.gif
4511 ms
btn_font_large.gif
4454 ms
h2_index_01.gif
4458 ms
btn_index_01.gif
4400 ms
btn_index_02.gif
4391 ms
icon_loading.gif
4292 ms
h2_index_02.gif
4196 ms
info_title00.gif
4171 ms
bg_info_li.gif
4129 ms
info_title01.gif
4218 ms
btn_social.gif
3960 ms
btn_index_navi.jpg
3704 ms
btn_index_visitor.jpg
3699 ms
banner_undobu.jpg
3368 ms
banner_philosophy.jpg
3246 ms
banner_kids_top.gif
3212 ms
kids_banner.jpg
3154 ms
copyright.gif
3004 ms
print.css
177 ms
inoutline.css
179 ms
envi.css
189 ms
report.css
190 ms
other.css
178 ms
big.css
175 ms
medium.css
175 ms
small.css
176 ms
glovalnavi_01_ovr.gif
176 ms
glovalnavi_02_ovr.gif
186 ms
glovalnavi_03_ovr.gif
187 ms
glovalnavi_04_ovr.gif
177 ms
glovalnavi_05_ovr.gif
173 ms
fhi.co.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
fhi.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
General
Impact
Issue
Detected JavaScript libraries
fhi.co.jp SEO score
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 Fhi.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 Fhi.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.
fhi.co.jp
Open Graph description is not detected on the main page of Fhi. 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: