Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

familytime.io

FamilyTime: Parental Control App | Screen Time Limit for Android & iOS

Page Load Speed

4.2 sec in total

First Response

132 ms

Resources Loaded

2.5 sec

Page Rendered

1.5 sec

familytime.io screenshot

About Website

Click here to check amazing Family Time content for Pakistan. Otherwise, check out these important facts you probably never knew about familytime.io

FamilyTime is the best parental control app for Android & iOS devices. Monitor and track your child's cell phone activities, Limit screen time, and Filter internet.

Visit familytime.io

Key Findings

We analyzed Familytime.io page load time and found that the first response time was 132 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

familytime.io performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value1,220 ms

20/100

30%

CLS (Cumulative Layout Shift)

Value0.531

14/100

15%

TTI (Time to Interactive)

Value9.4 s

31/100

10%

Network Requests Diagram

familytime.io

132 ms

familytime.io

410 ms

gtm.js

77 ms

A198442-0c3a-4957-ba42-aec4f1edb67e1.js

93 ms

desktop-style-en-v2.css

66 ms

Our browser made a total of 155 requests to load all elements on the main page. We found that 89% of them (138 requests) were addressed to the original Familytime.io, 6% (9 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (886 ms) belongs to the original domain Familytime.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 96.6 kB (59%)

Content Size

162.9 kB

After Optimization

66.3 kB

In fact, the total size of Familytime.io main page is 162.9 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. 70% of websites need less resources to load. HTML takes 109.5 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 96.4 kB

  • Original 109.5 kB
  • After minification 70.5 kB
  • After compression 13.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 39.0 kB, which is 36% 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 96.4 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 3.4 kB
  • After minification 3.4 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 Time images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 3 B

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

-2%

Potential reduce by 246 B

  • Original 14.8 kB
  • After minification 14.8 kB
  • After compression 14.6 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. Familytime.io has all CSS files already compressed.

Requests Breakdown

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

Requests Now

144

After Optimization

123

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

Accessibility Review

familytime.io accessibility score

88

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-hidden="true"] elements contain focusable descendents

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

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.

Best Practices

familytime.io best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

familytime.io SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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 Familytime.io 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 Familytime.io 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 Time. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: