Tools & Wizards About Us
famly.co screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

famly.co

Famly | The Early Childhood Platform

Page Load Speed

3.8 sec in total

First Response

192 ms

Resources Loaded

3.2 sec

Page Rendered

438 ms

famly.co screenshot

About Website

Welcome to famly.co homepage info - get ready to check Famly best content for United Kingdom right away, or after learning these important things about famly.co

Bring everyone closer with one easy-to-use Early Childhood Platform for families, educators, and management. Try it for free.

Visit famly.co

Key Findings

We analyzed Famly.co page load time and found that the first response time was 192 ms and then it took 3.6 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

famly.co performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value2,500 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

famly.co

192 ms

famly.co

1388 ms

234 ms

415 ms

css

59 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 64% of them (25 requests) were addressed to the original Famly.co, 15% (6 requests) were made to Fonts.gstatic.com and 8% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Famly.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 72.0 kB (10%)

Content Size

723.6 kB

After Optimization

651.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Famly.co main page is 723.6 kB. 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 613.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 45.2 kB

  • Original 55.7 kB
  • After minification 50.7 kB
  • After compression 10.5 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 45.2 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 26.7 kB

  • Original 613.3 kB
  • After minification 586.6 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. Famly images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 93 B

  • Original 54.6 kB
  • After minification 54.6 kB
  • After compression 54.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.

Requests Breakdown

Number of requests can be reduced by 10 (36%)

Requests Now

28

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

famly.co

famly.co

192 ms

famly.co

famly.co

1388 ms

234 ms

415 ms

css

css

59 ms

css

css

73 ms

css

css

85 ms

jquery.min.js

jquery.min.js

71 ms

322 ms

504 ms

503 ms

329 ms

famlyLogoHvid-1-1.png

famlyLogoHvid-1-1.png

170 ms

Screen-Shot-2016-01-27-at-14.34.25-1.png

Screen-Shot-2016-01-27-at-14.34.25-1.png

495 ms

static1.squarespace-2-300x102.jpg

static1.squarespace-2-300x102.jpg

170 ms

static1.squarespace-1-1-300x101.jpg

static1.squarespace-1-1-300x101.jpg

151 ms

static1.squarespace-5.png

static1.squarespace-5.png

169 ms

mainproductshot2-1.png

mainproductshot2-1.png

585 ms

Screen-Shot-2016-01-27-at-15.34.05-1.png

Screen-Shot-2016-01-27-at-15.34.05-1.png

516 ms

Screen-Shot-2016-02-01-at-17.16.07-1.png

Screen-Shot-2016-02-01-at-17.16.07-1.png

664 ms

imgres-1.jpg

imgres-1.jpg

305 ms

stine-1.jpg

stine-1.jpg

458 ms

Screen-Shot-2016-02-01-at-16.47.31-1.png

Screen-Shot-2016-02-01-at-16.47.31-1.png

731 ms

security-faded-1.png

security-faded-1.png

778 ms

helpsupport.png

helpsupport.png

676 ms

famly.co

famly.co

1016 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

66 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

92 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

111 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

125 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

711 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

853 ms

JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf

JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf

140 ms

bIcY3_3JNqUVRAQQRNVteQ.ttf

bIcY3_3JNqUVRAQQRNVteQ.ttf

140 ms

analytics.js

analytics.js

64 ms

ajax-loader.gif

ajax-loader.gif

707 ms

collect

collect

51 ms

APP_ID

APP_ID

38 ms

intercom.7cc40b8a.js

intercom.7cc40b8a.js

44 ms

Accessibility Review

famly.co accessibility score

100

Accessibility Issues

Best Practices

famly.co best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Missing source maps for large first-party JavaScript

SEO Factors

famly.co 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 Famly.co 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 Famly.co 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

famly.co

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