6.7 sec in total
1.9 sec
4.6 sec
197 ms
Visit fbuo.com now to see the best up-to-date Fbuo content and also check out these interesting facts you probably never knew about fbuo.com
Fbuo.com is a Human edited and search engine friendly web directory, each listing being reviewed to ensure only the highest quality listings.
Visit fbuo.comWe analyzed Fbuo.com page load time and found that the first response time was 1.9 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
fbuo.com performance score
name
value
score
weighting
Value3.0 s
48/100
10%
Value14.8 s
0/100
25%
Value8.8 s
16/100
10%
Value3,250 ms
2/100
30%
Value0.236
53/100
15%
Value19.5 s
2/100
10%
1911 ms
653 ms
598 ms
589 ms
599 ms
Our browser made a total of 77 requests to load all elements on the main page. We found that 78% of them (60 requests) were addressed to the original Fbuo.com, 6% (5 requests) were made to Pagead2.googlesyndication.com and 5% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Fbuo.com.
Page size can be reduced by 158.6 kB (64%)
248.1 kB
89.5 kB
In fact, the total size of Fbuo.com main page is 248.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. 30% of websites need less resources to load. Javascripts take 157.2 kB which makes up the majority of the site volume.
Potential reduce by 27.4 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 27.4 kB or 81% of the original size.
Potential reduce by 9.0 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. Obviously, Fbuo needs image optimization as it can save up to 9.0 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 102.5 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 102.5 kB or 65% of the original size.
Potential reduce by 19.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. Fbuo.com needs all CSS files to be minified and compressed as it can save up to 19.8 kB or 79% of the original size.
Number of requests can be reduced by 56 (74%)
76
20
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fbuo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
fbuo.com
1911 ms
style.css
653 ms
rating.css
598 ms
thumbs.css
589 ms
resize.css
599 ms
minmax.css
658 ms
datepicker.css
662 ms
jquery.js
1232 ms
cookie.js
770 ms
rating.js
764 ms
sessvars.js
940 ms
esyndicat.js
948 ms
sotd.css
954 ms
category-tree-style.css
983 ms
resize.js
981 ms
show_ads.js
14 ms
banners.js
1185 ms
thumbs.js
1279 ms
utils.js
1291 ms
minmax.js
1293 ms
esyndicat.search.js
1292 ms
esyndicat.common.js
1380 ms
15532_Reseller199_120x600_blue.gif
171 ms
body-bottom.gif
174 ms
body-top.gif
591 ms
inventory-right.gif
570 ms
inventory-left.gif
590 ms
inventory-bg.gif
587 ms
page_setup.gif
588 ms
logo.png
584 ms
sp.gif
587 ms
ajax-loader.gif
765 ms
spinner.gif
738 ms
34283_reseller_hosting_468x60_bluebg.gif
581 ms
vert-line.gif
692 ms
text-bg.gif
685 ms
flat-button.gif
681 ms
td-left-top.gif
651 ms
tab-left-active.gif
793 ms
tab-right-active.gif
847 ms
tab-left.gif
844 ms
green-caption-right.gif
835 ms
green-caption-left.gif
846 ms
green-caption-bg.gif
853 ms
box-border-right.gif
955 ms
box-border-left.gif
990 ms
box-footer-right.gif
991 ms
box-footer-left.gif
990 ms
box-footer-bg.gif
988 ms
shadow-left.gif
1019 ms
td-center-top.gif
1097 ms
login-button.gif
1157 ms
ico-dir.gif
1152 ms
ca-pub-4159360852621630.js
427 ms
zrt_lookup.html
439 ms
show_ads_impl.js
439 ms
pr10.gif
1044 ms
td-right-top.gif
1055 ms
shadow-right.gif
1099 ms
td-left-bottom.gif
1150 ms
td-right-bottom.gif
1178 ms
footer-right.gif
1195 ms
footer-left.gif
1201 ms
footer-bg.gif
1191 ms
ga.js
92 ms
thumb-bg.gif
866 ms
minmax.gif
873 ms
ads
386 ms
osd.js
23 ms
__utm.gif
15 ms
12362428665734745445
63 ms
abg.js
74 ms
m_js_controller.js
89 ms
googlelogo_color_112x36dp.png
120 ms
s
31 ms
x_button_blue2.png
34 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
6 ms
fbuo.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.
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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
fbuo.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
fbuo.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fbuo.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Fbuo.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.
fbuo.com
Open Graph description is not detected on the main page of Fbuo. 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: