22.6 sec in total
775 ms
21.5 sec
354 ms
Visit comedz.com now to see the best up-to-date Comedz content for India and also check out these interesting facts you probably never knew about comedz.com
Visit comedz.comWe analyzed Comedz.com page load time and found that the first response time was 775 ms and then it took 21.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
comedz.com performance score
775 ms
2206 ms
1690 ms
35 ms
40 ms
Our browser made a total of 125 requests to load all elements on the main page. We found that 67% of them (84 requests) were addressed to the original Comedz.com, 10% (13 requests) were made to Fonts.gstatic.com and 6% (7 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (10.5 sec) belongs to the original domain Comedz.com.
Page size can be reduced by 1.2 MB (48%)
2.5 MB
1.3 MB
In fact, the total size of Comedz.com main page is 2.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. 75% 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 947.5 kB which makes up the majority of the site volume.
Potential reduce by 112.5 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 21.8 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 112.5 kB or 78% of the original size.
Potential reduce by 37.9 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. Comedz images are well optimized though.
Potential reduce by 508.9 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 508.9 kB or 64% of the original size.
Potential reduce by 535.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. Comedz.com needs all CSS files to be minified and compressed as it can save up to 535.9 kB or 88% of the original size.
Number of requests can be reduced by 42 (42%)
99
57
The browser has sent 99 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Comedz. 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 29 to 1 for CSS and as a result speed up the page load time.
comedz.com
775 ms
www.comedz.com
2206 ms
www.comedz.com
1690 ms
font-awesome.min.css
35 ms
css
40 ms
css
51 ms
css
54 ms
font-awesome.css
771 ms
anim.css
778 ms
style.css
802 ms
mob2.css
796 ms
checkout.css
823 ms
innerproducts.css
1040 ms
hover.css
1526 ms
gh-buttons.css
1557 ms
style2.css
1595 ms
responsive.css
1597 ms
bootstrapcss.css
1886 ms
slidercss.css
1783 ms
jquery.min.js
38 ms
allpopup.js
2292 ms
simpleMobileMenu.js
2347 ms
ionicons.min.css
2347 ms
simpleMobileMenu.css
2391 ms
lightbox.min.css
2536 ms
ionic.min.css
63 ms
awesomplete.css
2709 ms
awesomplete.js
3040 ms
jquery-ui.min.js
40 ms
timeout-dialog.js
3130 ms
timeout-dialog.css
3144 ms
autojs.js
5252 ms
jquery-1.9.1.min.js
3548 ms
clients.js
3215 ms
bootstrap.min.js
3501 ms
jquery-easing-1.js
3600 ms
wow.min.js
3684 ms
css
13 ms
css
13 ms
000d657502539fcd65718797f766d4a9
500 ms
css
16 ms
css
19 ms
added.css
3440 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
109 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
115 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
108 ms
vzIUHo9z-oJ4WgkpPOtg1_esZW2xOQ-xsNqO47m55DA.woff
108 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
114 ms
mnpfi9pxYH-Go5UiibESIj8E0i7KZn-EPnyo3HZu7kw.woff
114 ms
analytics.js
114 ms
close.png
362 ms
loading.gif
754 ms
prev2.png
771 ms
next2.png
775 ms
tel.png
811 ms
logo.png
1079 ms
mob_cart.png
5363 ms
cart1_active.png
5444 ms
user_active.png
5445 ms
search_bg.png
5444 ms
fontawesome-webfont.woff
6428 ms
fontawesome-webfont.woff
48 ms
9k-RPmcnxYEPm8CNFsH2gg.woff
18 ms
KT3KS9Aol4WfR6Vas8kNcg.woff
18 ms
boeCNmOCCh-EWFLSfVffDg.woff
17 ms
wkfQbvfT_02e2IWO3yYueQ.woff
47 ms
BVtM30trf7q_jfqYeHfjtA.woff
47 ms
09537dff1aef3e972c97c8d014bb8da9.png
6469 ms
4b94e35f2217c6f96b3e648269f9744a.jpg
6863 ms
cf6bfe8dde3e84f29785cf9abfd2e97c.png
6909 ms
d931e78de1e8f328c283eb939772230f.png
6744 ms
89b3f1e5195675777386ea80d0582b10.png
7026 ms
b8eaee90b932e81d2a1559f962050a5a.png
8007 ms
m1.png
7248 ms
m2.png
7516 ms
m3.png
7657 ms
left_arrow.png
7702 ms
r_arrow.png
7781 ms
cad94b6baa323dcd990d11dda391e2e8.jpg
8282 ms
f0544f33dd53a80d4c770e6af25db0c3.jpg
8550 ms
d6ba22c0e003810ff017d34590c93d6f.jpg
8417 ms
1274cbb0a919c5c581d467851f362225.jpg
8759 ms
a90f32a4e307f1e60951d44252403357.jpg
8531 ms
479a840ea06220e1099f86c095aa3f34.jpg
8746 ms
7119f1122502d4569cc219bfb044bbde.jpg
9106 ms
94cc32df77bb449aeb72002a97b4f147.jpg
9227 ms
390ccbb10a44e4094ad567c279026ad5.jpg
9604 ms
ytqixbrv3xl.jpg
9916 ms
20sms2odpza.jpg
10064 ms
1d771633df3b550fac880cf8ea769469.jpg
10111 ms
367c1bd095905744038a19e6a7c0ab91.jpg
10403 ms
collect
14 ms
collect
44 ms
ga-audiences
32 ms
f6cc320d9e6e57027be6186afec71b1f.jpg
10228 ms
231aac60bb2251e0eeb06f40b0312711.jpg
10314 ms
543651306366bf6baa1d07875d00acff.jpg
10543 ms
process1.png
10192 ms
process2.png
10157 ms
process3.png
10143 ms
process4.png
6281 ms
UyYrYy3ltEffJV9QueSi4RdbPw3QSf9R-kE0EsQUn2A.woff
110 ms
Q_pTky3Sc3ubRibGToTAYiylde52zikAzebNtJS89aM.woff
111 ms
default
215 ms
icons.png
43 ms
emojione.min.css
36 ms
emojione.min.js
46 ms
1504706230866
249 ms
process5.png
6378 ms
ajax-loader.gif
86 ms
app1_1.png
6295 ms
app2_1.png
6354 ms
p1.png
6500 ms
ajax-loader-3.gif
27 ms
222 ms
197 ms
154 ms
v3
55 ms
p2.png
5555 ms
p3.png
5578 ms
p4.png
5723 ms
p5.png
5631 ms
CaptchaSecurityImages.php
5582 ms
disc1.png
5679 ms
icon_top.png
5470 ms
comedz.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 Comedz.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 Comedz.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.
comedz.com
Open Graph description is not detected on the main page of Comedz. 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: