8.6 sec in total
763 ms
7.5 sec
299 ms
Click here to check amazing Foh content. Otherwise, check out these important facts you probably never knew about foh.jp
Full Of Harmony OFFICIAL WEB SITEでは、出演、リリース情報他、様々なコンテンツをご用意しています。さらにオフィシャルファンクラブ「JOYSTICK」会員も募集中!会員限定イベントやチケット先行など、詳しくは当サイトをご覧ください。
Visit foh.jpWe analyzed Foh.jp page load time and found that the first response time was 763 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
foh.jp performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value37.4 s
0/100
25%
Value11.5 s
5/100
10%
Value180 ms
92/100
30%
Value0.428
22/100
15%
Value23.0 s
1/100
10%
763 ms
359 ms
531 ms
362 ms
358 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 54% of them (44 requests) were addressed to the original Foh.jp, 38% (31 requests) were made to Finn-asp.jp and 4% (3 requests) were made to Countdown.reportitle.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Finn-asp.jp.
Page size can be reduced by 476.1 kB (44%)
1.1 MB
612.0 kB
In fact, the total size of Foh.jp main page is 1.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. 25% of websites need less resources to load. Javascripts take 607.4 kB which makes up the majority of the site volume.
Potential reduce by 7.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 1.2 kB, which is 11% 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 7.3 kB or 71% of the original size.
Potential reduce by 22.3 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. Foh images are well optimized though.
Potential reduce by 430.7 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 430.7 kB or 71% of the original size.
Potential reduce by 15.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. Foh.jp needs all CSS files to be minified and compressed as it can save up to 15.8 kB or 74% of the original size.
Number of requests can be reduced by 51 (70%)
73
22
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foh. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
foh.jp
763 ms
reset.css
359 ms
basic.css
531 ms
top.css
362 ms
roll.js
358 ms
scrollsmoothly.js
367 ms
jquery-1.3.2.min.js
1080 ms
jquery-ui-1.7.1.custom.min.js
1747 ms
jquery.easing.1.3.js
701 ms
jquery.scrollfollow.js
717 ms
show_name.js
552 ms
jquery.js
702 ms
colorbox.css
739 ms
jquery.colorbox.js
1221 ms
neo1.js
680 ms
neo2.js
529 ms
ga.js
32 ms
bnr.html
179 ms
base_white.gif
179 ms
bg_content.png
513 ms
bg_navi.png
358 ms
logo.gif
531 ms
img.jpg
554 ms
navi01_off.gif
378 ms
navi02_off.gif
406 ms
navi03_off.gif
527 ms
navi04_off.gif
561 ms
navi05_off.gif
601 ms
navi06_off.gif
698 ms
navi07_off.gif
700 ms
navi08_off.gif
701 ms
main3_1.jpg
1913 ms
ttl02.gif
748 ms
sttl02.gif
795 ms
pagetop.gif
886 ms
copyright.gif
875 ms
neo_parts.php
366 ms
login_foh.html
1161 ms
user.cgi
1234 ms
__utm.gif
13 ms
dotted.gif
812 ms
bg_bar.gif
870 ms
bg_black.gif
923 ms
bnr.css
885 ms
103549_pc_popup.jpg
2211 ms
bnr_mailmaga.jpg
387 ms
anniversary.jpg
743 ms
bnr_140710.jpg
563 ms
bnr_hiro.jpg
698 ms
bnr_yutaka.jpg
760 ms
bnr_arata.jpg
1004 ms
bnr04.jpg
738 ms
reset.css
551 ms
basic.css
753 ms
inner.css
570 ms
top.css
566 ms
reset.css
656 ms
basic.css
1075 ms
inner.css
1142 ms
top.css
1151 ms
roll.js
1199 ms
scrollsmoothly.js
1281 ms
jquery-1.3.2.min.js
2268 ms
jquery-ui-1.7.1.custom.min.js
2821 ms
jquery.easing.1.3.js
1897 ms
jquery.scrollfollow.js
1880 ms
show_name.js
1765 ms
base_white.gif
1104 ms
dia.gif
1552 ms
ga.js
33 ms
base_white.gif
541 ms
bg_black.gif
536 ms
ttl_log.gif
554 ms
icon01.gif
579 ms
icon02.gif
584 ms
line_log.gif
591 ms
btn01_off.gif
1061 ms
btn02_off.gif
1105 ms
btn03_off.gif
1086 ms
btn04_off.gif
1131 ms
btn05_off.gif
1119 ms
__utm.gif
14 ms
foh.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.
[aria-*] attributes do not have valid values
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
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.
foh.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
Missing source maps for large first-party JavaScript
foh.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 doesn't use 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 Foh.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 Foh.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.
foh.jp
Open Graph description is not detected on the main page of Foh. 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: