6.2 sec in total
420 ms
5.1 sec
635 ms
Welcome to mydukaan.io homepage info - get ready to check My Dukaan best content for India right away, or after learning these important things about mydukaan.io
Try Dukaan, the cutting-edge enterprise ecommerce platform. Seamlessly manage your online business and drive growth with our powerful tools.
Visit mydukaan.ioWe analyzed Mydukaan.io page load time and found that the first response time was 420 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
mydukaan.io performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value23.5 s
0/100
25%
Value12.6 s
3/100
10%
Value1,430 ms
15/100
30%
Value0.091
92/100
15%
Value19.2 s
2/100
10%
420 ms
1320 ms
131 ms
183 ms
252 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 86% of them (59 requests) were addressed to the original Mydukaan.io, 7% (5 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Mydukaan.io.
Page size can be reduced by 299.8 kB (28%)
1.1 MB
783.3 kB
In fact, the total size of Mydukaan.io main page is 1.1 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. 50% of websites need less resources to load. Javascripts take 544.6 kB which makes up the majority of the site volume.
Potential reduce by 179.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. 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 179.6 kB or 75% of the original size.
Potential reduce by 0 B
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. My Dukaan images are well optimized though.
Potential reduce by 100.0 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 100.0 kB or 18% of the original size.
Potential reduce by 20.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. Mydukaan.io needs all CSS files to be minified and compressed as it can save up to 20.2 kB or 23% of the original size.
Number of requests can be reduced by 28 (45%)
62
34
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Dukaan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and as a result speed up the page load time.
mydukaan.io
420 ms
mydukaan.io
1320 ms
gtm.js
131 ms
js
183 ms
js
252 ms
animate.min.css
33 ms
c38a4d51b4fbd80da7bd.css
854 ms
6438a53150fd7bafd582.css
884 ms
hero_image_shadow-new-ef38d2da7a63bb815162083389e05f32.webp
2736 ms
wow-e6238cc10380aaff6bbf0847c1d341e1.svg
701 ms
healthxp-5ef279d7f5d8a34f50bbd9d4d86091e2.svg
1095 ms
lemonade-875990583808ba3dca93f8caaf1ffddc.svg
767 ms
uppercase-f225d6aa2bf2a3ff7bee2e2f7c352fb2.svg
787 ms
truke-ecee96a2de057adaede46531a80f1d9d.svg
1043 ms
launch-fast-6349265d2de0cf16e61e160f85bd681d.svg
807 ms
scale-faster-615089c61891323e0c2e2f0a4d498d53.svg
1007 ms
manage-better-5f03835fb0602b9fa6a4b3fc98bc9c7c.svg
1362 ms
tinker-0b59397a813a30dccbf17d9278372824.webp
1121 ms
ursa-047137008aa0cf119dc1a54047b7fd87.png
1479 ms
enigma-b98c9aff293be1a8103e3f5bf15682e7.png
1596 ms
mana-3d58c03ccebc3fb7ccd5e1035aca044c.webp
1388 ms
nirvana-0d20aed96a17d45b4de7df85875d5731.webp
1431 ms
oxford-3d6756d13f284e6d6205f8c607355ca0.webp
1602 ms
lemonade-logo-a6e4ca9cdec5ed18e1494d37621d47c1.svg
1612 ms
emo-bois-logo-9aa3c940d8866ed84b3ea0aadcf93deb.svg
1789 ms
polyfills-95036aead0e634c0c881.js
1633 ms
webpack-d5abd492e43aace273ff.js
1702 ms
framework.4ceb3e29f1c4f90f6fdf.js
1833 ms
commons.4af1bf667ec82200c041.js
1760 ms
main-b81e4ec47cfb7d0671d2.js
1848 ms
ea88be26.e308dd00bb131f0937f2.js
2224 ms
02679c23e6623e519c5fdff9b07cd29ad5f86ba1.d20cb32e766bf20e3f59.js
1912 ms
ec45683493eef25f03dc06424382a2bce488491a.df613adb459e31388950.js
2015 ms
02c74fd01b92b28e09ecf706321ad3c0c6aca670.c8601bb666fa0f4569f1.js
2039 ms
0e0c8f429fc7b1a29b6b7383c4c3831d25c97c6e.53e68a95886a9ac2b442.js
2059 ms
f3ca3d0c28100e0a367b6191468b08ed38b14a14.20a668c408cf0c08524f.js
2117 ms
cd054f915006ad7eb5ca5b96d55c1d71ebc2d437.779d45800e4d55e4e7ee.js
2232 ms
_app-5a37d7b1eba730758537.js
2257 ms
a653b67e563ac8b4094b06402c40f5e618e9fdb9.abb47ae9999eccedc784.js
2313 ms
f9066a76106e864f103a3c6315abb12cb22abd72.8291d129c3b1f3a2e2c3.js
2337 ms
6bae642ae9a139314d99b35a734e104c1cca3fa3.a95c2117638988bc9133.js
2435 ms
bot.js
43 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDNp8w.woff
111 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTBjNp8w.woff
139 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT6jRp8w.woff
164 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT0zRp8w.woff
183 ms
k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTtDRp8w.woff
209 ms
3445a953f2452c95e5433705926b9a00d3478dff_CSS.ddce25b62cf34b951439.js
2433 ms
eda2bf11d572bdf44a9e79766dc2e9ecd55aae68.f45ae1e252bc7cad8978.js
2022 ms
25c4c7968b1bc1d94b6f2d4428cdf9bd33e4d633.6c2b02afcd465021a0c4.js
2017 ms
da394473313220f0486d32e099c93e7f348ef600.cd59255e488407645b9a.js
1943 ms
2f7ac05545f8793df49baf496f0980023a56fb9e.1539886754c3ff28a411.js
2019 ms
7b0b89d7369e2c5924792f2a3e3197864397c43f.041b2fe77849bfa607e8.js
1964 ms
index-5d44ac278faeddade8b7.js
2203 ms
_buildManifest.js
1830 ms
_ssgManifest.js
1821 ms
wow-logo-506ff91f087f4f6e6a04217a2adcd7a6.svg
1807 ms
jain-shikanji-logo-d7dbdda1421fcf8bd1b1d11ab2b63f2b.svg
1843 ms
banner-home-main.ebd707dd321420dd97b2e08e0aa39020.webp
1683 ms
star-purple.3a0f99650c0ab639cf633cf46e9a29ae.svg
1664 ms
star-blue.f616f6970481413e436c6ec2ad621545.svg
1610 ms
star-gray.1f0c906d374a9e78df3310d226fb00d9.svg
1584 ms
vector-left.0051142329353632f8a8d25e3422b061.webp
1651 ms
rectangle-left.6b7999eecc154d8c005ae9e0ae8f3474.svg
1625 ms
rectangle-right.b572e7cb5d77acf9d4d32932676f08cc.svg
1623 ms
star.37fd9fafbd38e4ad75cceef41c13cd77.webp
1556 ms
banner-bg-grid.9316afcddfcb78d705d0f20c456dd4be.svg
1469 ms
tick.a3071874e4031049b0416759d5684d25.svg
1455 ms
start-selling-online.b1df8e79dc95ace9c62e9326dbd36ebd.webp
1621 ms
mydukaan.io 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
<frame> or <iframe> elements do not have a title
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
mydukaan.io 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
mydukaan.io 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
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mydukaan.io 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 Mydukaan.io 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.
mydukaan.io
Open Graph description is not detected on the main page of My Dukaan. 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: