Tools & Wizards About Us
flumpool.jp screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

flumpool.jp

flumpool（フランプール） オフィシャル ウェブサイト

Page Load Speed

5.9 sec in total

First Response

517 ms

Resources Loaded

5.3 sec

Page Rendered

120 ms

flumpool.jp screenshot

About Website

Click here to check amazing Flumpool content for Japan. Otherwise, check out these important facts you probably never knew about flumpool.jp

flumpoolオフィシャルサイト。最新情報など

Visit flumpool.jp

Key Findings

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

Performance Metrics

flumpool.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value8.6 s

17/100

10%

TBT (Total Blocking Time)

Value1,000 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.445

21/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

flumpool.jp

517 ms

www.flumpool.jp

3765 ms

gtm.js

158 ms

gtm.js

174 ms

css

54 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 13% of them (4 requests) were addressed to the original Flumpool.jp, 33% (10 requests) were made to Cdnjs.cloudflare.com and 13% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Flumpool.jp.

Page Optimization Overview & Recommendations

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

Content Size

180.1 kB

After Optimization

167.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 11.1 kB

  • Original 14.3 kB
  • After minification 12.2 kB
  • After compression 3.2 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 2.0 kB, which is 14% 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 11.1 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 117.4 kB
  • After minification 117.4 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. Flumpool images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 1.4 kB

  • Original 48.2 kB
  • After minification 48.1 kB
  • After compression 46.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. This website has mostly compressed JavaScripts.

CSS Optimization

-38%

Potential reduce by 88 B

  • Original 232 B
  • After minification 230 B
  • After compression 144 B

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. Flumpool.jp needs all CSS files to be minified and compressed as it can save up to 88 B or 38% of the original size.

Requests Breakdown

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

Requests Now

24

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flumpool. 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.

Network Requests Diagram

flumpool.jp

flumpool.jp

517 ms

www.flumpool.jp

www.flumpool.jp

3765 ms

gtm.js

gtm.js

158 ms

gtm.js

gtm.js

174 ms

css

css

54 ms

all.min.css

all.min.css

46 ms

tailwind.min.css

tailwind.min.css

68 ms

uikit.min.css

uikit.min.css

160 ms

animate.min.css

animate.min.css

157 ms

5.css

5.css

223 ms

jquery.slim.min.js

jquery.slim.min.js

155 ms

uikit.min.js

uikit.min.js

170 ms

anime.min.js

anime.min.js

169 ms

conversion.js

conversion.js

169 ms

s_retargeting.js

s_retargeting.js

935 ms

logo.png

logo.png

522 ms

analytics.js

analytics.js

83 ms

js

js

102 ms

fa-solid-900.ttf

fa-solid-900.ttf

36 ms

fa-regular-400.ttf

fa-regular-400.ttf

36 ms

HTx3L3I-JCGChYJ8VI-L6OO_au7B6xHT3w.ttf

HTx3L3I-JCGChYJ8VI-L6OO_au7B6xHT3w.ttf

226 ms

fa-brands-400.ttf

fa-brands-400.ttf

45 ms

274 ms

collect

collect

196 ms

destination

destination

202 ms

102 ms

24 ms

uwt.js

uwt.js

27 ms

40 ms

15 ms

Accessibility Review

flumpool.jp accessibility score

94

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

flumpool.jp best practices score

83

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

SEO Factors

flumpool.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 Flumpool.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 Flumpool.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

flumpool.jp

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