Tools & Wizards About Us
familytreeandme.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

familytreeandme.com

Photo Family Trees, customized Family Photo Art products

Page Load Speed

1.1 sec in total

First Response

35 ms

Resources Loaded

831 ms

Page Rendered

232 ms

familytreeandme.com screenshot

About Website

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

You provide the pictures and we create the art! Our customized family photo art, including Photo Family Trees, makes beautiful memorable keepsakes! Great for gifts, reunions, and your home's decor!!

Visit familytreeandme.com

Key Findings

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

Performance Metrics

familytreeandme.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value2,750 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

familytreeandme.com

35 ms

www.familytreeandme.com

255 ms

all.min.css

52 ms

v4-shims.min.css

50 ms

bootstrap.min.css

114 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 20% of them (12 requests) were addressed to the original Familytreeandme.com, 31% (19 requests) were made to Media.rainpos.com and 15% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (403 ms) relates to the external source Media.rainpos.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 420.6 kB (16%)

Content Size

2.7 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Familytreeandme.com main page is 2.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 82.8 kB

  • Original 112.8 kB
  • After minification 111.1 kB
  • After compression 29.9 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 82.8 kB or 73% of the original size.

Image Optimization

-9%

Potential reduce by 162.6 kB

  • Original 1.9 MB
  • After minification 1.7 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. Family Treeandme images are well optimized though.

JavaScript Optimization

-31%

Potential reduce by 175.1 kB

  • Original 563.5 kB
  • After minification 561.6 kB
  • After compression 388.4 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 175.1 kB or 31% of the original size.

CSS Optimization

-0%

Potential reduce by 45 B

  • Original 106.7 kB
  • After minification 106.7 kB
  • After compression 106.7 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. Familytreeandme.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (50%)

Requests Now

48

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

familytreeandme.com

familytreeandme.com

35 ms

www.familytreeandme.com

www.familytreeandme.com

255 ms

all.min.css

all.min.css

52 ms

v4-shims.min.css

v4-shims.min.css

50 ms

bootstrap.min.css

bootstrap.min.css

114 ms

jquery-ui.css

jquery-ui.css

113 ms

css

css

122 ms

jquery.tools.min.js

jquery.tools.min.js

90 ms

jquery.min.js

jquery.min.js

179 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

87 ms

jquery-ui.min.js

jquery-ui.min.js

200 ms

json2.js

json2.js

87 ms

bootstrap.min.js

bootstrap.min.js

121 ms

recaptchaCode.js

recaptchaCode.js

120 ms

api.js

api.js

172 ms

api.js

api.js

189 ms

products-28.js

products-28.js

119 ms

axios.0.18.0.min.js

axios.0.18.0.min.js

171 ms

big.min.js

big.min.js

119 ms

lib.js

lib.js

118 ms

cart.js

cart.js

187 ms

polyfill.min.js

polyfill.min.js

226 ms

WaitList.js

WaitList.js

188 ms

186 ms

379x271_logow_black_background5x7jpg.jpg

379x271_logow_black_background5x7jpg.jpg

196 ms

ss_663_2273494_3.jpg

ss_663_2273494_3.jpg

208 ms

ss_663_2273494_2.jpg

ss_663_2273494_2.jpg

262 ms

ss_663_2273494_3_20170306125336.jpg

ss_663_2273494_3_20170306125336.jpg

217 ms

ss_663_2273494_4.jpg

ss_663_2273494_4.jpg

217 ms

ss_663_2273494_5.jpg

ss_663_2273494_5.jpg

217 ms

ss_663_2273494_6_20170309220026.jpg

ss_663_2273494_6_20170309220026.jpg

262 ms

ss_663_2273494_7.jpg

ss_663_2273494_7.jpg

329 ms

ss_663_2273494_8.jpg

ss_663_2273494_8.jpg

329 ms

ss_663_2273494_9_20170307200455.jpg

ss_663_2273494_9_20170307200455.jpg

331 ms

ss_663_2273494_10.jpg

ss_663_2273494_10.jpg

331 ms

ss_663_2273494_11_20170309220423.jpg

ss_663_2273494_11_20170309220423.jpg

331 ms

ss_663_2273494_12.jpg

ss_663_2273494_12.jpg

337 ms

grove.jpg

grove.jpg

392 ms

bott.jpg

bott.jpg

374 ms

mckinnon.jpg

mckinnon.jpg

403 ms

generation.jpg

generation.jpg

371 ms

paypal_logo.jpg

paypal_logo.jpg

386 ms

cart-bg-1a.png

cart-bg-1a.png

152 ms

hex5f021f_burgundy_design_swirl_boldtiny09867633333333.jpg

hex5f021f_burgundy_design_swirl_boldtiny09867633333333.jpg

346 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

100 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

118 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

166 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

165 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtU.woff

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKdFvXDXbtU.woff

127 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtU.woff

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKeiunDXbtU.woff

127 ms

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtU.woff

nuFvD-vYSZviVYUb_rj3ij__anPXJzDwcbmjWBN2PKfsunDXbtU.woff

163 ms

fa-brands-400.ttf

fa-brands-400.ttf

98 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

50 ms

KFOkCnqEu92Fr1Mu51xIIzQ.woff

KFOkCnqEu92Fr1Mu51xIIzQ.woff

126 ms

KFOjCnqEu92Fr1Mu51TjASc6CsI.woff

KFOjCnqEu92Fr1Mu51TjASc6CsI.woff

166 ms

all.js

all.js

70 ms

recaptcha__en.js

recaptcha__en.js

116 ms

ga.js

ga.js

67 ms

all.js

all.js

13 ms

__utm.gif

__utm.gif

20 ms

89 ms

Accessibility Review

familytreeandme.com accessibility score

83

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Links do not have a discernible name

Best Practices

familytreeandme.com best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

familytreeandme.com SEO score

100

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Familytreeandme.com 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 Familytreeandme.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

familytreeandme.com

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