Tools & Wizards About Us
towness.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

towness.com

Towness - Foodie Friendly Online Vegetables and Grocery Shopping in Bangalore

Page Load Speed

6.2 sec in total

First Response

1.5 sec

Resources Loaded

4.4 sec

Page Rendered

347 ms

towness.com screenshot

About Website

Welcome to towness.com homepage info - get ready to check Towness best content right away, or after learning these important things about towness.com

Online grocery and Vegetable shop and supermarket in Bangalore. Buy Vegetables, Grocery, household items, Organic Vegetables, Organic Pulses, Dal Online. Home Delivery. Towness online shopping store.

Visit towness.com

Key Findings

We analyzed Towness.com page load time and found that the first response time was 1.5 sec and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

towness.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.6 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.8 s

10/100

10%

Network Requests Diagram

towness.com

1458 ms

home.php

649 ms

_a2a3279ead3507d04ead43bf468a93fb.css

240 ms

_d58533438d9a1def342d5e7732cccf7e.js

399 ms

jquery.bxslider.css

182 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Towness.com, 72% (51 requests) were made to Towness.co.in and 6% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Towness.co.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 847.3 kB (48%)

Content Size

1.8 MB

After Optimization

927.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Towness.com main page is 1.8 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. 65% of websites need less resources to load. Javascripts take 781.4 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 69.5 kB

  • Original 88.2 kB
  • After minification 74.8 kB
  • After compression 18.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. This page needs HTML code to be minified as it can gain 13.4 kB, which is 15% 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 69.5 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 30.6 kB

  • Original 654.7 kB
  • After minification 624.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. Towness images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 529.2 kB

  • Original 781.4 kB
  • After minification 713.6 kB
  • After compression 252.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 529.2 kB or 68% of the original size.

CSS Optimization

-87%

Potential reduce by 218.0 kB

  • Original 250.6 kB
  • After minification 195.6 kB
  • After compression 32.6 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. Towness.com needs all CSS files to be minified and compressed as it can save up to 218.0 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (37%)

Requests Now

67

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Towness. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

towness.com

towness.com

1458 ms

home.php

home.php

649 ms

_a2a3279ead3507d04ead43bf468a93fb.css

_a2a3279ead3507d04ead43bf468a93fb.css

240 ms

_d58533438d9a1def342d5e7732cccf7e.js

_d58533438d9a1def342d5e7732cccf7e.js

399 ms

jquery.bxslider.css

jquery.bxslider.css

182 ms

fadeslideshow.js

fadeslideshow.js

203 ms

jquery-1.8.0.min.js

jquery-1.8.0.min.js

306 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

255 ms

jquery.confirm.js

jquery.confirm.js

256 ms

func.js

func.js

256 ms

classic-081711.css

classic-081711.css

18 ms

mc-validate.js

mc-validate.js

39 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

345 ms

jquery.mCustomScrollbar.concat.min.js

jquery.mCustomScrollbar.concat.min.js

346 ms

conversion.js

conversion.js

13 ms

_4ed148dca724c5ce1bf6742b9721a577.js

_4ed148dca724c5ce1bf6742b9721a577.js

416 ms

mm_tmon_script.php

mm_tmon_script.php

102 ms

spacer.gif

spacer.gif

202 ms

banner_offers1.jpg

banner_offers1.jpg

558 ms

malabar_coffee.jpg

malabar_coffee.jpg

580 ms

organic_vegetables_delivery_banner.jpg

organic_vegetables_delivery_banner.jpg

302 ms

no_preservatives.jpg

no_preservatives.jpg

301 ms

weekly_recommendations_1.jpg

weekly_recommendations_1.jpg

556 ms

weekly_recommendations_2.jpg

weekly_recommendations_2.jpg

559 ms

DSCF1148-02.jpg

DSCF1148-02.jpg

1208 ms

ginger_thokku.jpg

ginger_thokku.jpg

653 ms

australiangrapes.jpg

australiangrapes.jpg

642 ms

cta_green_drop.png

cta_green_drop.png

651 ms

cta_cutoff_time.png

cta_cutoff_time.png

652 ms

cta_crdit_card.png

cta_crdit_card.png

711 ms

cta_free_food_hamper.png

cta_free_food_hamper.png

798 ms

cta_refer_friend.png

cta_refer_friend.png

816 ms

cta_jaldi_healthy.png

cta_jaldi_healthy.png

817 ms

cta_post_recipe.png

cta_post_recipe.png

829 ms

cta_food_coupon.png

cta_food_coupon.png

1206 ms

cta_special_offers.png

cta_special_offers.png

1205 ms

prepaid_customers.png

prepaid_customers.png

1283 ms

at-twitter_normal.png

at-twitter_normal.png

1280 ms

new_icon.png

new_icon.png

1298 ms

logo.png

logo.png

1454 ms

banner.png

banner.png

1381 ms

email_icon_small.gif

email_icon_small.gif

1397 ms

Mobile_phone_icon_small.gif

Mobile_phone_icon_small.gif

1449 ms

link_foodie_corner.png

link_foodie_corner.png

1452 ms

link_wholesale.png

link_wholesale.png

1469 ms

search_loading.gif

search_loading.gif

1564 ms

sdk.js

sdk.js

197 ms

ga.js

ga.js

41 ms

bg_header.jpg

bg_header.jpg

1568 ms

bg_gift.png

bg_gift.png

1571 ms

dingbats_orders.gif

dingbats_orders.gif

1578 ms

__utm.gif

__utm.gif

19 ms

plus_minus.gif

plus_minus.gif

1503 ms

button_search.gif

button_search.gif

1515 ms

Roboto-Regular-webfont.woff

Roboto-Regular-webfont.woff

1641 ms

social_links.png

social_links.png

1537 ms

widget_v2.134.js

widget_v2.134.js

91 ms

analytics.js

analytics.js

84 ms

321 ms

194 ms

collect

collect

25 ms

bx_loader.gif

bx_loader.gif

1250 ms

controls.png

controls.png

1248 ms

42 ms

xd_arbiter.php

xd_arbiter.php

133 ms

xd_arbiter.php

xd_arbiter.php

255 ms

like.php

like.php

78 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

620 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

654 ms

avatar_simple_visitor.png

avatar_simple_visitor.png

70 ms

aL63HcygAAVYuCCsAAA==

aL63HcygAAVYuCCsAAA==

0 ms

Accessibility Review

towness.com accessibility score

100

Accessibility Issues

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

towness.com SEO score

83

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

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Towness.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 Towness.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

towness.com

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