Tools & Wizards About Us
familytime.io screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    57% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

familytime.io

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

Page Load Speed

5.1 sec in total

First Response

1.2 sec

Resources Loaded

2.9 sec

Page Rendered

1 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 1.2 sec and then it took 3.9 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

familytime.io performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

56/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value17,630 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value24.9 s

0/100

10%

Network Requests Diagram

familytime.io

1173 ms

jquery.fancybox.css

145 ms

css

66 ms

main.css

214 ms

typography.css

157 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 69% of them (63 requests) were addressed to the original Familytime.io, 12% (11 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Assets.zendesk.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Familytime.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (46%)

Content Size

3.3 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Familytime.io main page is 3.3 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 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 34.5 kB

  • Original 46.3 kB
  • After minification 40.5 kB
  • After compression 11.8 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 5.7 kB, which is 12% 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 34.5 kB or 75% of the original size.

Image Optimization

-32%

Potential reduce by 702.7 kB

  • Original 2.2 MB
  • After minification 1.5 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, Family Time needs image optimization as it can save up to 702.7 kB or 32% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 623.4 kB

  • Original 873.5 kB
  • After minification 873.5 kB
  • After compression 250.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 623.4 kB or 71% of the original size.

CSS Optimization

-84%

Potential reduce by 148.7 kB

  • Original 177.8 kB
  • After minification 146.7 kB
  • After compression 29.0 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 needs all CSS files to be minified and compressed as it can save up to 148.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (33%)

Requests Now

75

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 75 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 8 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

familytime.io

familytime.io

1173 ms

jquery.fancybox.css

jquery.fancybox.css

145 ms

css

css

66 ms

main.css

main.css

214 ms

typography.css

typography.css

157 ms

buttons.css

buttons.css

168 ms

icons.css

icons.css

177 ms

spacing.css

spacing.css

189 ms

fonts.css

fonts.css

220 ms

colors.css

colors.css

233 ms

font-awesome.css

font-awesome.css

251 ms

media-1025px.css

media-1025px.css

262 ms

media-768px.css

media-768px.css

286 ms

custom.js

custom.js

422 ms

jquery.min.js

jquery.min.js

51 ms

jquery.fancybox.js

jquery.fancybox.js

269 ms

gtm.js

gtm.js

144 ms

main.js

main.js

351 ms

fbevents.js

fbevents.js

196 ms

STOP-2-200x93.png

STOP-2-200x93.png

298 ms

familytime_app_small_darktm.png

familytime_app_small_darktm.png

171 ms

ft-blog-approval-200x107.png

ft-blog-approval-200x107.png

289 ms

biggest_offer_web.jpg

biggest_offer_web.jpg

458 ms

biggest_offer_tablet.jpg

biggest_offer_tablet.jpg

559 ms

biggest_offer_mobile.jpg

biggest_offer_mobile.jpg

317 ms

familytime-blue.png

familytime-blue.png

168 ms

en.png

en.png

165 ms

es.png

es.png

164 ms

ja.png

ja.png

185 ms

background-inner.jpg

background-inner.jpg

312 ms

main-slider.png

main-slider.png

692 ms

familytham-white.png

familytham-white.png

279 ms

limit-time.png

limit-time.png

449 ms

bed-time.png

bed-time.png

448 ms

instant-lock.png

instant-lock.png

449 ms

places.png

places.png

519 ms

location-history.png

location-history.png

486 ms

app-block1.png

app-block1.png

483 ms

app-block2.png

app-block2.png

517 ms

app-block3.png

app-block3.png

555 ms

app-block4.png

app-block4.png

555 ms

app-block5.png

app-block5.png

588 ms

app-block6.png

app-block6.png

610 ms

game-block.png

game-block.png

796 ms

app-block.png

app-block.png

764 ms

rive1.jpg

rive1.jpg

625 ms

star-4.png

star-4.png

675 ms

feature-new.png

feature-new.png

909 ms

label-coming-soon.png

label-coming-soon.png

696 ms

works_on.png

works_on.png

762 ms

androidheadlines.png

androidheadlines.png

764 ms

tnw.png

tnw.png

767 ms

yahoo.png

yahoo.png

849 ms

slashgear.png

slashgear.png

831 ms

thewestsidestory.png

thewestsidestory.png

840 ms

toms-guide.png

toms-guide.png

838 ms

digital-trends.png

digital-trends.png

879 ms

wired.png

wired.png

808 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

80 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

81 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

130 ms

Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf

Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf

172 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

173 ms

mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf

mnpfi9pxYH-Go5UiibESIqCWcynf_cDxXwCLxiixG1c.ttf

172 ms

W4wDsBUluyw0tK3tykhXEfesZW2xOQ-xsNqO47m55DA.ttf

W4wDsBUluyw0tK3tykhXEfesZW2xOQ-xsNqO47m55DA.ttf

172 ms

OLffGBTaF0XFOW1gnuHF0Z0EAVxt0G0biEntp43Qt6E.ttf

OLffGBTaF0XFOW1gnuHF0Z0EAVxt0G0biEntp43Qt6E.ttf

172 ms

7m8l7TlFO-S3VkhHuR0at50EAVxt0G0biEntp43Qt6E.ttf

7m8l7TlFO-S3VkhHuR0at50EAVxt0G0biEntp43Qt6E.ttf

171 ms

12mE4jfMSBTmg-81EiS-YS3USBnSvpkopQaUR-2r7iU.ttf

12mE4jfMSBTmg-81EiS-YS3USBnSvpkopQaUR-2r7iU.ttf

173 ms

t6Nd4cfPRhZP44Q5QAjcC50EAVxt0G0biEntp43Qt6E.ttf

t6Nd4cfPRhZP44Q5QAjcC50EAVxt0G0biEntp43Qt6E.ttf

174 ms

analytics.js

analytics.js

33 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

760 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

785 ms

49 ms

your-privacy.png

your-privacy.png

831 ms

account.png

account.png

813 ms

collect

collect

68 ms

collect

collect

240 ms

manage-devices.png

manage-devices.png

719 ms

invite-parent.png

invite-parent.png

705 ms

uninstalled.png

uninstalled.png

687 ms

update.html

update.html

59 ms

compatible-and-ios-kin.png

compatible-and-ios-kin.png

556 ms

data-security.png

data-security.png

584 ms

familytham-gray.png

familytham-gray.png

700 ms

ga-audiences

ga-audiences

40 ms

payment-mathod-card.png

payment-mathod-card.png

697 ms

app-store.svg

app-store.svg

663 ms

google-play.svg

google-play.svg

667 ms

blips

blips

277 ms

config

config

142 ms

widget_v2.132.js

widget_v2.132.js

21 ms

Accessibility Review

familytime.io accessibility score

85

Accessibility Issues

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

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

Links do not have a discernible name

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

67

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

Browser errors were logged to the console

SEO Factors

familytime.io SEO score

79

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

familytime.io

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: