6.8 sec in total
732 ms
5 sec
993 ms
Welcome to fear.co.jp homepage info - get ready to check F E A R best content for Japan right away, or after learning these important things about fear.co.jp
TRPGの制作、出版を行っている(有)ファーイースト・アミューズメント・リサーチ(F.E.A.R.)の公式サイトです。TRPGとは、テーブルトーク・ロールプレイング・ゲームの略称で、ゲームマスターと呼ばれる進行役と、複数人のプレイヤーがテーブルを囲み、会話によって進行するゲームのことです。このサイトでは、F.E.A.R.関連のイベント情報や、出版物のお知らせなどを公開しています。
Visit fear.co.jpWe analyzed Fear.co.jp page load time and found that the first response time was 732 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
fear.co.jp performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value27.9 s
0/100
25%
Value15.5 s
0/100
10%
Value11,000 ms
0/100
30%
Value0.159
73/100
15%
Value30.2 s
0/100
10%
732 ms
335 ms
336 ms
20 ms
688 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 84% of them (108 requests) were addressed to the original Fear.co.jp, 14% (18 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Fear.co.jp.
Page size can be reduced by 382.3 kB (8%)
4.8 MB
4.5 MB
In fact, the total size of Fear.co.jp main page is 4.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 99.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. This page needs HTML code to be minified as it can gain 14.6 kB, which is 13% 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 99.8 kB or 90% of the original size.
Potential reduce by 232.9 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. F E A R images are well optimized though.
Potential reduce by 45.6 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 45.6 kB or 54% of the original size.
Potential reduce by 4.1 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. Fear.co.jp needs all CSS files to be minified and compressed as it can save up to 4.1 kB or 76% of the original size.
Number of requests can be reduced by 18 (14%)
128
110
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of F E A R. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.
fear.co.jp
732 ms
flexslider.css
335 ms
fontsize.css
336 ms
jquery.min.js
20 ms
jquery.flexslider.js
688 ms
upd.htm
182 ms
2014_bg_b.jpg
335 ms
menutop.jpg
502 ms
w_top.jpg
174 ms
adimg004.jpg
1168 ms
adimg003.jpg
1065 ms
adimg006.jpg
1552 ms
adimg002.jpg
861 ms
adimg005.jpg
1170 ms
adimg001.jpg
1171 ms
fear_x_bana.jpg
1034 ms
fear2ch_bana.jpg
1207 ms
hiworks_bana_b.jpg
1245 ms
t_update.jpg
1335 ms
info_img.jpg
1337 ms
fear2_chbana.jpg
1339 ms
udon_img.jpg
1425 ms
gf284_sam.jpg
1426 ms
ara_sss05_sam.jpg
1502 ms
gf283_sam.jpg
1504 ms
dc3_sss04_sam.jpg
1512 ms
boas_rule_sam.jpg
1551 ms
tnx_sss14_sam.jpg
1604 ms
gf282_sam.jpg
1669 ms
rze_rule_sam.jpg
1671 ms
mgr_com_sam.jpg
1675 ms
gf281_sam.jpg
1712 ms
gf276_sam.jpg
1724 ms
dc3_sss03_sam.jpg
1784 ms
dc3_ia_sam.jpg
1835 ms
dc3_crcre_sam.jpg
1837 ms
tnx_crude_sam.jpg
1841 ms
gf275_sam.jpg
1884 ms
lrq_reeien_sam.jpg
1895 ms
gf274_sam.jpg
1964 ms
widgets.js
55 ms
dc3_sss02_sam.jpg
1944 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
184 ms
hkn_rule_sam.jpg
1837 ms
lrq_sss03_sam.jpg
1848 ms
settings
98 ms
gf273_sam.jpg
1726 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
29 ms
FEAR_TRPG
833 ms
dc3_sss01_sam.jpg
1570 ms
gf272_sam.jpg
1286 ms
mom_da_sam.jpg
1141 ms
gf271_sam.jpg
1112 ms
kar_rule_sam.jpg
1021 ms
lrq_prb_sam.jpg
1062 ms
gf266_sam.jpg
1073 ms
lrq_sss02_sam.jpg
1120 ms
anm_sss01_sam.jpg
1098 ms
polyfills-a40ef1678bae11e696dba45124eadd70.js
27 ms
runtime-b1c52fd0a13ead5fcf6b.js
58 ms
modules-96ebc7ac3ad66d681a3d.js
86 ms
main-babd9234dc048fb47339.js
105 ms
_app-a9c9f1a99e4414675fb1.js
125 ms
%5BscreenName%5D-0517bdda27d5006a5a2d.js
129 ms
_buildManifest.js
139 ms
_ssgManifest.js
138 ms
vc_rule_sam.jpg
1009 ms
gf265_sam.jpg
1032 ms
tnx_nan_sam.jpg
1065 ms
8526.0c32a8f0cfc5749221a3.js
27 ms
1755.07a49c40b12af4f75780.js
28 ms
gf264_sam.jpg
991 ms
tnm_sss08_sam.jpg
1080 ms
8283.f3e5048cca7cef5eed7f.js
32 ms
3077.44bfeb00af01bc4020f6.js
59 ms
1362.42d432e02f7980bca032.js
52 ms
4956.c4e51ef593974b9db0bb.js
80 ms
5893.d500bd2a89ded806aa73.js
35 ms
gf263_sam.jpg
1007 ms
gf262_sam.jpg
1006 ms
dc3_ccnc_sam.jpg
1016 ms
lrq_sss01_sam.jpg
1024 ms
lrq_rule_sam.jpg
1037 ms
boa_bana.jpg
1082 ms
mg_bana.jpg
1007 ms
vc_bana.jpg
1006 ms
cfsc_bana.jpg
1028 ms
rze_bana.jpg
1034 ms
dc3_bana.jpg
1037 ms
nw3_bana.jpg
1059 ms
sfm_banner.jpg
1009 ms
hkn_bana.jpg
1028 ms
ksb_bana.jpg
1028 ms
lrq_bana.jpg
1034 ms
rib_bana.jpg
1037 ms
anima_bana.jpg
1047 ms
ara2e_bana.jpg
1007 ms
al2_bana.jpg
1039 ms
ino02_bana.jpg
1020 ms
aog_bana.jpg
1033 ms
akg_bana.jpg
1036 ms
ag2_bana.jpg
1035 ms
oct_link.jpg
1006 ms
go_bana.jpg
1032 ms
stigma_bana.jpg
1040 ms
kar_bana.jpg
1034 ms
gmb_bana.jpg
1036 ms
kzm_bana.jpg
1022 ms
bana_cl.jpg
1007 ms
ph2_bana.jpg
1032 ms
poly_bana.jpg
1040 ms
shs_bana.jpg
1033 ms
star_bana.jpg
1037 ms
sqs_bana.jpg
1009 ms
tenka_bana.jpg
1007 ms
tenwar_bana.jpg
1039 ms
tnm_bana.jpg
1052 ms
novax_bana.jpg
1034 ms
dar_bana.jpg
1036 ms
tvs_bana.jpg
1006 ms
ths_bana.jpg
1006 ms
nir_bana.jpg
1024 ms
bbt_bana.jpg
1064 ms
fpr_bana.jpg
1033 ms
mar_bana.jpg
1037 ms
mgac_bana.jpg
1006 ms
mhe_bana.jpg
1006 ms
monorpg_bana.jpg
1011 ms
srs_bana.jpg
1077 ms
fear.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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
fear.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
fear.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
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fear.co.jp 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 Fear.co.jp 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.
fear.co.jp
Open Graph description is not detected on the main page of F E A R. 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: