5.3 sec in total
894 ms
4.2 sec
169 ms
Welcome to flobal.jp homepage info - get ready to check Flobal best content for Japan right away, or after learning these important things about flobal.jp
配管部品のフローバル株式会社(旧社名:岡田産業)オフィシャルサイト。自社ブランドの配管部品の開発・製造から海外メーカー品の卸、小売まで、継手・ホース・バルブ等、配管部品分野で総合的にサポートします。
Visit flobal.jpWe analyzed Flobal.jp page load time and found that the first response time was 894 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
flobal.jp performance score
name
value
score
weighting
Value11.8 s
0/100
10%
Value13.9 s
0/100
25%
Value15.4 s
0/100
10%
Value340 ms
74/100
30%
Value0.243
51/100
15%
Value16.4 s
5/100
10%
894 ms
332 ms
352 ms
355 ms
357 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 96% of them (65 requests) were addressed to the original Flobal.jp, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Track.list-finder.jp. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Flobal.jp.
Page size can be reduced by 52.3 kB (9%)
595.5 kB
543.2 kB
In fact, the total size of Flobal.jp main page is 595.5 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. 25% of websites need less resources to load. Images take 515.3 kB which makes up the majority of the site volume.
Potential reduce by 13.0 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 3.7 kB, which is 22% 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 13.0 kB or 78% of the original size.
Potential reduce by 61 B
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. Flobal images are well optimized though.
Potential reduce by 35.7 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 35.7 kB or 61% of the original size.
Potential reduce by 3.6 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. Flobal.jp needs all CSS files to be minified and compressed as it can save up to 3.6 kB or 77% of the original size.
Number of requests can be reduced by 11 (17%)
66
55
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flobal. 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.
flobal.jp
894 ms
default.css
332 ms
index.css
352 ms
default.js
355 ms
popup.js
357 ms
top_img.js
332 ms
top_bgline.jpg
192 ms
top_bg01.jpg
166 ms
top_logo.gif
192 ms
top_lnk07.gif
192 ms
top_lnk01.gif
236 ms
index_topbtn03.jpg
296 ms
index_topbtn02.jpg
331 ms
index_topbtn01.jpg
352 ms
nav01_o.jpg
357 ms
nav02.jpg
357 ms
nav03.jpg
454 ms
nav04.jpg
461 ms
nav05.jpg
496 ms
nav06.jpg
526 ms
nav07.jpg
534 ms
nav08.jpg
535 ms
index_ttl01.jpg
887 ms
index_01_img01.jpg
793 ms
index_01_img02.jpg
834 ms
index_01_img03.jpg
699 ms
index_ttl02.jpg
890 ms
index_02_img01.jpg
1064 ms
index_02_img02.jpg
1067 ms
index_02_img03.jpg
1125 ms
index_new.gif
999 ms
index_newline.gif
1108 ms
side_bnr08.jpg
1243 ms
index_bnr07.jpg
1340 ms
index_bnr05.jpg
1240 ms
index_bnr09.jpg
1242 ms
index_bnr04.jpg
1320 ms
index_logo.jpg
1289 ms
madoguti.jpg
1426 ms
foot_line01.jpg
1416 ms
index_topimg07.jpg
1825 ms
analytics.js
24 ms
track.js
872 ms
index_back.jpg
1313 ms
collect
13 ms
index_topbtn01o.jpg
172 ms
index_topbtn02o.jpg
179 ms
index_topbtn03o.jpg
169 ms
nav02_o.jpg
181 ms
nav03_o.jpg
181 ms
nav04_o.jpg
221 ms
nav05_o.jpg
333 ms
nav06_o.jpg
336 ms
nav07_o.jpg
354 ms
nav08_o.jpg
356 ms
top_lnk01_o.gif
358 ms
top_lnk02_o.gif
436 ms
sub01o.jpg
494 ms
index_ttl01o.jpg
662 ms
index_ttl02o.jpg
700 ms
index_01_img01o.jpg
530 ms
index_01_img02o.jpg
706 ms
index_01_img03o.jpg
653 ms
index_02_img01o.jpg
984 ms
index_02_img02o.jpg
709 ms
index_bnr01o.jpg
1304 ms
index_bnr02o.jpg
989 ms
index_bnr03o.jpg
892 ms
flobal.jp accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Links do not have a discernible name
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.
flobal.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
Browser errors were logged to the console
flobal.jp SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Flobal.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Flobal.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.
flobal.jp
Open Graph description is not detected on the main page of Flobal. 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: