Tools & Wizards About Us
finlock.in screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

finlock.in

FinLock

Page Load Speed

7.7 sec in total

First Response

111 ms

Resources Loaded

6.9 sec

Page Rendered

717 ms

finlock.in screenshot

About Website

Welcome to finlock.in homepage info - get ready to check Fin Lock best content for India right away, or after learning these important things about finlock.in

India’s only app for protection against online frauds - Phishing, fake SMS, UPI fraud, SIM swap, Privacy apps with cyber insurance cover up to Rs 1 lakh.

Visit finlock.in

Key Findings

We analyzed Finlock.in page load time and found that the first response time was 111 ms and then it took 7.6 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

finlock.in performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value18.6 s

0/100

25%

SI (Speed Index)

Value9.1 s

13/100

10%

TBT (Total Blocking Time)

Value2,950 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value27.5 s

0/100

10%

Network Requests Diagram

finlock.in

111 ms

www.finlock.in

1596 ms

icon

110 ms

bootstrap.min.css

129 ms

font-awesome.min.css

556 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 75% of them (36 requests) were addressed to the original Finlock.in, 6% (3 requests) were made to Googletagmanager.com and 6% (3 requests) were made to Finlocks3.s3-ap-south-1.amazonaws.com. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Finlock.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 74.3 kB (16%)

Content Size

474.1 kB

After Optimization

399.8 kB

  • HTML
  • Images

In fact, the total size of Finlock.in main page is 474.1 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. 65% of websites need less resources to load. Images take 429.8 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 37.7 kB

  • Original 44.3 kB
  • After minification 44.1 kB
  • After compression 6.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 37.7 kB or 85% of the original size.

Image Optimization

-9%

Potential reduce by 36.6 kB

  • Original 429.8 kB
  • After minification 393.3 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. Fin Lock images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 20 (50%)

Requests Now

40

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

finlock.in

finlock.in

111 ms

www.finlock.in

www.finlock.in

1596 ms

icon

icon

110 ms

bootstrap.min.css

bootstrap.min.css

129 ms

font-awesome.min.css

font-awesome.min.css

556 ms

owl.carousel.css

owl.carousel.css

743 ms

style.css

style.css

1141 ms

media.css

media.css

1148 ms

jquery-2.1.1.js

jquery-2.1.1.js

1178 ms

owl.carousel.min.js

owl.carousel.min.js

971 ms

bootstrap.min.js

bootstrap.min.js

147 ms

js

js

141 ms

styles.e40bb509f636d3f7c283.css

styles.e40bb509f636d3f7c283.css

778 ms

runtime-es2015.cdfb0ddb511f65fdc0a0.js

runtime-es2015.cdfb0ddb511f65fdc0a0.js

566 ms

runtime-es5.cdfb0ddb511f65fdc0a0.js

runtime-es5.cdfb0ddb511f65fdc0a0.js

615 ms

polyfills-es5.223371d329dc1d2ced10.js

polyfills-es5.223371d329dc1d2ced10.js

1720 ms

polyfills-es2015.be5d568be8418a3cabb6.js

polyfills-es2015.be5d568be8418a3cabb6.js

1019 ms

main-es2015.984ee763727ea9852764.js

main-es2015.984ee763727ea9852764.js

4737 ms

main-es5.984ee763727ea9852764.js

main-es5.984ee763727ea9852764.js

1959 ms

gtm.js

gtm.js

215 ms

fbevents.js

fbevents.js

792 ms

1657824151341.jpg

1657824151341.jpg

3771 ms

logo.png

logo.png

734 ms

direct-download.png

direct-download.png

732 ms

cross-icon.png

cross-icon.png

732 ms

homebg.jpg

homebg.jpg

734 ms

stepbg.jpg

stepbg.jpg

952 ms

mobhome.png

mobhome.png

1278 ms

risk-icon.png

risk-icon.png

815 ms

notification.png

notification.png

952 ms

transcation-icon.png

transcation-icon.png

1033 ms

wrkfaurd-icon.png

wrkfaurd-icon.png

1033 ms

time.png

time.png

1032 ms

tick.png

tick.png

1276 ms

footer-logo.png

footer-logo.png

1293 ms

dwnlodbtn.png

dwnlodbtn.png

1286 ms

facebook.png

facebook.png

1280 ms

twitter.png

twitter.png

3716 ms

insta.png

insta.png

3717 ms

linkden.png

linkden.png

3717 ms

1654451248558.png

1654451248558.png

3718 ms

1654101343249.png

1654101343249.png

3721 ms

gibsonregular-webfont.woff

gibsonregular-webfont.woff

2910 ms

gibsonsemibd-webfont.woff

gibsonsemibd-webfont.woff

2910 ms

gibsonlight-webfont.woff

gibsonlight-webfont.woff

2911 ms

575192273827299

575192273827299

89 ms

js

js

254 ms

widget

widget

3110 ms

Accessibility Review

finlock.in accessibility score

63

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

finlock.in 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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

finlock.in SEO score

89

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Finlock.in can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Finlock.in 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

finlock.in

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