8.6 sec in total
2 sec
6.3 sec
410 ms
Welcome to flow-fushi.jp homepage info - get ready to check FLOWFUSHI best content for Japan right away, or after learning these important things about flow-fushi.jp
UZUの会社概要、プライバシーポリシーなどををご覧いただけます。
Visit flow-fushi.jpWe analyzed Flow-fushi.jp page load time and found that the first response time was 2 sec and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
flow-fushi.jp performance score
name
value
score
weighting
Value6.3 s
3/100
10%
Value16.6 s
0/100
25%
Value12.3 s
3/100
10%
Value1,010 ms
27/100
30%
Value0
100/100
15%
Value16.3 s
5/100
10%
1957 ms
342 ms
1049 ms
365 ms
20 ms
Our browser made a total of 28 requests to load all elements on the main page. We found that 86% of them (24 requests) were addressed to the original Flow-fushi.jp, 7% (2 requests) were made to Google-analytics.com and 4% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Flow-fushi.jp.
Page size can be reduced by 119.3 kB (4%)
3.0 MB
2.9 MB
In fact, the total size of Flow-fushi.jp main page is 3.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. 20% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 5.6 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 5.6 kB or 70% of the original size.
Potential reduce by 54.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. FLOWFUSHI images are well optimized though.
Potential reduce by 40.9 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 40.9 kB or 42% of the original size.
Potential reduce by 18.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. Flow-fushi.jp needs all CSS files to be minified and compressed as it can save up to 18.5 kB or 81% of the original size.
Number of requests can be reduced by 4 (15%)
27
23
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FLOWFUSHI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
flow-fushi.jp
1957 ms
reset.css
342 ms
main.css
1049 ms
common.css
365 ms
jsapi
20 ms
bubble.js
558 ms
main.js
574 ms
jquery.min.js
30 ms
key01.png
755 ms
key02.png
1159 ms
key03.png
1029 ms
key04.png
756 ms
cm01.png
2175 ms
cm02.png
3519 ms
cm03.png
2428 ms
redbulll.jpg
948 ms
analytics.js
116 ms
h_logo2.svg
1134 ms
mail.svg
1186 ms
store.svg
1320 ms
copy.svg
1356 ms
title_news.svg
1362 ms
logo_sns.svg
1503 ms
youtube.svg
1536 ms
twitter.svg
1527 ms
facebook.svg
1686 ms
copy.svg
1688 ms
collect
13 ms
flow-fushi.jp accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
flow-fushi.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
flow-fushi.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flow-fushi.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 Flow-fushi.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.
flow-fushi.jp
Open Graph description is not detected on the main page of FLOWFUSHI. 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: