Tools & Wizards About Us
famcard.me screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

famcard.me

FamApp: Make payments with your own UPI and Card

Page Load Speed

8.9 sec in total

First Response

380 ms

Resources Loaded

5.2 sec

Page Rendered

3.3 sec

famcard.me screenshot

About Website

Welcome to famcard.me homepage info - get ready to check Fam Card best content for India right away, or after learning these important things about famcard.me

FamX Spending Account for everyone · Get a customised card & UPI ID · Keep your bank statements clean · Track & keep expenses in check · Open for ages 11+

Visit famcard.me

Key Findings

We analyzed Famcard.me page load time and found that the first response time was 380 ms and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

famcard.me performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

71/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value950 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value23.1 s

1/100

10%

Network Requests Diagram

famcard.me

380 ms

famcard.me

792 ms

1eeb47b16e5026ae6367.css

188 ms

db95c50e3f11143c3507.css

373 ms

fp-logo-white.svg

834 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 97% of them (64 requests) were addressed to the original Famcard.me, 2% (1 request) were made to Fampay-app-content.s3.ap-south-1.amazonaws.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Famcard.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 485.7 kB (9%)

Content Size

5.3 MB

After Optimization

4.8 MB

  • HTML
  • Images

In fact, the total size of Famcard.me main page is 5.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. 80% 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 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 25.4 kB

  • Original 31.1 kB
  • After minification 31.1 kB
  • After compression 5.7 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 25.4 kB or 82% of the original size.

Image Optimization

-9%

Potential reduce by 460.4 kB

  • Original 5.3 MB
  • After minification 4.8 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. Fam Card images are well optimized though.

Requests Breakdown

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

Requests Now

59

After Optimization

48

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

famcard.me

famcard.me

380 ms

famcard.me

famcard.me

792 ms

1eeb47b16e5026ae6367.css

1eeb47b16e5026ae6367.css

188 ms

db95c50e3f11143c3507.css

db95c50e3f11143c3507.css

373 ms

fp-logo-white.svg

fp-logo-white.svg

834 ms

polyfills-8683bd742a84c1edd48c.js

polyfills-8683bd742a84c1edd48c.js

732 ms

webpack-da3f75ab19172a79e001.js

webpack-da3f75ab19172a79e001.js

814 ms

framework-f9a3284d684380663b93.js

framework-f9a3284d684380663b93.js

1193 ms

282-60cff030ccd6b24dccc0.js

282-60cff030ccd6b24dccc0.js

975 ms

778-c17961c08b01ffc1e801.js

778-c17961c08b01ffc1e801.js

816 ms

main-60aaf1501a313df3af96.js

main-60aaf1501a313df3af96.js

815 ms

_app-b33b82f666ea3e9f3d2e.js

_app-b33b82f666ea3e9f3d2e.js

917 ms

453-2b62457324d111179ede.js

453-2b62457324d111179ede.js

1125 ms

index-448a361369afb4a17f21.js

index-448a361369afb4a17f21.js

993 ms

_buildManifest.js

_buildManifest.js

993 ms

_ssgManifest.js

_ssgManifest.js

1099 ms

js

js

74 ms

FamCardMeLogo.svg

FamCardMeLogo.svg

1149 ms

playBtn.png

playBtn.png

1160 ms

Underline.svg

Underline.svg

1157 ms

rewardIcon.svg

rewardIcon.svg

1647 ms

giftIcon.svg

giftIcon.svg

1293 ms

FamCardMe.png

FamCardMe.png

1895 ms

listImageCoin.svg

listImageCoin.svg

1339 ms

listImageName.svg

listImageName.svg

1347 ms

listImageWifi.svg

listImageWifi.svg

1361 ms

listImageDesign.svg

listImageDesign.svg

1478 ms

listImageCalender.svg

listImageCalender.svg

1524 ms

FamCardClassicLogo.png

FamCardClassicLogo.png

1532 ms

FamCardClassic.png

FamCardClassic.png

2360 ms

visaCardBlank.png

visaCardBlank.png

2631 ms

doodle_bag.png

doodle_bag.png

1894 ms

doodle_basket.png

doodle_basket.png

1903 ms

doodle_skate.png

doodle_skate.png

1830 ms

doodle_pizza.png

doodle_pizza.png

2199 ms

doodle_music.png

doodle_music.png

2068 ms

doodle_chai.png

doodle_chai.png

2081 ms

doodle_flower.png

doodle_flower.png

2275 ms

doodle_tanmay.png

doodle_tanmay.png

2254 ms

doodle_bike.png

doodle_bike.png

2269 ms

doodle_panda.png

doodle_panda.png

2234 ms

doodle_dragons.png

doodle_dragons.png

1931 ms

Metropolis-SemiBold.woff

Metropolis-SemiBold.woff

1666 ms

Metropolis-Bold.woff

Metropolis-Bold.woff

1730 ms

Metropolis-Medium.woff

Metropolis-Medium.woff

1771 ms

Metropolis-Regular.woff

Metropolis-Regular.woff

1780 ms

Chilldranety-400.ttf

Chilldranety-400.ttf

1783 ms

envelopMob.png

envelopMob.png

1724 ms

gradient.png

gradient.png

2426 ms

dog.png

dog.png

1767 ms

basket.png

basket.png

2049 ms

bag.png

bag.png

1701 ms

car.png

car.png

1679 ms

skate.png

skate.png

1863 ms

bike.png

bike.png

1788 ms

dragon.png

dragon.png

1700 ms

panda.png

panda.png

1717 ms

thumbnail.png

thumbnail.png

1996 ms

vibe1.png

vibe1.png

1803 ms

vibe2.png

vibe2.png

2019 ms

vibe3.png

vibe3.png

2101 ms

vibe4.png

vibe4.png

2519 ms

vibe5.png

vibe5.png

1805 ms

vibe6.png

vibe6.png

2073 ms

vibe7.png

vibe7.png

1692 ms

vibe8.png

vibe8.png

1680 ms

Accessibility Review

famcard.me accessibility score

83

Accessibility Issues

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

Image elements do not have [alt] attributes

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

famcard.me best practices score

83

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

High

Browser errors were logged to the console

SEO Factors

famcard.me SEO score

92

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

Image elements do not have [alt] attributes

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 Famcard.me 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 Famcard.me 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

famcard.me

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