Tools & Wizards About Us
pbcf.jp screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

pbcf.jp

船舶の省エネ装置｜PBCF｜商船三井テクノトレード株式会社

Page Load Speed

10.2 sec in total

First Response

521 ms

Resources Loaded

9.1 sec

Page Rendered

535 ms

pbcf.jp screenshot

About Website

Welcome to pbcf.jp homepage info - get ready to check PBCF best content right away, or after learning these important things about pbcf.jp

PBCF（Propeller Boss Cap Fins）は、5%の省エネ効果・メンテナンスが容易で永久に効果を発揮する船舶の省エネ装置。省燃費とCO2削減を可能にする地球環境に優しい技術です。

Visit pbcf.jp

Key Findings

We analyzed Pbcf.jp page load time and found that the first response time was 521 ms and then it took 9.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

pbcf.jp performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value16.5 s

0/100

10%

TBT (Total Blocking Time)

Value1,680 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.39

26/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

pbcf.jp

521 ms

pbcf.jp

1286 ms

analytics.js

35 ms

common.css

182 ms

en.css

360 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 81% of them (55 requests) were addressed to the original Pbcf.jp, 4% (3 requests) were made to Fonts.googleapis.com and 4% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain Pbcf.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 460.7 kB (7%)

Content Size

7.0 MB

After Optimization

6.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pbcf.jp main page is 7.0 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. 40% of websites need less resources to load. Images take 6.8 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 25.5 kB

  • Original 31.0 kB
  • After minification 24.0 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 7.0 kB, which is 23% 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 25.5 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 389.6 kB

  • Original 6.8 MB
  • After minification 6.5 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. PBCF images are well optimized though.

JavaScript Optimization

-50%

Potential reduce by 42.6 kB

  • Original 84.5 kB
  • After minification 84.5 kB
  • After compression 41.8 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 42.6 kB or 50% of the original size.

CSS Optimization

-15%

Potential reduce by 3.0 kB

  • Original 20.0 kB
  • After minification 20.0 kB
  • After compression 17.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. Pbcf.jp needs all CSS files to be minified and compressed as it can save up to 3.0 kB or 15% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (28%)

Requests Now

61

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pbcf.jp

pbcf.jp

521 ms

pbcf.jp

pbcf.jp

1286 ms

analytics.js

analytics.js

35 ms

common.css

common.css

182 ms

en.css

en.css

360 ms

css

css

52 ms

css

css

62 ms

css

css

71 ms

drawer.min.css

drawer.min.css

515 ms

fakeLoader.min.css

fakeLoader.min.css

639 ms

qswow.css

qswow.css

517 ms

jquery-1.12.4.js

jquery-1.12.4.js

49 ms

font-awesome.min.css

font-awesome.min.css

50 ms

uniq.css

uniq.css

523 ms

anime.min.js

anime.min.js

50 ms

common-dist.js

common-dist.js

807 ms

jquery.bxslider.css

jquery.bxslider.css

537 ms

jquery.bxslider.js

jquery.bxslider.js

705 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

706 ms

jquery-numerator.js

jquery-numerator.js

706 ms

collect

collect

16 ms

js

js

74 ms

header_logo.svg

header_logo.svg

203 ms

icon_arrow.svg

icon_arrow.svg

201 ms

img_strength_01.jpg

img_strength_01.jpg

1212 ms

img_strength_02.jpg

img_strength_02.jpg

1902 ms

img_strength_03.jpg

img_strength_03.jpg

1080 ms

img_strength_04.jpg

img_strength_04.jpg

1227 ms

img_reseach_01.jpg

img_reseach_01.jpg

1890 ms

img_reseach_02.jpg

img_reseach_02.jpg

1082 ms

img_reseach_03.jpg

img_reseach_03.jpg

2124 ms

img_reseach_04.jpg

img_reseach_04.jpg

1607 ms

header_logo.svg

header_logo.svg

1383 ms

mail_icon.svg

mail_icon.svg

1404 ms

country_icon.svg

country_icon.svg

1557 ms

mv01@2x.jpg

mv01@2x.jpg

2796 ms

mv02@2x.jpg

mv02@2x.jpg

2068 ms

mv03@2x.jpg

mv03@2x.jpg

6638 ms

img03@2x.jpg

img03@2x.jpg

2566 ms

img01@2x.jpg

img01@2x.jpg

2247 ms

img04@2x.jpg

img04@2x.jpg

2244 ms

img02@2x.jpg

img02@2x.jpg

2822 ms

icon01.png

icon01.png

2449 ms

icon02.png

icon02.png

2421 ms

icon03.png

icon03.png

2596 ms

icon04.png

icon04.png

2621 ms

16589138045622c1d9ed0cdcd3-M.png

16589138045622c1d9ed0cdcd3-M.png

3248 ms

1606200880b919b0907fafa40c-M.jpg

1606200880b919b0907fafa40c-M.jpg

2772 ms

1596161320d2de5cf12a733cff-M.png

1596161320d2de5cf12a733cff-M.png

3642 ms

1595922295966284cb24481b4c-M.jpg

1595922295966284cb24481b4c-M.jpg

2951 ms

15922031936925a70b9735db59-M.jpg

15922031936925a70b9735db59-M.jpg

2974 ms

1587607047b2bdcd81ed305358-M.png

1587607047b2bdcd81ed305358-M.png

4244 ms

15840594406a12f5765daf2b6e-M.jpg

15840594406a12f5765daf2b6e-M.jpg

3129 ms

15794295243ac5e15fbf44d632-M.jpg

15794295243ac5e15fbf44d632-M.jpg

3110 ms

1580254300f55b4ec4ba4b22fe-M.png

1580254300f55b4ec4ba4b22fe-M.png

3939 ms

1579430737200588237cdf0c96-M.png

1579430737200588237cdf0c96-M.png

4500 ms

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf

19 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1g.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj35zS1g.ttf

31 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

31 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

14 ms

1580194946ad34b4ee2178a32b-M.gif

1580194946ad34b4ee2178a32b-M.gif

3380 ms

btn_arrow.svg

btn_arrow.svg

3403 ms

btn_arrow_small.svg

btn_arrow_small.svg

3572 ms

footer_logo.png

footer_logo.png

3619 ms

icon_mail.svg

icon_mail.svg

2869 ms

pbcf_logo.svg

pbcf_logo.svg

2915 ms

header_logo_white.svg

header_logo_white.svg

2910 ms

bx_loader.gif

bx_loader.gif

2937 ms

Accessibility Review

pbcf.jp accessibility score

87

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

Links do not have a discernible name

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

pbcf.jp 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

SEO Factors

pbcf.jp SEO score

100

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pbcf.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Pbcf.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.

Social Sharing Optimization

pbcf.jp

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