Tools & Wizards About Us
fobus.biz screenshot

Report Summary

  • 97

    Performance

    Renders faster than
    95% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

fobus.biz

イベントを成功に導くプロモーションのポイントとは？

Page Load Speed

2.5 sec in total

First Response

140 ms

Resources Loaded

1.9 sec

Page Rendered

419 ms

fobus.biz screenshot

About Website

Welcome to fobus.biz homepage info - get ready to check Fobus best content right away, or after learning these important things about fobus.biz

大成功に収めるためには、プロモーションが大事です。 そこでいくつかのおすすめの方法を知り、採用しましょう。

Visit fobus.biz

Key Findings

We analyzed Fobus.biz page load time and found that the first response time was 140 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

fobus.biz performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.9 s

100/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.112

86/100

15%

TTI (Time to Interactive)

Value3.1 s

95/100

10%

Network Requests Diagram

fobus.biz

140 ms

www.fobus.com

1068 ms

pro-jquery.lazyloadxt.fadein.css

83 ms

template.css

124 ms

lightslider.css

87 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Fobus.biz, 79% (38 requests) were made to Fobus.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Fobus.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 646.6 kB (31%)

Content Size

2.1 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fobus.biz main page is 2.1 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. 50% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 24.5 kB

  • Original 32.1 kB
  • After minification 32.1 kB
  • After compression 7.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 24.5 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 3.8 kB

  • Original 1.2 MB
  • After minification 1.2 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. Fobus images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 343.9 kB

  • Original 497.6 kB
  • After minification 446.5 kB
  • After compression 153.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 343.9 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 274.4 kB

  • Original 329.2 kB
  • After minification 312.9 kB
  • After compression 54.8 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. Fobus.biz needs all CSS files to be minified and compressed as it can save up to 274.4 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

45

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fobus.biz

fobus.biz

140 ms

www.fobus.com

www.fobus.com

1068 ms

pro-jquery.lazyloadxt.fadein.css

pro-jquery.lazyloadxt.fadein.css

83 ms

template.css

template.css

124 ms

lightslider.css

lightslider.css

87 ms

maximenuck.php

maximenuck.php

173 ms

maximenuresponsiveck.css

maximenuresponsiveck.css

85 ms

j2store_cart.css

j2store_cart.css

96 ms

jquery.min.js

jquery.min.js

217 ms

jquery-noconflict.js

jquery-noconflict.js

137 ms

jquery-migrate.min.js

jquery-migrate.min.js

137 ms

caption.js

caption.js

140 ms

pro-jquery.lazyloadxt.js

pro-jquery.lazyloadxt.js

169 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

181 ms

maximenuck.js

maximenuck.js

182 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

183 ms

html5fallback.js

html5fallback.js

213 ms

css

css

69 ms

lightslider.js

lightslider.js

210 ms

responsive-nav.js

responsive-nav.js

271 ms

analytics.js

analytics.js

19 ms

logo.svg

logo.svg

74 ms

login.png

login.png

78 ms

social-top.png

social-top.png

77 ms

cart.png

cart.png

75 ms

lang.jpg

lang.jpg

75 ms

search.png

search.png

77 ms

products-menu-bg.png

products-menu-bg.png

108 ms

menu.png

menu.png

101 ms

product-title-bg.png

product-title-bg.png

102 ms

mid2-bgk.jpg

mid2-bgk.jpg

103 ms

newsletter.jpg

newsletter.jpg

105 ms

footer-social.png

footer-social.png

108 ms

rL4JY78pA4E

rL4JY78pA4E

77 ms

menu-sub-arrow.png

menu-sub-arrow.png

64 ms

collect

collect

25 ms

homepage_slider_01.jpg

homepage_slider_01.jpg

383 ms

homepage_slider_08.jpg

homepage_slider_08.jpg

376 ms

homepage_slider_09.jpg

homepage_slider_09.jpg

353 ms

1911CH_NEW.jpg

1911CH_NEW.jpg

55 ms

EXND2_Home.jpg

EXND2_Home.jpg

116 ms

HKCH2_NEW.jpg

HKCH2_NEW.jpg

170 ms

banner-mid2.png

banner-mid2.png

283 ms

collect

collect

71 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

42 ms

www-embed-player.js

www-embed-player.js

70 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

41 ms

ad_status.js

ad_status.js

89 ms

Accessibility Review

fobus.biz accessibility score

68

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

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

fobus.biz 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

fobus.biz SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

High

robots.txt is not valid

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

    JA

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fobus.biz can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Fobus.biz 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

fobus.biz

Open Graph description is not detected on the main page of Fobus. 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: