1.9 sec in total
506 ms
1.2 sec
187 ms
Visit libazaar.in now to see the best up-to-date Libazaar content for India and also check out these interesting facts you probably never knew about libazaar.in
Get lowest price online shopping India and up to 10% cash back shopping website Libazaar.com, 100% money back Your store of fun
Visit libazaar.inWe analyzed Libazaar.in page load time and found that the first response time was 506 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
libazaar.in performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value3.3 s
68/100
25%
Value3.5 s
89/100
10%
Value2,080 ms
7/100
30%
Value0
100/100
15%
Value5.0 s
76/100
10%
506 ms
189 ms
137 ms
136 ms
26 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 84% of them (56 requests) were addressed to the original Libazaar.in, 6% (4 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (506 ms) belongs to the original domain Libazaar.in.
Page size can be reduced by 71.6 kB (71%)
101.5 kB
29.9 kB
In fact, the total size of Libazaar.in main page is 101.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 54.6 kB which makes up the majority of the site volume.
Potential reduce by 39.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 5.8 kB, which is 12% 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 39.6 kB or 84% of the original size.
Potential reduce by 32.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 32.0 kB or 59% of the original size.
Number of requests can be reduced by 27 (45%)
60
33
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Libazaar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
libazaar.in
506 ms
jquery-2.1.1.min.js
189 ms
bootstrap.min.js
137 ms
font-awesome.min.css
136 ms
css
26 ms
css
37 ms
stylesheet.css
213 ms
carousel.css
95 ms
custom.css
96 ms
bootstrap.min.css
255 ms
owl.carousel.css
137 ms
owl.transitions.css
171 ms
custom.js
169 ms
jstree.min.js
176 ms
carousel.min.js
212 ms
megnor.min.js
212 ms
jquery.custom.min.js
212 ms
scrolltop.min.js
216 ms
jquery.formalize.min.js
218 ms
common.js
245 ms
owl.carousel.min.js
273 ms
tabs.js
447 ms
analytics.js
22 ms
atrk.js
49 ms
collect
14 ms
atrk.gif
21 ms
test.png
225 ms
logo.png
50 ms
top-cms-sprite.png
63 ms
sprite.png
51 ms
contact-icon.png
51 ms
menu_3d_line.jpg
50 ms
caregory-arrow.png
120 ms
cate_h_arrow.png
90 ms
left_banner1-200x266.png
155 ms
mainbaner2-770x328.jpg
149 ms
upto.png
100 ms
easy.png
99 ms
delivery.png
123 ms
icon.png
131 ms
main-300x300-150x150.jpg
134 ms
main-150x150.jpg
160 ms
main-150x150.jpg
161 ms
main-150x150.jpg
173 ms
sub-banner2-368x99.png
180 ms
sub-banner3-368x99.png
184 ms
main-150x150.jpg
196 ms
main-150x150.jpg
196 ms
main-150x150.jpg
207 ms
main-150x150.jpg
210 ms
ajax-loader.gif
194 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
19 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
20 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
20 ms
fontawesome-webfont.woff
260 ms
1bg.jpg
192 ms
2bg.jpg
192 ms
3bg.jpg
200 ms
bg4.jpg
201 ms
glass.png
211 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
26 ms
about-_img.png
190 ms
social_sprite.png
188 ms
footer_icon.png
200 ms
pipe.png
199 ms
payment.png
208 ms
top_arrow.png
222 ms
libazaar.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
libazaar.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
libazaar.in 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
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Libazaar.in can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Libazaar.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.
libazaar.in
Open Graph description is not detected on the main page of Libazaar. 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: