Tools & Wizards About Us
whatsform.com screenshot

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

whatsform.com

Collect data directly to your WhatsApp number - WhatsForm

Page Load Speed

1.8 sec in total

First Response

23 ms

Resources Loaded

904 ms

Page Rendered

916 ms

whatsform.com screenshot

About Website

Visit whatsform.com now to see the best up-to-date Whats Form content for India and also check out these interesting facts you probably never knew about whatsform.com

Create a free form using our drag & drop WhatsApp form builder. Get form responses directly to your WhatsApp from the customer's number. Convert existing google forms to WhatsApp contact form in one c...

Visit whatsform.com

Key Findings

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

whatsform.com performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

39/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value6.2 s

62/100

10%

Network Requests Diagram

whatsform.com

23 ms

whatsform.com

230 ms

css2

58 ms

bootstrap.min.css

60 ms

slick.css

49 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 51% of them (23 requests) were addressed to the original Whatsform.com, 11% (5 requests) were made to Cdnjs.cloudflare.com and 9% (4 requests) were made to Cdn.jsdelivr.net. The less responsive or slowest element that took the longest time to load (369 ms) relates to the external source Record.micro.company.

Page Optimization Overview & Recommendations

Page size can be reduced by 29.8 kB (2%)

Content Size

1.3 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-80%

Potential reduce by 27.1 kB

  • Original 33.7 kB
  • After minification 27.2 kB
  • After compression 6.6 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 6.5 kB, which is 19% 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 27.1 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.3 MB
  • After minification 1.3 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. Whats Form images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 2.7 kB

  • Original 6.9 kB
  • After minification 6.9 kB
  • After compression 4.2 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 2.7 kB or 39% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (58%)

Requests Now

40

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whatsform.com

whatsform.com

23 ms

whatsform.com

whatsform.com

230 ms

css2

css2

58 ms

bootstrap.min.css

bootstrap.min.css

60 ms

slick.css

slick.css

49 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

52 ms

aos.css

aos.css

60 ms

all.min.css

all.min.css

66 ms

style.css

style.css

117 ms

typing.css

typing.css

138 ms

intlTelInput.css

intlTelInput.css

73 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

56 ms

fpr.js

fpr.js

53 ms

script.js

script.js

369 ms

intlTelInput.min.js

intlTelInput.min.js

80 ms

script.js

script.js

265 ms

style.css

style.css

162 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

70 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

51 ms

slick.min.js

slick.min.js

50 ms

aos.js

aos.js

72 ms

jquery.maskedinput.min.js

jquery.maskedinput.min.js

166 ms

script.js

script.js

163 ms

signup.js

signup.js

157 ms

script.js

script.js

230 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

62 ms

framework.css

framework.css

163 ms

css2

css2

18 ms

logo-dark.png

logo-dark.png

123 ms

logo.png

logo.png

112 ms

whatsapphero.png

whatsapphero.png

126 ms

chatbot.png

chatbot.png

130 ms

crm.png

crm.png

125 ms

laptop-en.png

laptop-en.png

117 ms

sreeragfabuframes.jpeg

sreeragfabuframes.jpeg

227 ms

travel.jpg

travel.jpg

230 ms

contact.jpg

contact.jpg

237 ms

feedback.jpg

feedback.jpg

247 ms

restaurant.jpg

restaurant.jpg

246 ms

shopping.jpg

shopping.jpg

255 ms

registration.jpg

registration.jpg

343 ms

font

font

28 ms

fa-solid-900.woff

fa-solid-900.woff

28 ms

fa-regular-400.woff

fa-regular-400.woff

10 ms

font

font

28 ms

Accessibility Review

whatsform.com accessibility score

52

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

whatsform.com SEO score

90

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatsform.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 Whatsform.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

whatsform.com

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