Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

florence.or.jp

認定NPO法人フローレンス | こども達のために、日本を変える。

Page Load Speed

7.8 sec in total

First Response

606 ms

Resources Loaded

6.7 sec

Page Rendered

504 ms

florence.or.jp screenshot

About Website

Visit florence.or.jp now to see the best up-to-date Florence content for Japan and also check out these interesting facts you probably never knew about florence.or.jp

フローレンスは事業開発、政策提言、文化創造の3つの軸で、日本の子ども・子育て領域の社会課題と価値創造に取り組む団体です。 「今を生きるわたしたちと まだ見ぬ子どもたちが 希望と手をつないで歩める社会。さあ、心躍る未来へ。」をビジョンに掲げ、各種保育事業、福祉支援活動を全国で展開しています。

Visit florence.or.jp

Key Findings

We analyzed Florence.or.jp page load time and found that the first response time was 606 ms and then it took 7.2 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

florence.or.jp performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value920 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value1.273

1/100

15%

TTI (Time to Interactive)

Value20.9 s

2/100

10%

Network Requests Diagram

florence.or.jp

606 ms

wp-emoji-release.min.js

445 ms

widget.css

298 ms

pagenavi-css.css

298 ms

wpp.css

299 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 68% of them (52 requests) were addressed to the original Florence.or.jp, 5% (4 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Florence.or.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 891.9 kB (23%)

Content Size

3.9 MB

After Optimization

3.0 MB

In fact, the total size of Florence.or.jp main page is 3.9 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 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 45.0 kB

  • Original 57.0 kB
  • After minification 54.4 kB
  • After compression 11.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 45.0 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 129.3 kB

  • Original 2.9 MB
  • After minification 2.8 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. Florence images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 391.9 kB

  • Original 609.9 kB
  • After minification 609.0 kB
  • After compression 218.0 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 391.9 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 325.7 kB

  • Original 391.4 kB
  • After minification 358.3 kB
  • After compression 65.7 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. Florence.or.jp needs all CSS files to be minified and compressed as it can save up to 325.7 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

69

After Optimization

42

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

Accessibility Review

florence.or.jp accessibility score

55

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Form elements do not have associated labels

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

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

florence.or.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

florence.or.jp SEO score

83

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

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

    UTF-8

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

Open Graph data is detected on the main page of Florence. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: