4.1 sec in total
363 ms
3.2 sec
581 ms
Click here to check amazing Doozy content. Otherwise, check out these important facts you probably never knew about doozy.co.in
Make Your Home Smart Home Control, Monitor and Secure your home with your smart phone from any where.. learn more Watch Demo Doozy security solutions Leading CCTV suppliers in Rayalaseema. All variant...
Visit doozy.co.inWe analyzed Doozy.co.in page load time and found that the first response time was 363 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
doozy.co.in performance score
name
value
score
weighting
Value8.3 s
0/100
10%
Value31.5 s
0/100
25%
Value18.0 s
0/100
10%
Value3,090 ms
2/100
30%
Value0
100/100
15%
Value44.3 s
0/100
10%
363 ms
126 ms
184 ms
195 ms
128 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 81% of them (104 requests) were addressed to the original Doozy.co.in, 14% (18 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Doozy.co.in.
Page size can be reduced by 495.9 kB (11%)
4.5 MB
4.0 MB
In fact, the total size of Doozy.co.in main page is 4.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. 80% 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 3.2 MB which makes up the majority of the site volume.
Potential reduce by 142.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 142.2 kB or 83% of the original size.
Potential reduce by 29.5 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. Doozy images are well optimized though.
Potential reduce by 163.3 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 163.3 kB or 21% of the original size.
Potential reduce by 160.9 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. Doozy.co.in needs all CSS files to be minified and compressed as it can save up to 160.9 kB or 48% of the original size.
Number of requests can be reduced by 82 (76%)
108
26
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doozy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 64 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.doozy.co.in
363 ms
woocommerce-layout.css
126 ms
woocommerce.css
184 ms
base.css
195 ms
auxin-icon.css
128 ms
main.css
308 ms
elementor-icons.min.css
175 ms
frontend.min.css
256 ms
swiper.min.css
192 ms
post-108.css
241 ms
elementor.css
247 ms
elementor-widgets.css
261 ms
mediaelementplayer-legacy.min.css
261 ms
wp-mediaelement.min.css
306 ms
post-101.css
343 ms
custom.css
343 ms
post-68.css
347 ms
post-236.css
345 ms
css
47 ms
wp-polyfill-inert.min.js
371 ms
regenerator-runtime.min.js
369 ms
wp-polyfill.min.js
440 ms
hooks.min.js
383 ms
w.js
33 ms
jquery.min.js
454 ms
jquery-migrate.min.js
386 ms
jquery.blockUI.min.js
434 ms
add-to-cart.min.js
434 ms
js.cookie.min.js
466 ms
woocommerce.min.js
467 ms
js
64 ms
modernizr-custom.min.js
504 ms
wc-blocks.css
401 ms
imagesloaded.min.js
400 ms
masonry.min.js
550 ms
plugins.min.js
788 ms
scripts.min.js
570 ms
widgets.js
571 ms
mediaelement-and-player.min.js
645 ms
mediaelement-migrate.min.js
568 ms
wp-mediaelement.min.js
555 ms
plugins.min.js
628 ms
scripts.js
581 ms
sourcebuster.min.js
571 ms
order-attribution.min.js
563 ms
react.min.js
638 ms
deprecated.min.js
599 ms
dom.min.js
592 ms
react-dom.min.js
633 ms
escape-html.min.js
599 ms
element.min.js
632 ms
is-shallow-equal.min.js
589 ms
i18n.min.js
552 ms
keycodes.min.js
550 ms
priority-queue.min.js
611 ms
compose.min.js
605 ms
private-apis.min.js
605 ms
redux-routine.min.js
586 ms
data.min.js
586 ms
lodash.min.js
576 ms
wc-blocks-registry.js
622 ms
url.min.js
582 ms
api-fetch.min.js
580 ms
g.gif
33 ms
wc-settings.js
562 ms
data-controls.min.js
549 ms
html-entities.min.js
558 ms
notices.min.js
587 ms
js
177 ms
analytics.js
172 ms
wc-blocks-middleware.js
578 ms
wc-blocks-data.js
581 ms
dom-ready.min.js
428 ms
a11y.min.js
412 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
84 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
99 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
99 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
100 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
150 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
150 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
153 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
153 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
152 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
154 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
154 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
157 ms
pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf
155 ms
pxiGyp8kv8JHgFVrLPTucHtF.ttf
155 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
156 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
158 ms
pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf
159 ms
pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf
158 ms
primitives.min.js
419 ms
warning.min.js
466 ms
blocks-components.js
483 ms
blocks-checkout.js
480 ms
collect
89 ms
order-attribution-blocks.min.js
400 ms
custom.js
403 ms
webpack.runtime.min.js
411 ms
frontend-modules.min.js
467 ms
waypoints.min.js
467 ms
core.min.js
390 ms
frontend.min.js
393 ms
auxin-front.woff
480 ms
cropped-doozy-1028-x-400-copy-1.png
342 ms
doozy-1028-x-400-copy.png
392 ms
downarrow.svg
395 ms
empty-cart.svg
399 ms
smart-home-banner-img.gif
630 ms
1422514191__1-1-1400x720.png
542 ms
dsafads-e1595410702912.png
451 ms
dsafads-1-e1595410744952.png
454 ms
zebra-services-gif.gif
685 ms
tk800-right30-2-e1595334680134-600x420.png
551 ms
JBL_Bar_2.1_Black_Hero_1605x1605px-1-e1612704985331.png
681 ms
DS-KIS202.png.thumb_.1280.1280-e1595397872498-1200x600.png
631 ms
Digital_Door_Locks_Integration__Yale__Samsung.png
566 ms
ds-pwa32-ng-1-e1595331942938-600x312.png
573 ms
promo-box_UPS-Amplon-Family_mobile-600x350.png
577 ms
noun_delivery_1095359-1.svg
584 ms
noun_guarantee_952398-1.svg
628 ms
Group-995-1.svg
644 ms
noun_Wallet_745515-1.svg
642 ms
yH5BAEAAAAALAAAAAABAAEAAAIBRAA7
1589 ms
cropped-doozy-1028-x-400-copy-1-150x60.png
627 ms
doozy-1028-x-400-copy-150x60.png
624 ms
symbols.svg
451 ms
woocommerce-smallscreen.css
68 ms
doozy.co.in accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
doozy.co.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
doozy.co.in SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Links do not have descriptive text
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
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 Doozy.co.in 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 Doozy.co.in 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.
doozy.co.in
Open Graph description is not detected on the main page of Doozy. 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: