Tools & Wizards About Us
familigram.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

familigram.com

Familigram - Connecting Generations - Delivering your message to loved ones in care

Page Load Speed

2 sec in total

First Response

180 ms

Resources Loaded

1.7 sec

Page Rendered

86 ms

familigram.com screenshot

About Website

Visit familigram.com now to see the best up-to-date Familigram content and also check out these interesting facts you probably never knew about familigram.com

Familigram deliver your social media messages to Granny in a format she can relax for, enjoy and embrace - print telegram style, photo message Familigrams.

Visit familigram.com

Key Findings

We analyzed Familigram.com page load time and found that the first response time was 180 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

familigram.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

familigram.com

180 ms

familigram.com

333 ms

style.css

230 ms

modernizr.custom.js

236 ms

chargebee.js

17 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 67% of them (35 requests) were addressed to the original Familigram.com, 19% (10 requests) were made to Js.chargebee.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (536 ms) belongs to the original domain Familigram.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 783.5 kB (30%)

Content Size

2.6 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Familigram.com main page is 2.6 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. 55% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 14.3 kB

  • Original 18.6 kB
  • After minification 15.5 kB
  • After compression 4.3 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 3.1 kB, which is 17% 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 14.3 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 42.8 kB

  • Original 1.5 MB
  • After minification 1.4 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. Familigram images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 348.2 kB

  • Original 716.8 kB
  • After minification 619.0 kB
  • After compression 368.6 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 348.2 kB or 49% of the original size.

CSS Optimization

-87%

Potential reduce by 378.2 kB

  • Original 435.5 kB
  • After minification 384.9 kB
  • After compression 57.3 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. Familigram.com needs all CSS files to be minified and compressed as it can save up to 378.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (76%)

Requests Now

45

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

familigram.com

familigram.com

180 ms

familigram.com

familigram.com

333 ms

style.css

style.css

230 ms

modernizr.custom.js

modernizr.custom.js

236 ms

chargebee.js

chargebee.js

17 ms

feedback2.js

feedback2.js

72 ms

jquery.min.js

jquery.min.js

428 ms

jquery.easings.min.js

jquery.easings.min.js

234 ms

bootstrap.min.js

bootstrap.min.js

307 ms

velocity.min.js

velocity.min.js

308 ms

velocity.ui.min.js

velocity.ui.min.js

305 ms

notifyMe.js

notifyMe.js

306 ms

contact-me.js

contact-me.js

306 ms

vegas.js

vegas.js

381 ms

jquery.mousewheel.js

jquery.mousewheel.js

383 ms

jquery.mCustomScrollbar.js

jquery.mCustomScrollbar.js

536 ms

classie.js

classie.js

383 ms

dialogFx.js

dialogFx.js

384 ms

photoswipe.js

photoswipe.js

534 ms

photoswipe-ui-default.js

photoswipe-ui-default.js

535 ms

main.js

main.js

459 ms

font-awesome.min.css

font-awesome.min.css

235 ms

ionicons.min.css

ionicons.min.css

276 ms

bootstrap.min.css

bootstrap.min.css

462 ms

animate.css

animate.css

389 ms

photoswipe.css

photoswipe.css

353 ms

default-skin.css

default-skin.css

386 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

387 ms

vegas.css

vegas.css

384 ms

css

css

25 ms

css

css

38 ms

201-156b52a7e4e2626c2fdf.js

201-156b52a7e4e2626c2fdf.js

39 ms

192-8ebc18c88b6cd0946fe5.js

192-8ebc18c88b6cd0946fe5.js

30 ms

familigram_logo_white.png

familigram_logo_white.png

163 ms

apple.png

apple.png

241 ms

googleplay.png

googleplay.png

162 ms

post1.jpg

post1.jpg

309 ms

post2.jpg

post2.jpg

183 ms

familigram-circles-2019.jpg

familigram-circles-2019.jpg

463 ms

font

font

127 ms

font

font

137 ms

263975521

263975521

94 ms

animation.css

animation.css

54 ms

master.html

master.html

7 ms

263975521

263975521

118 ms

master.html

master.html

59 ms

ionicons.ttf

ionicons.ttf

88 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

161 ms

master-95012d15674505c4c956.js

master-95012d15674505c4c956.js

5 ms

pi-worker.js

pi-worker.js

10 ms

207-2bc4476004887782f755.js

207-2bc4476004887782f755.js

7 ms

215-82fd3c3ff1669fc448e4.js

215-82fd3c3ff1669fc448e4.js

6 ms

Accessibility Review

familigram.com accessibility score

86

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

familigram.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

familigram.com SEO score

92

Search Engine Optimization Advices

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

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

familigram.com

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