Tools & Wizards About Us
foobee.io screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

foobee.io

Contact Support

Page Load Speed

4 sec in total

First Response

673 ms

Resources Loaded

2.1 sec

Page Rendered

1.3 sec

foobee.io screenshot

About Website

Welcome to foobee.io homepage info - get ready to check Foobee best content for Bangladesh right away, or after learning these important things about foobee.io

Foobee is bringing human connection to crypto with the world's first, “Swipe-to-Earn” social dating application. Foobee’s first-to-market platform is powered by e-commerce which utilizes Foobee Token'...

Visit foobee.io

Key Findings

We analyzed Foobee.io page load time and found that the first response time was 673 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

foobee.io performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value5.0 s

64/100

10%

TBT (Total Blocking Time)

Value2,590 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

foobee.io

673 ms

style.css

80 ms

color.css

84 ms

responsive.css

98 ms

font-awesome.min.css

77 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 79% of them (72 requests) were addressed to the original Foobee.io, 5% (5 requests) were made to Youtube.com and 3% (3 requests) were made to Tracking.bestseoplans.com. The less responsive or slowest element that took the longest time to load (747 ms) belongs to the original domain Foobee.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (15%)

Content Size

10.1 MB

After Optimization

8.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foobee.io main page is 10.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. Only a small number of websites need less resources to load. Images take 9.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 65.7 kB

  • Original 81.9 kB
  • After minification 81.8 kB
  • After compression 16.2 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 65.7 kB or 80% of the original size.

Image Optimization

-15%

Potential reduce by 1.4 MB

  • Original 9.6 MB
  • After minification 8.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. Obviously, Foobee needs image optimization as it can save up to 1.4 MB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-8%

Potential reduce by 22.0 kB

  • Original 279.5 kB
  • After minification 279.5 kB
  • After compression 257.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. This website has mostly compressed JavaScripts.

CSS Optimization

-13%

Potential reduce by 16.4 kB

  • Original 121.9 kB
  • After minification 121.9 kB
  • After compression 105.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. Foobee.io needs all CSS files to be minified and compressed as it can save up to 16.4 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (40%)

Requests Now

87

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 87 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foobee. 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 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

foobee.io

foobee.io

673 ms

style.css

style.css

80 ms

color.css

color.css

84 ms

responsive.css

responsive.css

98 ms

font-awesome.min.css

font-awesome.min.css

77 ms

bootstrap.min.css

bootstrap.min.css

113 ms

owl.carousel.css

owl.carousel.css

76 ms

jquery.listtopie.css

jquery.listtopie.css

144 ms

animations.css

animations.css

145 ms

js

js

61 ms

email-decode.min.js

email-decode.min.js

82 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

143 ms

bootstrap.min.js

bootstrap.min.js

160 ms

owl.carousel.min.js

owl.carousel.min.js

179 ms

snap.svg-min.js

snap.svg-min.js

194 ms

jquery.listtopie.min.js

jquery.listtopie.min.js

208 ms

animation.js

animation.js

317 ms

custom.js

custom.js

209 ms

iframeResizer.contentWindow.min.js

iframeResizer.contentWindow.min.js

149 ms

css2.css

css2.css

147 ms

fbevents.js

fbevents.js

108 ms

yirq3RagER8

yirq3RagER8

148 ms

logo3.png

logo3.png

175 ms

small_cir.png

small_cir.png

230 ms

facebook.png

facebook.png

143 ms

telegram.png

telegram.png

142 ms

twitter1.png

twitter1.png

144 ms

github-big-logo.png

github-big-logo.png

142 ms

instagram-logo.png

instagram-logo.png

228 ms

Techrate%20approved.png

Techrate%20approved.png

231 ms

falling-coins_original.gif

falling-coins_original.gif

499 ms

Mission.png

Mission.png

487 ms

cir.png

cir.png

390 ms

1%20(3).png

1%20(3).png

489 ms

3%20(3).png

3%20(3).png

489 ms

4%20(3).png

4%20(3).png

491 ms

4_%20Purchase%20Using%20FBE%20Tokens.png

4_%20Purchase%20Using%20FBE%20Tokens.png

488 ms

what_make.png

what_make.png

559 ms

black-circle.svg

black-circle.svg

498 ms

black-circle.svg

black-circle.svg

500 ms

tokensale.svg

tokensale.svg

501 ms

profilea.png

profilea.png

532 ms

cravinga.png

cravinga.png

535 ms

wallet%20(1).png

wallet%20(1).png

535 ms

1%20(1).png

1%20(1).png

538 ms

2%20(1).png

2%20(1).png

537 ms

3%20(1).png

3%20(1).png

675 ms

4%20(1).png

4%20(1).png

683 ms

5%20(1).png

5%20(1).png

676 ms

6%20(1).png

6%20(1).png

675 ms

left-arrow.png

left-arrow.png

674 ms

right-arrow.png

right-arrow.png

674 ms

reffera.png

reffera.png

735 ms

match.png

match.png

738 ms

token1.png

token1.png

737 ms

price-taga.png

price-taga.png

736 ms

trophyb.png

trophyb.png

646 ms

js

js

68 ms

analytics.js

analytics.js

46 ms

01%20.png

01%20.png

747 ms

collect

collect

42 ms

02.png

02.png

685 ms

03.png

03.png

716 ms

04.png

04.png

718 ms

www-player.css

www-player.css

38 ms

www-embed-player.js

www-embed-player.js

58 ms

base.js

base.js

85 ms

smartphonea.png

smartphonea.png

658 ms

white%20paper%20transparent_.png

white%20paper%20transparent_.png

711 ms

wassim_a.png

wassim_a.png

730 ms

linkedin.png

linkedin.png

662 ms

ad_status.js

ad_status.js

156 ms

John%20Ki.jpg.png

John%20Ki.jpg.png

522 ms

embed.js

embed.js

58 ms

Sasha%20Perea.png

Sasha%20Perea.png

461 ms

Shaun%20Bernard.jpg.png

Shaun%20Bernard.jpg.png

455 ms

mrinal_sharma.jpg

mrinal_sharma.jpg

507 ms

Nikhil%20(1).png

Nikhil%20(1).png

553 ms

Ashwin%20(1).jpg

Ashwin%20(1).jpg

468 ms

pratik%20(1).jpg

pratik%20(1).jpg

567 ms

kamlesh.jpg

kamlesh.jpg

602 ms

Image%20(1).jpg

Image%20(1).jpg

553 ms

muhammad_irfan.jpg

muhammad_irfan.jpg

597 ms

emai.png

emai.png

535 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

33 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

38 ms

id

id

23 ms

tracking.bestseoplans.com

tracking.bestseoplans.com

119 ms

parallax-script.js

parallax-script.js

138 ms

Create

Create

24 ms

GenerateIT

GenerateIT

14 ms

Accessibility Review

foobee.io accessibility score

73

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

foobee.io best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

foobee.io SEO score

81

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

foobee.io

Open Graph data is detected on the main page of Foobee. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: