Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

fctg-fp.net

横浜・東京の独立系FP - FCTGファイナンシャルプランナーズ

Page Load Speed

17.8 sec in total

First Response

1.1 sec

Resources Loaded

15.6 sec

Page Rendered

1.1 sec

fctg-fp.net screenshot

About Website

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.net

Key Findings

We 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.

Performance Metrics

fctg-fp.net performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value18.7 s

0/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value940 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.573

12/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

fctg-fp.net

1098 ms

main.css

897 ms

1_page.css

887 ms

logo-left.jpg

1866 ms

button.jpg

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 Optimization Overview & Recommendations

Page size can be reduced by 90.0 kB (8%)

Content Size

1.2 MB

After Optimization

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.

HTML Optimization

-71%

Potential reduce by 22.2 kB

  • Original 31.1 kB
  • After minification 30.1 kB
  • After compression 8.9 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.

Image Optimization

-1%

Potential reduce by 5.5 kB

  • Original 1.1 MB
  • After minification 1.1 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. Fctg Fp images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 28.9 kB

  • Original 45.8 kB
  • After minification 45.8 kB
  • After compression 16.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.

CSS Optimization

-89%

Potential reduce by 33.4 kB

  • Original 37.4 kB
  • After minification 24.4 kB
  • After compression 4.0 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.

Requests Breakdown

Number of requests can be reduced by 18 (25%)

Requests Now

72

After Optimization

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.

Accessibility Review

fctg-fp.net accessibility score

78

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

fctg-fp.net best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

fctg-fp.net SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    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.

Social Sharing Optimization

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: