Tools & Wizards About Us
famberry.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 0

    Best Practices

  • 85

    SEO

    Google-friendlier than
    56% of websites

famberry.com

Famberry - Free Online Family Tree Maker

Page Load Speed

2.1 sec in total

First Response

392 ms

Resources Loaded

1.3 sec

Page Rendered

386 ms

famberry.com screenshot

About Website

Welcome to famberry.com homepage info - get ready to check Famberry best content for United States right away, or after learning these important things about famberry.com

Easily build and share your INTERACTIVE online family tree with your family, on the world's most beautiful FAMILY TREE MAKER.

Visit famberry.com

Key Findings

We analyzed Famberry.com page load time and found that the first response time was 392 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

famberry.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value1.403

0/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

famberry.com

392 ms

bootstrap.min.css

332 ms

icons.css

152 ms

css

63 ms

flexslider.css

167 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 74% of them (28 requests) were addressed to the original Famberry.com, 11% (4 requests) were made to Fonts.gstatic.com and 8% (3 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (613 ms) belongs to the original domain Famberry.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 314.5 kB (30%)

Content Size

1.0 MB

After Optimization

723.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Famberry.com main page is 1.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. 35% of websites need less resources to load. Images take 634.6 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 17.5 kB

  • Original 23.6 kB
  • After minification 20.8 kB
  • After compression 6.1 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 2.7 kB, which is 12% 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 17.5 kB or 74% of the original size.

Image Optimization

-5%

Potential reduce by 29.3 kB

  • Original 634.6 kB
  • After minification 605.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. Famberry images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 156.3 kB

  • Original 246.4 kB
  • After minification 237.9 kB
  • After compression 90.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 156.3 kB or 63% of the original size.

CSS Optimization

-83%

Potential reduce by 111.3 kB

  • Original 133.5 kB
  • After minification 125.1 kB
  • After compression 22.1 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. Famberry.com needs all CSS files to be minified and compressed as it can save up to 111.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (48%)

Requests Now

31

After Optimization

16

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

famberry.com

famberry.com

392 ms

bootstrap.min.css

bootstrap.min.css

332 ms

icons.css

icons.css

152 ms

css

css

63 ms

flexslider.css

flexslider.css

167 ms

set1.css

set1.css

168 ms

index_style.css

index_style.css

241 ms

stylesheet.css

stylesheet.css

170 ms

popup-logo.png

popup-logo.png

223 ms

white-logo.png

white-logo.png

241 ms

fb-logo-white.png

fb-logo-white.png

244 ms

twitter-logo-white.png

twitter-logo-white.png

253 ms

ajax-loader.gif

ajax-loader.gif

388 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

554 ms

bootstrap.min.js

bootstrap.min.js

396 ms

jquery.flexslider.js

jquery.flexslider.js

401 ms

jquery.fadethis.js

jquery.fadethis.js

384 ms

jquery.easing.js

jquery.easing.js

405 ms

jquery.mousewheel.js

jquery.mousewheel.js

439 ms

classie.js

classie.js

450 ms

scroll.js

scroll.js

475 ms

FamilyTree.png

FamilyTree.png

478 ms

banner-image1.jpg

banner-image1.jpg

312 ms

banner-image7.jpg

banner-image7.jpg

613 ms

banner-image3.jpg

banner-image3.jpg

477 ms

banner-image4.jpg

banner-image4.jpg

535 ms

banner-image5.jpg

banner-image5.jpg

381 ms

nav-icons.png

nav-icons.png

301 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

28 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

50 ms

zJY4gsxBiSo5L7tNutxFNg.ttf

zJY4gsxBiSo5L7tNutxFNg.ttf

63 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

63 ms

linecons.woff

linecons.woff

328 ms

analytics.js

analytics.js

31 ms

dc.js

dc.js

43 ms

collect

collect

18 ms

__utm.gif

__utm.gif

12 ms

collect

collect

50 ms

Accessibility Review

famberry.com accessibility score

71

Accessibility Issues

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 [lang] attribute

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

Image elements do not have [alt] attributes

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.

SEO Factors

famberry.com SEO score

85

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Famberry.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Famberry.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.

Social Sharing Optimization

famberry.com

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