Tools & Wizards About Us
urbankissan.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

urbankissan.com

Buy Healthy Food | Hydroponics | Farming | Local Farm | Sustainability

Page Load Speed

9.6 sec in total

First Response

39 ms

Resources Loaded

6.2 sec

Page Rendered

3.3 sec

urbankissan.com screenshot

About Website

Click here to check amazing Urbankissan content. Otherwise, check out these important facts you probably never knew about urbankissan.com

Now you can shop pesticide free fruits and vegetables and farm bowls filled with nutrients online at UrbanKisaan. Also get into home-farming with our Exclusive homekits.

Visit urbankissan.com

Key Findings

We analyzed Urbankissan.com page load time and found that the first response time was 39 ms and then it took 9.5 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

urbankissan.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value31.9 s

0/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value910 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value31.5 s

0/100

10%

Network Requests Diagram

urbankissan.com

39 ms

www.urbankisaan.com

1087 ms

styles.3d2081a58cd23a3a56c5.css

26 ms

js

127 ms

runtime-es2015.afa70d10a94fdb18c3fc.js

100 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Urbankissan.com, 76% (74 requests) were made to Urbankisaan.com and 4% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Urbankisaan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 205.3 kB (3%)

Content Size

7.5 MB

After Optimization

7.3 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Urbankissan.com main page is 7.5 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.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 123.9 kB

  • Original 151.2 kB
  • After minification 151.0 kB
  • After compression 27.2 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 123.9 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 81.1 kB

  • Original 7.2 MB
  • After minification 7.1 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. Urbankissan images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 328 B

  • Original 120.2 kB
  • After minification 120.2 kB
  • After compression 119.8 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.

Requests Breakdown

Number of requests can be reduced by 66 (70%)

Requests Now

94

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

urbankissan.com

urbankissan.com

39 ms

www.urbankisaan.com

www.urbankisaan.com

1087 ms

styles.3d2081a58cd23a3a56c5.css

styles.3d2081a58cd23a3a56c5.css

26 ms

js

js

127 ms

runtime-es2015.afa70d10a94fdb18c3fc.js

runtime-es2015.afa70d10a94fdb18c3fc.js

100 ms

runtime-es5.afa70d10a94fdb18c3fc.js

runtime-es5.afa70d10a94fdb18c3fc.js

403 ms

polyfills-es5.8eb5ad8b2358e9d2d48c.js

polyfills-es5.8eb5ad8b2358e9d2d48c.js

636 ms

polyfills-es2015.4a4a119a4abf4ecfbb60.js

polyfills-es2015.4a4a119a4abf4ecfbb60.js

43 ms

main-es2015.06ae78cf053f02f2c02a.js

main-es2015.06ae78cf053f02f2c02a.js

178 ms

main-es5.06ae78cf053f02f2c02a.js

main-es5.06ae78cf053f02f2c02a.js

1031 ms

v84a3a4012de94ce1a686ba8c167c359c1696973893317

v84a3a4012de94ce1a686ba8c167c359c1696973893317

107 ms

play.svg

play.svg

55 ms

r1.jpg

r1.jpg

96 ms

r2.jpg

r2.jpg

97 ms

r3.jpg

r3.jpg

98 ms

s1.jpg

s1.jpg

116 ms

arrow-right-2.svg

arrow-right-2.svg

113 ms

tech.png

tech.png

178 ms

n1.JPG

n1.JPG

179 ms

discovery.png

discovery.png

619 ms

n2.jpg

n2.jpg

240 ms

forbes.png

forbes.png

236 ms

n3.jpg

n3.jpg

245 ms

footer_logo.png

footer_logo.png

243 ms

fbevents.js

fbevents.js

29 ms

qevents.js

qevents.js

59 ms

banner.jpg

banner.jpg

1396 ms

facebook.svg

facebook.svg

271 ms

twitter.svg

twitter.svg

273 ms

instagram.svg

instagram.svg

285 ms

youtube.svg

youtube.svg

298 ms

pixel

pixel

16 ms

platform.js

platform.js

270 ms

sdk.js

sdk.js

209 ms

362c91cb65c2498daf089231f47ae1b0.js

362c91cb65c2498daf089231f47ae1b0.js

257 ms

pixel

pixel

121 ms

gtm.js

gtm.js

208 ms

ns.html

ns.html

206 ms

25-es5.ee12dd3d30d2e33ccf74.js

25-es5.ee12dd3d30d2e33ccf74.js

485 ms

26-es5.0a616e6e111856359a3e.js

26-es5.0a616e6e111856359a3e.js

520 ms

2-es5.19b580dc3fc21df9823a.js

2-es5.19b580dc3fc21df9823a.js

659 ms

3-es5.f1d8e2180275d5f5db42.js

3-es5.f1d8e2180275d5f5db42.js

494 ms

31-es5.98459b7b50827b670a18.js

31-es5.98459b7b50827b670a18.js

658 ms

32-es5.30d8922ede89dbd76094.js

32-es5.30d8922ede89dbd76094.js

492 ms

27-es5.bcc01a610a396f2b2ea3.js

27-es5.bcc01a610a396f2b2ea3.js

884 ms

common-es5.1faeefb7c761e204278a.js

common-es5.1faeefb7c761e204278a.js

896 ms

23-es5.f793e0cfa358c02f4c90.js

23-es5.f793e0cfa358c02f4c90.js

988 ms

22-es5.43c12debe9e2d47407fd.js

22-es5.43c12debe9e2d47407fd.js

901 ms

8-es5.2d890255b7307c12fbc1.js

8-es5.2d890255b7307c12fbc1.js

980 ms

30-es5.248d3a368ed081664a96.js

30-es5.248d3a368ed081664a96.js

1066 ms

35-es5.3ba5731dd49d9a80a46a.js

35-es5.3ba5731dd49d9a80a46a.js

1265 ms

37-es5.82c54228ecf638050942.js

37-es5.82c54228ecf638050942.js

1290 ms

36-es5.9a95f4ad43a76b218938.js

36-es5.9a95f4ad43a76b218938.js

1296 ms

39-es5.2dbe53384009d7fc7b49.js

39-es5.2dbe53384009d7fc7b49.js

1349 ms

44-es5.f15cdf08dbeb322ccf74.js

44-es5.f15cdf08dbeb322ccf74.js

1380 ms

43-es5.013043b630595148ce06.js

43-es5.013043b630595148ce06.js

1447 ms

45-es5.2d6613de9a9437d717c1.js

45-es5.2d6613de9a9437d717c1.js

1670 ms

46-es5.68256718c09a7231e656.js

46-es5.68256718c09a7231e656.js

1711 ms

28-es5.ed3dcdb1810cf33451f2.js

28-es5.ed3dcdb1810cf33451f2.js

1683 ms

11-es5.bf468a4682e251364ce9.js

11-es5.bf468a4682e251364ce9.js

1868 ms

12-es5.6fbb59dd79ba3d8241e0.js

12-es5.6fbb59dd79ba3d8241e0.js

1775 ms

10-es5.8baf14f1745d16d16337.js

10-es5.8baf14f1745d16d16337.js

1832 ms

29-es5.ae0e52ac5c006b060134.js

29-es5.ae0e52ac5c006b060134.js

2086 ms

42-es5.4e33616c300845e593f3.js

42-es5.4e33616c300845e593f3.js

2069 ms

40-es5.4b02d35e5506007d029d.js

40-es5.4b02d35e5506007d029d.js

2098 ms

47-es5.ce13860a84fc8535ae12.js

47-es5.ce13860a84fc8535ae12.js

2188 ms

34-es5.e799eb929b3583955188.js

34-es5.e799eb929b3583955188.js

2217 ms

38-es5.5587f4fbfa6e5c505edf.js

38-es5.5587f4fbfa6e5c505edf.js

2259 ms

41-es5.092c64a2e8d1a1e22b8c.js

41-es5.092c64a2e8d1a1e22b8c.js

2441 ms

33-es5.66368d026cf5320029b3.js

33-es5.66368d026cf5320029b3.js

2479 ms

13-es5.d3823ad2a01139a40809.js

13-es5.d3823ad2a01139a40809.js

2487 ms

19-es5.42723b458942a3e0407b.js

19-es5.42723b458942a3e0407b.js

2618 ms

18-es5.9c909e522f1c33a6737f.js

18-es5.9c909e522f1c33a6737f.js

2663 ms

14-es5.94ee86882cb09479c978.js

14-es5.94ee86882cb09479c978.js

2678 ms

sdk.js

sdk.js

17 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

8 ms

iframe

iframe

296 ms

analytics.js

analytics.js

31 ms

collect

collect

14 ms

collect

collect

17 ms

js

js

100 ms

ga-audiences

ga-audiences

41 ms

15-es5.7de7267cc2c58a4ff279.js

15-es5.7de7267cc2c58a4ff279.js

2441 ms

17-es5.62bd3de2a54c784d8252.js

17-es5.62bd3de2a54c784d8252.js

2385 ms

16-es5.0850fb2c9eabccc83c7b.js

16-es5.0850fb2c9eabccc83c7b.js

2401 ms

m=base

m=base

26 ms

9-es5.30f7250cc96cb4da9424.js

9-es5.30f7250cc96cb4da9424.js

2614 ms

iframerpc

iframerpc

193 ms

21-es5.f91244d85b3eebeb6472.js

21-es5.f91244d85b3eebeb6472.js

2558 ms

20-es5.b00bf56a2a89349b5e42.js

20-es5.b00bf56a2a89349b5e42.js

2509 ms

24-es5.46a9692f2f1938299a0e.js

24-es5.46a9692f2f1938299a0e.js

2393 ms

banner.8e5b5482c3ddd9c0ff91.jpg

banner.8e5b5482c3ddd9c0ff91.jpg

2769 ms

facebook.svg

facebook.svg

2037 ms

twitter.svg

twitter.svg

1972 ms

instagram.svg

instagram.svg

2349 ms

youtube.svg

youtube.svg

2084 ms

collect

collect

4 ms

Accessibility Review

urbankissan.com accessibility score

53

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

Form elements do not have associated labels

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

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

urbankissan.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

urbankissan.com SEO score

85

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

Links do not have descriptive text

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

urbankissan.com

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