Tools & Wizards About Us

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

familyshare.com

Familytoday | Discover How To Improve Your Family Life And More

Page Load Speed

2 sec in total

First Response

154 ms

Resources Loaded

1.4 sec

Page Rendered

364 ms

About Website

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

FamilyToday is dedicated to strengthening families to better our communities and our world. Read daily articles designed to help you improve your relationships, become a better parent, and so much mor...

Visit familyshare.com

Key Findings

We analyzed Familyshare.com page load time and found that the first response time was 154 ms and then it took 1.8 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

familyshare.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value2,650 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.078

94/100

15%

TTI (Time to Interactive)

Value22.0 s

1/100

10%

Network Requests Diagram

familyshare.com

154 ms

www.familytoday.com

148 ms

pushly-sdk.min.js

107 ms

gtm.js

207 ms

analytics.js

120 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Familyshare.com, 21% (12 requests) were made to Wp-media.familytoday.com and 16% (9 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Familytoday.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 214.3 kB (19%)

Content Size

1.1 MB

After Optimization

929.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 172.5 kB

  • Original 206.4 kB
  • After minification 196.8 kB
  • After compression 34.0 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 172.5 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 132.3 kB
  • After minification 132.3 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. Family Share images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 38.6 kB

  • Original 790.6 kB
  • After minification 790.6 kB
  • After compression 752.1 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

-24%

Potential reduce by 3.3 kB

  • Original 14.1 kB
  • After minification 14.1 kB
  • After compression 10.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. Familyshare.com needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 24% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (42%)

Requests Now

45

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

familyshare.com accessibility score

64

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-*] attributes do not match their roles

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

Form elements do not have associated labels

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

familyshare.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

familyshare.com SEO score

77

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

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

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 Familyshare.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 Familyshare.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

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