13.9 sec in total
633 ms
8.3 sec
5 sec
Welcome to fubic.com homepage info - get ready to check Fubic best content for Japan right away, or after learning these important things about fubic.com
株式会社nobitelのコーポレートサイトです。私たちは「人の未来を大きくする」というビジョンを掲げ、世界200店舗を誇るドクターストレッチや国内最大級のテニスポータルサイトtennis365.netなどを運営しています。
Visit fubic.comWe analyzed Fubic.com page load time and found that the first response time was 633 ms and then it took 13.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fubic.com performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value18.7 s
0/100
25%
Value12.3 s
3/100
10%
Value1,790 ms
10/100
30%
Value0
100/100
15%
Value14.7 s
8/100
10%
633 ms
655 ms
1217 ms
1151 ms
364 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Fubic.com, 54% (29 requests) were made to Corporate.nobitel.jp and 13% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Corporate.nobitel.jp.
Page size can be reduced by 3.2 MB (40%)
8.0 MB
4.8 MB
In fact, the total size of Fubic.com main page is 8.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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.9 MB which makes up the majority of the site volume.
Potential reduce by 33.5 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 6.1 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 33.5 kB or 79% of the original size.
Potential reduce by 438.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. Fubic images are well optimized though.
Potential reduce by 42.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 42.0 kB or 38% of the original size.
Potential reduce by 2.7 MB
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. Fubic.com needs all CSS files to be minified and compressed as it can save up to 2.7 MB or 92% of the original size.
Number of requests can be reduced by 24 (55%)
44
20
The browser has sent 44 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fubic. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
fubic.com
633 ms
fubic.com
655 ms
corporate.nobitel.jp
1217 ms
nobitel-header.min.js
1151 ms
styles.css
364 ms
styles.css
518 ms
swiper.min.css
461 ms
editor.css
2122 ms
jquery.min.js
431 ms
scripts.js
933 ms
jquery.form.min.js
947 ms
scripts.js
798 ms
api.js
444 ms
script.js
797 ms
swiper.min.js
436 ms
jquery.fancybox.min.js
1088 ms
editor.js
945 ms
wp-embed.min.js
945 ms
lazysizes.min.js
454 ms
ls.unveilhooks.min.js
432 ms
vue.js
30 ms
gtm.js
407 ms
wp-emoji-release.min.js
333 ms
logonew.svg
249 ms
logo-top.png
335 ms
ic-right.png
293 ms
service.png
2388 ms
logo_fubicsi.png
336 ms
logo_fubicbeyond.png
336 ms
logo_singapore.png
337 ms
logo_taiwan.png
663 ms
logo_jcc.png
1187 ms
footer_logo.svg
635 ms
analytics.js
55 ms
js
312 ms
collect
909 ms
company-access-sp.png
885 ms
css2
850 ms
css2
834 ms
css
834 ms
bg-vision.png
552 ms
history.png
1121 ms
csr.png
1925 ms
recruit.png
1672 ms
-F62fjtqLzI2JPCgQBnw7HFoxQ.woff
522 ms
-F6pfjtqLzI2JPCgQBnw7HFQMisq0Q.woff
982 ms
-F6pfjtqLzI2JPCgQBnw7HFQei0q0Q.woff
1001 ms
-F6pfjtqLzI2JPCgQBnw7HFQQi8q0Q.woff
2058 ms
S6u9w4BMUTPHh50Xeww.woff
865 ms
S6u9w4BMUTPHh6UVeww.woff
863 ms
S6uyw4BMUTPHvxo.woff
849 ms
recaptcha__en.js
250 ms
main_visual_2.jpg
585 ms
main_visual.png
166 ms
fubic.com 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.
fubic.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
fubic.com 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
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fubic.com 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 Fubic.com 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.
fubic.com
Open Graph data is detected on the main page of Fubic. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: