Tools & Wizards About Us
wizely.in screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

wizely.in

Earn cash rewards for good financial habits with Wizely

Page Load Speed

3.5 sec in total

First Response

377 ms

Resources Loaded

2.8 sec

Page Rendered

322 ms

wizely.in screenshot

About Website

Visit wizely.in now to see the best up-to-date Wizely content for India and also check out these interesting facts you probably never knew about wizely.in

An app that understands your financial life and guides you on a personalized path towards financial wellness.

Visit wizely.in

Key Findings

We analyzed Wizely.in page load time and found that the first response time was 377 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

wizely.in performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value240 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value12.4 s

14/100

10%

Network Requests Diagram

wizely.in

377 ms

wizely.in

764 ms

bootstrap.min.css

48 ms

tiny-slider.css

53 ms

css2

58 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 49% of them (24 requests) were addressed to the original Wizely.in, 20% (10 requests) were made to Cdnjs.cloudflare.com and 6% (3 requests) were made to Cdn.taboola.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Wizely.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 134.9 kB (12%)

Content Size

1.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wizely.in main page is 1.2 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 794.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 33.8 kB

  • Original 40.6 kB
  • After minification 26.2 kB
  • After compression 6.9 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 14.5 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 33.8 kB or 83% of the original size.

Image Optimization

-9%

Potential reduce by 73.6 kB

  • Original 794.7 kB
  • After minification 721.1 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. Wizely images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 7.5 kB

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

-80%

Potential reduce by 20.1 kB

  • Original 25.1 kB
  • After minification 17.0 kB
  • After compression 5.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. Wizely.in needs all CSS files to be minified and compressed as it can save up to 20.1 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (56%)

Requests Now

43

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wizely.in

wizely.in

377 ms

wizely.in

wizely.in

764 ms

bootstrap.min.css

bootstrap.min.css

48 ms

tiny-slider.css

tiny-slider.css

53 ms

css2

css2

58 ms

animate.min.css

animate.min.css

56 ms

style.css

style.css

189 ms

slider.css

slider.css

376 ms

custom.css

custom.css

554 ms

stylesheet2.css

stylesheet2.css

554 ms

jquery.min.js

jquery.min.js

58 ms

js

js

77 ms

jquery.serializeObject.min.js

jquery.serializeObject.min.js

314 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

56 ms

modernizr.js

modernizr.js

61 ms

popper.min.js

popper.min.js

74 ms

bootstrap.min.js

bootstrap.min.js

67 ms

tiny-slider.js

tiny-slider.js

68 ms

content-api.min.js

content-api.min.js

79 ms

all.js

all.js

81 ms

script.js

script.js

622 ms

fbevents.js

fbevents.js

113 ms

integrate_0a6c4210a790b4e0af13419f5ab712bb.js

integrate_0a6c4210a790b4e0af13419f5ab712bb.js

414 ms

tfa.js

tfa.js

140 ms

loader_three_bars.gif

loader_three_bars.gif

375 ms

Wizely_Logo_Mar11-1.png

Wizely_Logo_Mar11-1.png

186 ms

WizeUP-Logo.png

WizeUP-Logo.png

185 ms

playstore_badge.png

playstore_badge.png

186 ms

partnership_with_1x@2x.png

partnership_with_1x@2x.png

372 ms

pixel_23.png

pixel_23.png

921 ms

background_transaction.png

background_transaction.png

370 ms

pixel_20.png

pixel_20.png

740 ms

background_plan_screen.png

background_plan_screen.png

555 ms

pixel_21.png

pixel_21.png

1107 ms

background_recipe_screen.png

background_recipe_screen.png

558 ms

pixel_22.png

pixel_22.png

937 ms

Wizely-Logo-White.png

Wizely-Logo-White.png

739 ms

location_icon.svg

location_icon.svg

744 ms

email_icon.svg

email_icon.svg

923 ms

white_amfi_vertical.png

white_amfi_vertical.png

924 ms

heart1.png

heart1.png

930 ms

zYXgKVElMYYaJe8bpLHnCwDKtdY.ttf

zYXgKVElMYYaJe8bpLHnCwDKtdY.ttf

94 ms

zYX9KVElMYYaJe8bpLHnCwDKjSL9MIY.ttf

zYX9KVElMYYaJe8bpLHnCwDKjSL9MIY.ttf

99 ms

zYX9KVElMYYaJe8bpLHnCwDKjWr7MIY.ttf

zYX9KVElMYYaJe8bpLHnCwDKjWr7MIY.ttf

109 ms

insight.min.js

insight.min.js

61 ms

json

json

44 ms

cds-pips.js

cds-pips.js

3 ms

eid.es5.js

eid.es5.js

3 ms

pips.taboola.com

pips.taboola.com

16 ms

Accessibility Review

wizely.in accessibility score

84

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

wizely.in SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

wizely.in

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