17.8 sec in total
1.1 sec
15.6 sec
1.1 sec
Click here to check amazing Fctg Fp content. Otherwise, check out these important facts you probably never knew about fctg-fp.net
横浜・東京近郊出張対応可のFP事務所FCTGファイナンシャルプランナーズのHPです。ライフプランシミュレーション、保険、資産運用等のご相談
Visit fctg-fp.netWe analyzed Fctg-fp.net page load time and found that the first response time was 1.1 sec and then it took 16.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fctg-fp.net performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value18.7 s
0/100
25%
Value6.1 s
45/100
10%
Value940 ms
30/100
30%
Value0.573
12/100
15%
Value9.3 s
31/100
10%
1098 ms
897 ms
887 ms
1866 ms
1473 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 61% of them (45 requests) were addressed to the original Fctg-fp.net, 11% (8 requests) were made to Apis.google.com and 9% (7 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (13.2 sec) belongs to the original domain Fctg-fp.net.
Page size can be reduced by 90.0 kB (8%)
1.2 MB
1.1 MB
In fact, the total size of Fctg-fp.net main page is 1.2 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 22.2 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 22.2 kB or 71% of the original size.
Potential reduce by 5.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. Fctg Fp images are well optimized though.
Potential reduce by 28.9 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 28.9 kB or 63% of the original size.
Potential reduce by 33.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. Fctg-fp.net needs all CSS files to be minified and compressed as it can save up to 33.4 kB or 89% of the original size.
Number of requests can be reduced by 18 (25%)
72
54
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fctg Fp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
fctg-fp.net
1098 ms
main.css
897 ms
1_page.css
887 ms
logo-left.jpg
1866 ms
button.jpg
1473 ms
navi-01.jpg
1340 ms
navi-02.jpg
1377 ms
navi-03.jpg
1403 ms
navi-06.jpg
1434 ms
navi-04.jpg
1751 ms
navi-05.jpg
1543 ms
main.jpg
3573 ms
contents.jpg
1718 ms
image1370260509.jpg
1543 ms
image1370260320.jpg
1688 ms
image1370262982.jpg
1827 ms
image1370263082.jpg
1816 ms
image1370263140.jpg
1855 ms
image1370263235.jpg
2054 ms
image1394292215.jpg
2099 ms
image1372324382.jpg
2182 ms
image1370263399.jpg
2172 ms
image1372124814.jpg
2234 ms
1452425811.jpg
2468 ms
1405070395.jpg
2495 ms
1401277342.jpg
2746 ms
1375363810.jpg
2578 ms
1375364962.jpg
2685 ms
soudan.jpg
2831 ms
blog.jpg
2885 ms
widgets.js
103 ms
plusone.js
143 ms
back.jpg
2367 ms
main.css
2833 ms
blog.gif
2473 ms
image1370260630.jpg
3028 ms
1370261095.jpg
3377 ms
1370261101.jpg
3074 ms
1370261132.jpg
3291 ms
1370261140.jpg
3690 ms
all.js
293 ms
1370261154.jpg
3813 ms
cb=gapi.loaded_0
56 ms
cb=gapi.loaded_1
78 ms
fastbutton
182 ms
tag.js
270 ms
timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js
107 ms
button.71000885400e222c3c0eec823f8f93f0.js
106 ms
postmessageRelay
173 ms
syndication
232 ms
346801756778422272
301 ms
cb=gapi.loaded_0
90 ms
cb=gapi.loaded_1
84 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
178 ms
tweet_button.fd774b599f565016d763dd860cb31c79.ja.html
62 ms
1077434459-postmessagerelay.js
133 ms
rpc:shindig_random.js
55 ms
197 ms
xd_arbiter.php
188 ms
xd_arbiter.php
454 ms
1370261162.jpg
3308 ms
1421506684.jpg
13193 ms
cb=gapi.loaded_0
14 ms
mainnews.jpg
3487 ms
rss.gif
3226 ms
203c.png
174 ms
proxy.jpg
167 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
17 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
20 ms
allnews.jpg
3471 ms
YHlBkbuP_normal.jpeg
362 ms
euqA4xQc_normal.jpg
363 ms
jot.html
17 ms
print.css
381 ms
fctg-fp.net 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.
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.
fctg-fp.net 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
Browser errors were logged to the console
Page has valid source maps
fctg-fp.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fctg-fp.net 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 Fctg-fp.net 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.
fctg-fp.net
Open Graph description is not detected on the main page of Fctg Fp. 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: