9.9 sec in total
1.1 sec
8.4 sec
422 ms
Click here to check amazing Local Dookan content. Otherwise, check out these important facts you probably never knew about localdookan.com
A complete local online directory, related to product and service in your local city. Search product or services nearby you and contact directly.
Visit localdookan.comWe analyzed Localdookan.com page load time and found that the first response time was 1.1 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
localdookan.com performance score
1122 ms
186 ms
301 ms
949 ms
267 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 44% of them (63 requests) were addressed to the original Localdookan.com, 5% (7 requests) were made to M.media-amazon.com and 5% (7 requests) were made to Ws-in.amazon-adsystem.com. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Localdookan.com.
Page size can be reduced by 846.1 kB (37%)
2.3 MB
1.4 MB
In fact, the total size of Localdookan.com main page is 2.3 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 1.0 MB which makes up the majority of the site volume.
Potential reduce by 77.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. This page needs HTML code to be minified as it can gain 19.5 kB, which is 22% 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 77.6 kB or 87% of the original size.
Potential reduce by 45.0 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. Local Dookan images are well optimized though.
Potential reduce by 366.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 366.5 kB or 47% of the original size.
Potential reduce by 357.1 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. Localdookan.com needs all CSS files to be minified and compressed as it can save up to 357.1 kB or 84% of the original size.
Number of requests can be reduced by 72 (59%)
123
51
The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Local Dookan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
localdookan.com
1122 ms
adsbygoogle.js
186 ms
js
301 ms
animate.css
949 ms
bootstrap.min.css
267 ms
color.css
524 ms
main.css
782 ms
owl.carousel.min.css
518 ms
owl.theme.default.min.css
518 ms
plugins.css
1575 ms
reset.css
976 ms
style.css
980 ms
jquery.dataTables.min.css
1216 ms
responsive.dataTables.min.css
1247 ms
style4.css
1630 ms
Style2.css
1421 ms
css
266 ms
font-awesome.min.css
262 ms
js
279 ms
jquery-ui.css
264 ms
jquery-1.11.3.js
279 ms
jquery-1.7.1.min.js
1891 ms
jquery.validate.min.js
1928 ms
jquery.validate.unobtrusive.min.js
1765 ms
logo-1.png
2029 ms
2.jpg
2599 ms
show_ads_impl.js
55 ms
zrt_lookup.html
115 ms
1.jpg
2400 ms
2.jpg
2520 ms
3.jpg
2560 ms
1.png
2149 ms
2013.png
2367 ms
10.png
2593 ms
0.png
2750 ms
5.png
2751 ms
12.png
2861 ms
6.png
2991 ms
2012.png
3036 ms
9.png
3174 ms
1012.png
3253 ms
11.png
3254 ms
2.png
3374 ms
7.png
3533 ms
8.png
3550 ms
4.png
3552 ms
analytics.js
62 ms
cookie.js
125 ms
integrator.js
127 ms
ads
171 ms
osd.js
113 ms
collect
24 ms
bootstrap.min.js
18 ms
jquery-ui.js
18 ms
email-decode.min.js
3054 ms
jquery.min.js
3924 ms
plugins.js
4376 ms
scripts.js
3798 ms
css
17 ms
css
20 ms
megamenu.jquery.js
3392 ms
Navbar-hover.js
3303 ms
Navbar.js
3280 ms
css
23 ms
dataTables.responsive.min.js
3665 ms
jquery.dataTables.min.js
4103 ms
jssor.slider-27.1.0.min.js
4068 ms
bus.js
3340 ms
3.png
3304 ms
logo.png
4131 ms
mem8YaGs126MiZpBA-UFVZ0e.ttf
90 ms
mem5YaGs126MiZpBA-UNirkOUuhs.ttf
142 ms
mem5YaGs126MiZpBA-UN7rgOUuhs.ttf
98 ms
mem5YaGs126MiZpBA-UN8rsOUuhs.ttf
95 ms
glyphicons-halflings-regular.woff
26 ms
fontawesome-webfont.woff
201 ms
fontawesome-webfont.woff
3612 ms
q
533 ms
q
568 ms
q
596 ms
q
628 ms
q
563 ms
q
540 ms
q
958 ms
ads
489 ms
a-logo-amazon.png
297 ms
41LFYsbKSQL._AC_AC_SR98,95_.jpg
103 ms
json
571 ms
cart.gif
279 ms
41DwZuxPCaL._AC_AC_SR98,95_.jpg
126 ms
3131ktf-UTL._AC_AC_SR98,95_.jpg
126 ms
31pVse2NwVL._AC_AC_SR98,95_.jpg
126 ms
json
523 ms
json
522 ms
json
533 ms
31oT+P2jC4L._AC_AC_SR98,95_.jpg
97 ms
json
493 ms
120x240.gif
65 ms
5b703875bcfb7c023f15567f5d4aaa34.js
65 ms
f46201e292288f9eaedf043de53d96ab.js
77 ms
load_preloaded_resource.js
58 ms
0cfd2de5cd55ae7a979bc84095cabf2e.js
100 ms
abg_lite.js
66 ms
window_focus.js
92 ms
osd_listener.js
57 ms
qs_click_protection.js
181 ms
49249410939569adea952c0fe5df9779.js
181 ms
icon.png
114 ms
41Jy18-CakL._AC_AC_SR98,95_.jpg
115 ms
json
113 ms
B23595838.283830000;dc_trk_aid=477508022;dc_trk_cid=138586791;ord=1373898166;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;tfua=;gdpr=;gdpr_consent=
280 ms
s
70 ms
cookie_push_onload.html
90 ms
css
60 ms
dpixel
235 ms
usermatchredir
323 ms
trk
308 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
62 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
61 ms
BtfhbKJ-Y5RfiteF0SJrgrcmJB2_8an7Z4FyTQpfLrM.js
32 ms
usermatchredir
48 ms
pixel
44 ms
pixel
43 ms
pixel
42 ms
pixel
19 ms
pixel
20 ms
1.jpg
835 ms
2.jpg
836 ms
3.jpg
1019 ms
4.jpg
997 ms
5.jpg
836 ms
6.jpg
1377 ms
7.jpg
1393 ms
8.jpg
1613 ms
9.jpg
1716 ms
10.jpg
2320 ms
11.jpg
1872 ms
fontawesome-webfont.ttf
974 ms
common.js
7 ms
util.js
36 ms
AuthenticationService.Authenticate
13 ms
fontawesome-webfont.svg
457 ms
activeview
72 ms
sodar
195 ms
localdookan.com SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Localdookan.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Localdookan.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.
localdookan.com
Open Graph description is not detected on the main page of Local Dookan. 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: