7.4 sec in total
671 ms
6.4 sec
247 ms
Click here to check amazing L Zzie content for Singapore. Otherwise, check out these important facts you probably never knew about lzzie.com
Visit lzzie.comWe analyzed Lzzie.com page load time and found that the first response time was 671 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
lzzie.com performance score
name
value
score
weighting
Value10.0 s
0/100
10%
Value12.6 s
0/100
25%
Value19.2 s
0/100
10%
Value1,990 ms
8/100
30%
Value0.642
9/100
15%
Value40.7 s
0/100
10%
671 ms
23 ms
33 ms
41 ms
854 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 8% of them (8 requests) were addressed to the original Lzzie.com, 32% (33 requests) were made to Scontent.cdninstagram.com and 31% (32 requests) were made to Cdn.lzzie.com. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Cdn.lzzie.com.
Page size can be reduced by 1.3 MB (23%)
5.9 MB
4.6 MB
In fact, the total size of Lzzie.com main page is 5.9 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. 85% 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 5.0 MB which makes up the majority of the site volume.
Potential reduce by 36.7 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 36.7 kB or 81% of the original size.
Potential reduce by 686.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. Obviously, L Zzie needs image optimization as it can save up to 686.1 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 440.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 440.0 kB or 70% of the original size.
Potential reduce by 169.4 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. Lzzie.com needs all CSS files to be minified and compressed as it can save up to 169.4 kB or 81% of the original size.
Number of requests can be reduced by 43 (44%)
98
55
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of L Zzie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
www.lzzie.com
671 ms
css
23 ms
css
33 ms
css
41 ms
cdn_css_http_8de6e88bc4c594a43a0ec533b26d2d3e.css
854 ms
js_32417ba408ebbed1d66ae99ae354cd2b.js
1613 ms
homepage_week_19_2015-01.jpg
1211 ms
634 ms
logo.png
611 ms
search1.png
612 ms
web-banner-v2.jpg
629 ms
banner_0.jpg
613 ms
banner.jpg
636 ms
lzzie_bannerjanlittlelz_2000x1000.jpg
631 ms
square-banner-v2.jpg
612 ms
instagram-cny-lookbook.jpg
611 ms
lzzie_insta_qiuqiubanner.jpg
632 ms
lzzie_janlittlelzzie_newarrival.jpg
635 ms
free-shipping-block_1.gif
628 ms
banner_bottom1.png
902 ms
arrow_right_small.png
631 ms
facebook.png
635 ms
instagram.png
636 ms
pinterest.png
637 ms
homepage_week_19_2015-02.jpg
1451 ms
homepage_week_19_2015-03.jpg
1450 ms
homepage_week_19_2015-04.jpg
1443 ms
homepage_week_19_2015-05.jpg
1449 ms
logo.png
638 ms
ga.js
591 ms
show
853 ms
selectdown.png
87 ms
chosen-sprite.png
85 ms
n.png
85 ms
s.png
86 ms
w.png
85 ms
arrow_menu.png
103 ms
lzziearrow_left1.png
102 ms
lzziearrow_right1.png
102 ms
search.png
101 ms
combined.css
58 ms
smoothDivScroll.css
57 ms
stack_161235.js
91 ms
jquery.min.js
67 ms
jquery-ui.min.js
84 ms
jquery.mousewheel.min.js
61 ms
jquery.kinetic.js
62 ms
jquery.smoothdivscroll-1.3-min.js
61 ms
BfQP1MR3mJNaumtWa4Tizg.ttf
46 ms
zR-6QGMCFX5j-6nbH_HpIQ.ttf
62 ms
AQQ1r0_czneVCtTD9ckSEA.ttf
61 ms
Q5N_zd0042xOVES9NXt9QqCWcynf_cDxXwCLxiixG1c.ttf
59 ms
__utm.gif
38 ms
analytics.js
155 ms
stackpile.api-6712054ce0.js
156 ms
917416_1663844590543674_119966303_n.jpg
197 ms
play_small.png
150 ms
big_transparent.gif
48 ms
10009381_195396570835192_888080138_n.jpg
118 ms
12819080_1077460768942511_1913884340_n.jpg
86 ms
12822391_1705405899728411_1638099234_n.jpg
64 ms
10748227_1685910465001414_950241324_n.jpg
64 ms
12825843_1307376919278456_328221136_n.jpg
65 ms
12826009_859270147551883_827282867_n.jpg
66 ms
928197_616174305196273_692390235_n.jpg
129 ms
12826202_1565602513757179_1390220495_n.jpg
74 ms
12424640_912746725507516_330845874_n.jpg
126 ms
12328196_1777145612506644_1538698279_n.jpg
69 ms
12797934_230084584006533_471023190_n.jpg
171 ms
12825824_167086053677475_2042485720_n.jpg
117 ms
1661825_995904373836392_771688715_n.jpg
164 ms
12822550_850342188426357_1836829415_n.jpg
184 ms
12822415_1577083175941295_877267202_n.jpg
128 ms
12826245_609145242570059_354050179_n.jpg
195 ms
12783504_1545411169121618_697158893_n.jpg
160 ms
12783917_1138218389544685_87439838_n.jpg
144 ms
12784091_240517532955983_1412415767_n.jpg
211 ms
12797785_1728212577424808_198389362_n.jpg
195 ms
12783481_243698795964312_727389694_n.jpg
201 ms
12822576_250382408627350_626848496_n.jpg
185 ms
12383513_982018448543770_53334615_n.jpg
260 ms
12826195_583890865099765_87398237_n.jpg
289 ms
12748184_940477682687151_1188936799_n.jpg
195 ms
12818882_1519927608311713_368213653_n.jpg
197 ms
12818923_1678550282384165_1484907608_n.jpg
199 ms
12729513_987174871375947_1043677591_n.jpg
263 ms
12751561_1312132545479260_1694973137_n.jpg
218 ms
12751299_984530868290589_1056878260_n.jpg
241 ms
11849412_477877899065780_241206262_n.jpg
274 ms
12748421_985890134825912_1475083483_n.jpg
219 ms
stackpile.api-6712054ce0.js
43 ms
collect
29 ms
collect
78 ms
collect
17 ms
collect
22 ms
cdn_css_http_53987de2e9d341dd59a17d3e77e4e199.css
535 ms
nr-885.min.js
21 ms
a53393d12f
43 ms
a53393d12f
34 ms
a53393d12f
23 ms
cdn_css_http_a02d937904df09383d02aab21b26a1d0.css
535 ms
cdn_css_http_1febb18594813fbf558da87b8ab29131.css
525 ms
cdn_css_http_6debd19769ef5869bcabfce872613e78.css
507 ms
cdn_css_http_c8697f5a91d658cd9c7e556c8fb950db.css
524 ms
lzzie.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
[role]s do not have all required [aria-*] attributes
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
lzzie.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
lzzie.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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 Lzzie.com 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 Lzzie.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.
lzzie.com
Open Graph description is not detected on the main page of L Zzie. 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: