Tools & Wizards About Us
fpo.bz screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    46% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

fpo.bz

株式会社FPO

Page Load Speed

7.3 sec in total

First Response

693 ms

Resources Loaded

6.3 sec

Page Rendered

313 ms

fpo.bz screenshot

About Website

Click here to check amazing Fpo content for Japan. Otherwise, check out these important facts you probably never knew about fpo.bz

FPOは、売買指南をするだけの投資助言業の枠を超えて個人投資家の育成に力を入れている投資顧問会社です。

Visit fpo.bz

Key Findings

We analyzed Fpo.bz page load time and found that the first response time was 693 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

fpo.bz performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

36/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

22/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value6,190 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value39.3 s

0/100

10%

Network Requests Diagram

fpo.bz

693 ms

index.css

318 ms

index.js

327 ms

prototype.js

814 ms

jsapi

18 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 81% of them (83 requests) were addressed to the original Fpo.bz, 5% (5 requests) were made to Google.com and 3% (3 requests) were made to Freeserv.dukascopy.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Fpo.bz.

Page Optimization Overview & Recommendations

Page size can be reduced by 132.3 kB (34%)

Content Size

388.6 kB

After Optimization

256.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fpo.bz main page is 388.6 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Images take 206.1 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 26.1 kB

  • Original 34.6 kB
  • After minification 33.1 kB
  • After compression 8.5 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 26.1 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 150 B

  • Original 206.1 kB
  • After minification 206.0 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. Fpo images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 83.3 kB

  • Original 120.7 kB
  • After minification 93.3 kB
  • After compression 37.5 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 83.3 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 22.7 kB

  • Original 27.2 kB
  • After minification 16.9 kB
  • After compression 4.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. Fpo.bz needs all CSS files to be minified and compressed as it can save up to 22.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (40%)

Requests Now

99

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fpo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

fpo.bz

fpo.bz

693 ms

index.css

index.css

318 ms

index.js

index.js

327 ms

prototype.js

prototype.js

814 ms

jsapi

jsapi

18 ms

news.js

news.js

345 ms

rollover.js

rollover.js

353 ms

EmbedComponent.ashx

EmbedComponent.ashx

268 ms

gs_flash_130-66_ja.js

gs_flash_130-66_ja.js

7 ms

embed.js

embed.js

155 ms

base.css

base.css

156 ms

command.css

command.css

319 ms

list.css

list.css

334 ms

layout.css

layout.css

523 ms

13 ms

default+en.css

default+en.css

7 ms

default+en.I.js

default+en.I.js

8 ms

bg_body.gif

bg_body.gif

168 ms

gs_noscript_130-66_ja.gif

gs_noscript_130-66_ja.gif

26 ms

h_logo.gif

h_logo.gif

166 ms

h01.gif

h01.gif

313 ms

h02.gif

h02.gif

330 ms

h03.gif

h03.gif

335 ms

h_check.gif

h_check.gif

336 ms

bg_leftM.gif

bg_leftM.gif

486 ms

bg_leftB.gif

bg_leftB.gif

487 ms

l_download.gif

l_download.gif

805 ms

l_about.gif

l_about.gif

631 ms

l01.gif

l01.gif

660 ms

l02.gif

l02.gif

680 ms

l03.gif

l03.gif

791 ms

l04.gif

l04.gif

821 ms

l05.gif

l05.gif

931 ms

l06.gif

l06.gif

986 ms

l_webpartner.gif

l_webpartner.gif

999 ms

l_bana01.jpg

l_bana01.jpg

1281 ms

l_bana06.gif

l_bana06.gif

1115 ms

l_bana09.gif

l_bana09.gif

1173 ms

l_bana10.gif

l_bana10.gif

1236 ms

l_bana_fujinoi_off.jpg

l_bana_fujinoi_off.jpg

1474 ms

l_bana07.gif

l_bana07.gif

1336 ms

l_bana08.gif

l_bana08.gif

1459 ms

g00.gif

g00.gif

1531 ms

g01.gif

g01.gif

1588 ms

g02.gif

g02.gif

1586 ms

g03.gif

g03.gif

1651 ms

g04.gif

g04.gif

1796 ms

g05.gif

g05.gif

1817 ms

bana01_2_off.gif

bana01_2_off.gif

2056 ms

bana02_2_off.gif

bana02_2_off.gif

1894 ms

free.gif

free.gif

1894 ms

free_illust.gif

free_illust.gif

1984 ms

tool.gif

tool.gif

2130 ms

free_btn.gif

free_btn.gif

2122 ms

siteSeal.do

siteSeal.do

633 ms

212 ms

tool_btn.gif

tool_btn.gif

2122 ms

title01.gif

title01.gif

2123 ms

hit

hit

257 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

12 ms

bana_tieup_off.jpg

bana_tieup_off.jpg

2362 ms

title_tieup.gif

title_tieup.gif

2073 ms

title02.gif

title02.gif

2342 ms

title03.gif

title03.gif

2342 ms

media01.gif

media01.gif

2193 ms

media02.gif

media02.gif

2190 ms

hit

hit

130 ms

title04.gif

title04.gif

2103 ms

index.php

index.php

101 ms

siteSealImage.do

siteSealImage.do

597 ms

fx14.gif

fx14.gif

2124 ms

fx16_2.gif

fx16_2.gif

2227 ms

fx04.gif

fx04.gif

2115 ms

fx03.gif

fx03.gif

2107 ms

fx10.gif

fx10.gif

2100 ms

fx17.gif

fx17.gif

2160 ms

fx20.gif

fx20.gif

2121 ms

fx08.gif

fx08.gif

2108 ms

fx13.gif

fx13.gif

1993 ms

fx11.gif

fx11.gif

2042 ms

fx18.gif

fx18.gif

2112 ms

fx19.gif

fx19.gif

2110 ms

pageTop.gif

pageTop.gif

2083 ms

f_logo.gif

f_logo.gif

1976 ms

f_name.gif

f_name.gif

1970 ms

f01.gif

f01.gif

2012 ms

f02.gif

f02.gif

1984 ms

f03.gif

f03.gif

2167 ms

copyright.gif

copyright.gif

2114 ms

f_mm.gif

f_mm.gif

1959 ms

f_inq.gif

f_inq.gif

1949 ms

f_text01.gif

f_text01.gif

2125 ms

f_text02.gif

f_text02.gif

2125 ms

bg_flash.jpg

bg_flash.jpg

2525 ms

bana_01RB_2.gif

bana_01RB_2.gif

2001 ms

bana_02RB_2.gif

bana_02RB_2.gif

1956 ms

01.gif

01.gif

1961 ms

01.gif

01.gif

1935 ms

index.php

index.php

97 ms

Gfeeds

Gfeeds

350 ms

get_flash_player.gif

get_flash_player.gif

7 ms

Accessibility Review

fpo.bz accessibility score

92

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

fpo.bz best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fpo.bz SEO score

91

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

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

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 Fpo.bz 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 Fpo.bz 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

fpo.bz

Open Graph description is not detected on the main page of Fpo. 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: