Tools & Wizards About Us
jfpea.jp screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% 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

  • 89

    SEO

    Google-friendlier than
    66% of websites

jfpea.jp

全国花き輸出拡大協議会｜輸出花・盆栽・植木

Page Load Speed

4.8 sec in total

First Response

521 ms

Resources Loaded

4.1 sec

Page Rendered

185 ms

jfpea.jp screenshot

About Website

Click here to check amazing Jfpea content. Otherwise, check out these important facts you probably never knew about jfpea.jp

全国花き輸出拡大協議会は、花きの輸出振興を目的として平成19年度に発足し、日本産花きの輸出マニュアルの作成等様々な取り組みを実施してまいりました。日本産花きのジャパン・ブランドの確立を目的とした取組みを積極的に実施してまいります。

Visit jfpea.jp

Key Findings

We analyzed Jfpea.jp page load time and found that the first response time was 521 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

jfpea.jp performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

jfpea.jp

521 ms

www.jfpea.jp

551 ms

www.jfpea.jp

859 ms

bootstrap.min.css

388 ms

bootstrap4-print.css

540 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 81% of them (39 requests) were addressed to the original Jfpea.jp, 6% (3 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Jfpea.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 336.1 kB (24%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jfpea.jp main page is 1.4 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. 70% of websites need less resources to load. Images take 906.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 23.9 kB

  • Original 30.7 kB
  • After minification 26.0 kB
  • After compression 6.7 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 4.7 kB, which is 15% 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 23.9 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 30.5 kB

  • Original 906.7 kB
  • After minification 876.2 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. Jfpea images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 149.4 kB

  • Original 271.0 kB
  • After minification 254.5 kB
  • After compression 121.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 149.4 kB or 55% of the original size.

CSS Optimization

-67%

Potential reduce by 132.2 kB

  • Original 197.7 kB
  • After minification 177.1 kB
  • After compression 65.5 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. Jfpea.jp needs all CSS files to be minified and compressed as it can save up to 132.2 kB or 67% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (69%)

Requests Now

39

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jfpea.jp

jfpea.jp

521 ms

www.jfpea.jp

www.jfpea.jp

551 ms

www.jfpea.jp

www.jfpea.jp

859 ms

bootstrap.min.css

bootstrap.min.css

388 ms

bootstrap4-print.css

bootstrap4-print.css

540 ms

all.css

all.css

536 ms

simplebar.css

simplebar.css

567 ms

lightcase.css

lightcase.css

569 ms

style_col4.css

style_col4.css

950 ms

style.css

style.css

582 ms

hamburgers.css

hamburgers.css

714 ms

slick.css

slick.css

716 ms

slick-theme.css

slick-theme.css

755 ms

viewport-extra.min.js

viewport-extra.min.js

758 ms

js

js

61 ms

system.css

system.css

773 ms

sdk.js

sdk.js

17 ms

jquery.min.js

jquery.min.js

1124 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

897 ms

tel.js

tel.js

945 ms

ofi.min.js

ofi.min.js

946 ms

jquery.matchHeight.min.js

jquery.matchHeight.min.js

994 ms

slick.min.js

slick.min.js

1139 ms

simplebar.min.js

simplebar.min.js

1334 ms

lightcase.js

lightcase.js

1146 ms

config.js

config.js

1147 ms

base.js

base.js

1369 ms

jquery.tagcolle-1.0.js

jquery.tagcolle-1.0.js

1249 ms

slick.min.js

slick.min.js

1254 ms

css2

css2

24 ms

css2

css2

37 ms

logo.png

logo.png

569 ms

header_btn.png

header_btn.png

386 ms

btn_more01.png

btn_more01.png

471 ms

footer_logo.png

footer_logo.png

478 ms

pagetop.png

pagetop.png

566 ms

main01.jpg

main01.jpg

1115 ms

main02.jpg

main02.jpg

1118 ms

main03.jpg

main03.jpg

1147 ms

sdk.js

sdk.js

62 ms

xn77YHs72GKoTvER4Gn3b5eMZCqNRkg.otf

xn77YHs72GKoTvER4Gn3b5eMZCqNRkg.otf

627 ms

xn7mYHs72GKoTvER4Gn3b5eMXNg.otf

xn7mYHs72GKoTvER4Gn3b5eMXNg.otf

964 ms

xn77YHs72GKoTvER4Gn3b5eMZGKLRkg.otf

xn77YHs72GKoTvER4Gn3b5eMZGKLRkg.otf

746 ms

fa-brands-400.woff

fa-brands-400.woff

691 ms

fa-solid-900.woff

fa-solid-900.woff

990 ms

fa-regular-400.woff

fa-regular-400.woff

616 ms

53 ms

ajax-loader.gif

ajax-loader.gif

541 ms

Accessibility Review

jfpea.jp accessibility score

87

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.

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

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

High

Page has valid source maps

SEO Factors

jfpea.jp SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jfpea.jp 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 Jfpea.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

jfpea.jp

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