4.6 sec in total
337 ms
3.1 sec
1.2 sec
Visit undezz.com now to see the best up-to-date Undezz content for India and also check out these interesting facts you probably never knew about undezz.com
Visit undezz.comWe analyzed Undezz.com page load time and found that the first response time was 337 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
undezz.com performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value2.4 s
91/100
25%
Value7.6 s
25/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value6.1 s
63/100
10%
337 ms
73 ms
144 ms
154 ms
155 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 84% of them (69 requests) were addressed to the original Undezz.com, 5% (4 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Undezz.com.
Page size can be reduced by 1.9 MB (15%)
12.7 MB
10.8 MB
In fact, the total size of Undezz.com main page is 12.7 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 11.4 MB which makes up the majority of the site volume.
Potential reduce by 33.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 33.2 kB or 79% of the original size.
Potential reduce by 798.1 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. Undezz images are well optimized though.
Potential reduce by 639.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 639.5 kB or 78% of the original size.
Potential reduce by 424.6 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. Undezz.com needs all CSS files to be minified and compressed as it can save up to 424.6 kB or 88% of the original size.
Number of requests can be reduced by 43 (58%)
74
31
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Undezz. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
undezz.com
337 ms
styles.css
73 ms
amlabel.css
144 ms
amscroll.css
154 ms
amshopby.css
155 ms
sociallogin.css
173 ms
prototype.js
514 ms
jquery-1.10.2.min.js
471 ms
noconflict.js
212 ms
ccard.js
228 ms
validation.js
304 ms
builder.js
256 ms
effects.js
353 ms
dragdrop.js
379 ms
controls.js
427 ms
slider.js
380 ms
js.js
424 ms
form.js
456 ms
translate.js
456 ms
cookies.js
494 ms
amlabel_observer.js
557 ms
amscroll.js
558 ms
modernizr.custom.min.js
559 ms
selectivizr.js
562 ms
matchMedia.js
564 ms
matchMedia.addListener.js
594 ms
enquire.js
596 ms
app.js
682 ms
jquery.cycle2.min.js
607 ms
jquery.cycle2.swipe.min.js
655 ms
slideshow.js
634 ms
imagesloaded.js
677 ms
minicart.js
680 ms
sociallogin.js
689 ms
css
33 ms
styles.css
988 ms
madisonisland.css
745 ms
font-awesome.min.css
33 ms
bootstrap.min.css
846 ms
main.css
791 ms
bootstrap.min.js
626 ms
swiper.js
617 ms
jssor.js
785 ms
jssor.slider.js
816 ms
analytics.js
25 ms
css
16 ms
flag.png
100 ms
sa.png
103 ms
kuwait.png
99 ms
logo.png
101 ms
1.png
527 ms
3.png
191 ms
4.jpg
190 ms
6.jpg
230 ms
2_1.png
344 ms
free.png
279 ms
trendy.png
285 ms
stylish.png
530 ms
newlook.png
523 ms
ucb.png
1680 ms
loungewear.png
647 ms
500off.png
524 ms
trends.png
693 ms
man.png
1200 ms
fb_icon.png
559 ms
tw_icon.png
611 ms
go_icon.png
615 ms
pi_icon.png
698 ms
yo_icon.png
695 ms
in_icon.png
718 ms
ins_icon.png
771 ms
collect
21 ms
undezz_sprite.png
730 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
15 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
49 ms
zJY4gsxBiSo5L7tNutxFNg.ttf
51 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
50 ms
fontawesome-webfont.woff
13 ms
back-top.png
694 ms
widget_v2.132.js
14 ms
avatar_simple_visitor.png
86 ms
aL63HcygAAVYuCCsAAA==
2 ms
undezz.com 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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
undezz.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
undezz.com SEO score
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
ZH
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Undezz.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Undezz.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.
undezz.com
Open Graph description is not detected on the main page of Undezz. 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: