17.8 sec in total
1.9 sec
13.7 sec
2.2 sec
Click here to check amazing VAATA content. Otherwise, check out these important facts you probably never knew about vaata.com
Vaata is known for its smart products such as DryTab, an In-tank automatic toilet cleaner. As the best toilet cleaner in India, DryTab handles toilet bowl stains effectively
Visit vaata.comWe analyzed Vaata.com page load time and found that the first response time was 1.9 sec and then it took 15.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
vaata.com performance score
name
value
score
weighting
Value8.4 s
0/100
10%
Value15.9 s
0/100
25%
Value47.6 s
0/100
10%
Value72,530 ms
0/100
30%
Value0.034
100/100
15%
Value100.8 s
0/100
10%
1940 ms
421 ms
658 ms
688 ms
707 ms
Our browser made a total of 196 requests to load all elements on the main page. We found that 82% of them (160 requests) were addressed to the original Vaata.com, 5% (10 requests) were made to Fonts.gstatic.com and 3% (6 requests) were made to Demo2wpopal.b-cdn.net. The less responsive or slowest element that took the longest time to load (6.4 sec) belongs to the original domain Vaata.com.
Page size can be reduced by 2.0 MB (27%)
7.6 MB
5.5 MB
In fact, the total size of Vaata.com main page is 7.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. 85% 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 7.0 MB which makes up the majority of the site volume.
Potential reduce by 120.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 120.7 kB or 82% of the original size.
Potential reduce by 1.9 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. Obviously, VAATA needs image optimization as it can save up to 1.9 MB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 12.5 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.
Potential reduce by 21.2 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. Vaata.com has all CSS files already compressed.
Number of requests can be reduced by 121 (71%)
171
50
The browser has sent 171 CSS, Javascripts, AJAX and image requests in order to completely render the main page of VAATA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 74 to 1 for JavaScripts and from 49 to 1 for CSS and as a result speed up the page load time.
vaata.com
1940 ms
wp-emoji-release.min.js
421 ms
shop.css
658 ms
style.min.css
688 ms
theme.min.css
707 ms
wc-blocks-vendors-style.css
708 ms
wc-blocks-style.css
968 ms
gutenberg-blocks.css
709 ms
cancel-order-request-woocommerce-public.css
891 ms
magnific-popup.css
920 ms
jquery.toast.min.css
947 ms
rs6.css
1173 ms
woocommerce_refund_and_exchange_lite-public.css
948 ms
wpcc_front_style.css
1138 ms
advance-ecommerce-tracking-public.css
1145 ms
slick.css
1167 ms
perfect-scrollbar.min.css
1177 ms
custom-theme.css
1178 ms
magnific-popup.css
1357 ms
feather.css
1369 ms
frontend.css
1405 ms
feather.css
1407 ms
frontend.css
1407 ms
style.css
1896 ms
frontend.min.css
1831 ms
post-8305.css
1598 ms
elementor-icons.min.css
1630 ms
animations.min.css
1633 ms
frontend.min.css
1876 ms
post-1086.css
1826 ms
post-668.css
1859 ms
style.min.css
1863 ms
font-awesome.min.css
2061 ms
post-232.css
2055 ms
frontend.min.css
2090 ms
wvs-theme-override.min.css
2095 ms
css
52 ms
js
73 ms
css
15 ms
frontend-tooltip.min.css
1943 ms
elementor.css
1710 ms
woocommerce.css
1869 ms
style.css
1616 ms
fontawesome.min.css
1860 ms
solid.min.css
1636 ms
brands.min.css
1646 ms
pricing-table.css
1468 ms
deals-table.css
1619 ms
font-awesome.css
1630 ms
style.css
1487 ms
post-800.css
1487 ms
wpforms-full.min.css
1615 ms
jquery.min.js
1863 ms
jquery-migrate.min.js
1627 ms
jquery.magnific-popup.min.js
1630 ms
jquery.toast.min.js
1643 ms
cancel-order-request-woocommerce-public.js
1646 ms
frontend.js
1622 ms
rbtools.min.js
2122 ms
rs6.min.js
2562 ms
woocommerce_refund_and_exchange_lite-public.js
1648 ms
wpcc_front_script.js
1647 ms
gtm4wp-woocommerce-enhanced.js
1608 ms
frontend.js
1607 ms
jquery.blockUI.min.js
1652 ms
js.cookie.min.js
1451 ms
woocommerce.min.js
1594 ms
cart-fragments.min.js
1612 ms
underscore.min.js
1654 ms
wp-util.min.js
1633 ms
add-to-cart-variation.min.js
1745 ms
slick.min.js
1651 ms
perfect-scrollbar.jquery.min.js
1657 ms
jquery.magnific-popup.min.js
1661 ms
frontend.js
1637 ms
frontend.js
1767 ms
mailchimp-woocommerce-public.min.js
1811 ms
main.js
1657 ms
skip-link-focus-fix.min.js
1702 ms
text-editor.js
1727 ms
search-popup.js
1830 ms
nav-mobile.js
1822 ms
login.js
1817 ms
happy-addons.min.js
1765 ms
frontend.min.js
1795 ms
header-cart.min.js
1793 ms
footer.min.js
1800 ms
tooltipster.bundle.js
1929 ms
main.min.js
1885 ms
quantity.min.js
1873 ms
cart-canvas.min.js
1869 ms
wp-embed.min.js
1867 ms
webpack.runtime.min.js
1710 ms
frontend-modules.min.js
1829 ms
waypoints.min.js
1799 ms
core.min.js
1802 ms
swiper.min.js
1874 ms
share-link.min.js
1628 ms
dialog.min.js
1582 ms
frontend.min.js
1799 ms
header-group.js
1653 ms
imagesloaded.min.js
1616 ms
webpack-pro.runtime.min.js
1595 ms
jquery.sticky.min.js
1581 ms
frontend.min.js
1794 ms
preloaded-elements-handlers.min.js
1891 ms
preloaded-modules.min.js
1622 ms
frontend.min.js
1609 ms
elementor-frontend.js
1600 ms
jquery.validate.min.js
1599 ms
mailcheck.min.js
1642 ms
wpforms.js
1617 ms
fbevents.js
160 ms
gtm.js
105 ms
analytics.js
209 ms
woocommerceWidget.js
210 ms
loading-load2.gif
1630 ms
about-03-img-3.jpg
1615 ms
Untitled-4.jpg
347 ms
conversion_async.js
320 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
315 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
351 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
438 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
470 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
470 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
465 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
469 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
469 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
469 ms
fa-brands-400.woff
2262 ms
h14-layer-4.png
351 ms
h14-layer-1.png
348 ms
Untitled-9.jpg
462 ms
h14-layer-3.png
463 ms
img-icon-6.png
429 ms
fontawesome-webfont.woff
2149 ms
227258935877399
243 ms
smartic-icon-1.7.1.woff
2080 ms
3077b3fe40868bc55feff36c1.js
495 ms
js
281 ms
ec.js
139 ms
BROmny-Regular.woff
1670 ms
BROmny-Medium.woff
1911 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
192 ms
BROmny-SemiBold.woff
1985 ms
BROmny-Bold.woff
2105 ms
fa-solid-900.woff
2526 ms
eicons.woff
2574 ms
270 ms
531500901209239
275 ms
collect
42 ms
collect
163 ms
eicons.woff
2288 ms
feather.ttf
2051 ms
feather.ttf
2083 ms
vaata-new-logo.png
2277 ms
vaata-logo.png
3445 ms
vaata-banner-bg.png
2746 ms
43 ms
ga-audiences
32 ms
vaata-drytab-toilet-cleaner.png
2289 ms
drytab-handsfree-toilet-cleaner.png
2552 ms
4.png
4176 ms
5.png
3265 ms
drytab-product.png
6372 ms
drytab-for-a-sparkling-toilets.png
2553 ms
vaata-leaf.png
2815 ms
drytab-drain-the-tank.png
2783 ms
vaata-drop-drytab.png
3015 ms
vaata-drytab-ensure-water-level.png
3036 ms
vaata-drytab-ready-to-use.jpg
3234 ms
82 ms
vaata-drytab-toilet-cleaner-use.jpg
3036 ms
drytab-automatic-toilet-cleaning-system-p8f8t884guzz2jiws78jnw0xluljt0qt448vnu4i1k.png
3269 ms
delete-sign.png
3038 ms
h14-layer-4.png
3674 ms
chandrakant-mandlik-pune.jpg
3474 ms
18 ms
ks-rajan-chennai.jpg
3298 ms
vijay-chodan-goa.jpg
3277 ms
rajeev-delhi.jpg
3695 ms
vaata.com
4152 ms
pranav-secunderabad.jpg
3653 ms
harshad-taki-mumbai.jpg
3451 ms
rajendra-babu-mumbai.jpg
3005 ms
vijay-delhi.jpg
3238 ms
mirdul-pune.jpg
3207 ms
prabish-kumar-secunderabad.jpg
3451 ms
padbhanaban-banglore.jpg
3591 ms
Noida.jpg
3460 ms
Warangal.jpg
3477 ms
delhi1.jpg
3186 ms
Bangalore-two.jpg
3540 ms
Bangalore-one1.jpg
3459 ms
chandru-manohar-coimbatore.png
3472 ms
bala-chennai.png
3705 ms
vaata.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
vaata.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
vaata.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vaata.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 Vaata.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.
vaata.com
Open Graph data is detected on the main page of VAATA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: