Tools & Wizards About Us
famberry.com screenshot

Report Summary

  • 26

    Performance

    Renders faster than
    45% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 0

    Best Practices

  • 85

    SEO

    Google-friendlier than
    55% of websites

famberry.com

Free Family Tree Maker - Family Photo Album

Page Load Speed

2.3 sec in total

First Response

263 ms

Resources Loaded

1.6 sec

Page Rendered

453 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

Discover the beautiful free Family Tree Maker that allows you and your family to share family history, photos, timelines and more.

Visit famberry.com

Key Findings

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

Performance Metrics

famberry.com performance score

26

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value450 ms

62/100

30%

CLS (Cumulative Layout Shift)

Value1.427

0/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

famberry.com

263 ms

js

82 ms

bootstrap.min.css

378 ms

icons.css

152 ms

css

46 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 76% of them (31 requests) were addressed to the original Famberry.com, 10% (4 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Famberry.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 601.6 kB (34%)

Content Size

1.8 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-70%

Potential reduce by 43.9 kB

  • Original 63.0 kB
  • After minification 57.9 kB
  • After compression 19.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 43.9 kB or 70% of the original size.

Image Optimization

-24%

Potential reduce by 321.8 kB

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

JavaScript Optimization

-58%

Potential reduce by 124.4 kB

  • Original 214.4 kB
  • After minification 206.0 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 124.4 kB or 58% of the original size.

CSS Optimization

-83%

Potential reduce by 111.6 kB

  • Original 133.8 kB
  • After minification 125.3 kB
  • After compression 22.2 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.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (46%)

Requests Now

35

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 35 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 11 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

263 ms

js

js

82 ms

bootstrap.min.css

bootstrap.min.css

378 ms

icons.css

icons.css

152 ms

css

css

46 ms

flexslider.css

flexslider.css

150 ms

set1.css

set1.css

153 ms

index_style.css

index_style.css

225 ms

stylesheet.css

stylesheet.css

153 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

520 ms

bootstrap.min.js

bootstrap.min.js

297 ms

jquery.flexslider.js

jquery.flexslider.js

298 ms

jquery.fadethis.js

jquery.fadethis.js

226 ms

jquery.easing.js

jquery.easing.js

299 ms

jquery.mousewheel.js

jquery.mousewheel.js

301 ms

classie.js

classie.js

371 ms

scroll.js

scroll.js

372 ms

white-logo.png

white-logo.png

373 ms

fb-logo-white.png

fb-logo-white.png

466 ms

Twitter-X-White-Logo.png

Twitter-X-White-Logo.png

1270 ms

FamilyTree.png

FamilyTree.png

467 ms

family_tree_new.jpg

family_tree_new.jpg

1312 ms

WDYTYALIVE.png

WDYTYALIVE.png

599 ms

FTMLogo.png

FTMLogo.png

554 ms

bbc_logo.png

bbc_logo.png

553 ms

popup-logo.png

popup-logo.png

592 ms

banner-image1.jpg

banner-image1.jpg

514 ms

banner-image7.jpg

banner-image7.jpg

749 ms

banner-image3.jpg

banner-image3.jpg

507 ms

banner-image4.jpg

banner-image4.jpg

518 ms

banner-image5.jpg

banner-image5.jpg

654 ms

nav-icons.png

nav-icons.png

589 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

23 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

33 ms

S6u8w4BMUTPHh30AXC-s.woff

S6u8w4BMUTPHh30AXC-s.woff

39 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

40 ms

linecons.woff

linecons.woff

507 ms

analytics.js

analytics.js

20 ms

dc.js

dc.js

20 ms

collect

collect

39 ms

__utm.gif

__utm.gif

13 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: