32.3 sec in total
1.9 sec
29.9 sec
503 ms
Visit uzise.com now to see the best up-to-date Uzise content for Hong Kong and also check out these interesting facts you probably never knew about uzise.com
柚子舍是中国无添加护肤品冠军,以全球领先的七大无添加为研发核心理念,力求带给每个爱美女性最完美的护肤体验,敏感肌肤、孕妇也能用的护肤品。顶级配方、7天免费体验,值得妳信赖
Visit uzise.comWe analyzed Uzise.com page load time and found that the first response time was 1.9 sec and then it took 30.4 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.
uzise.com performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value5.4 s
21/100
25%
Value14.4 s
1/100
10%
Value180 ms
92/100
30%
Value0
100/100
15%
Value6.3 s
61/100
10%
1863 ms
3038 ms
682 ms
700 ms
863 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 44% of them (51 requests) were addressed to the original Uzise.com, 22% (25 requests) were made to Uimg.uzise.com and 9% (11 requests) were made to Ckmap.mediav.com. The less responsive or slowest element that took the longest time to load (19.8 sec) relates to the external source Uimg.uzise.com.
Page size can be reduced by 176.1 kB (20%)
877.0 kB
700.9 kB
In fact, the total size of Uzise.com main page is 877.0 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. Images take 678.9 kB which makes up the majority of the site volume.
Potential reduce by 63.4 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 14.6 kB, which is 18% 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 63.4 kB or 77% of the original size.
Potential reduce by 52.6 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. Uzise images are well optimized though.
Potential reduce by 23.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 23.9 kB or 35% of the original size.
Potential reduce by 36.2 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. Uzise.com needs all CSS files to be minified and compressed as it can save up to 36.2 kB or 79% of the original size.
Number of requests can be reduced by 46 (41%)
111
65
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Uzise. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
uzise.com
1863 ms
base.css
3038 ms
dialog.loginreg.css
682 ms
index.css
700 ms
uaredirect.js
863 ms
jquery-1.9.1.min.js
3188 ms
jquery.autocomplete.min.js
342 ms
jquery.artDialog.js
1979 ms
underscore.js
1454 ms
common.js
1358 ms
ajaxtool.js
679 ms
getCode.js
1018 ms
jquery.slides.min.js
1358 ms
jquery.lazyload.js
1714 ms
6d213b0e8717ba0eef7223997c3b2cd4.jpg
8747 ms
2175 ms
5dfff2d667f20784c8f15d3790f3f334.jpg
5345 ms
a8e7f3948a66cf28f1b74167cae4cd21.jpg
19796 ms
4c7a6bb4b2d7ecec495baf39e9553e56.jpg
5733 ms
33ae0cdb5ef7e0ee6187fba8bbf99b28.jpg
3721 ms
5ef9720195d3dd20706fbc58f11b7323.jpg
3908 ms
c7da54c348103bc233e15e3612e234af.jpg
4063 ms
95483d6b3932659cefc4b7546f66ae0e.png
4923 ms
790a33520002662a98c7f008eb6f3e31.jpg
4403 ms
be43dc717a4c11f34df9433bdf0731e4.jpg
7147 ms
865f241bed35a41ef3111012b078b24f.jpg
5279 ms
3558f89e47d0ab9ca1afc41a6018c24d.jpg
5618 ms
d463cd0d03f724645ca6291c74f3a53c.jpg
6020 ms
537fda59f08d4abc9defdf981e2280ac.jpg
8977 ms
b185c60a7eafa5d25c5b3d2eaa6a8d92.jpg
6090 ms
7139a4f9863cebdc63b9026981fe355c.jpg
8358 ms
b71188ecd4319107dae05029eb6c24f2.jpg
6429 ms
fe687d575be555e1f98f0f2c7bbacab0.jpg
13575 ms
cd057065b55c2ca13860836cd48121c5.jpg
7487 ms
32471c585361996c0799f32feba75fa7.jpg
7832 ms
9ac17856ae057e6a9fe94623e5ada028.jpg
9069 ms
57b5942f3246a1dbe886e9e7af12c003.jpg
12837 ms
38c9a0bf6c5d27c4cb62ad4bd0636848.jpg
9062 ms
8e3ed63b6cf0fe10e95ad122aa7510d5.jpg
9314 ms
bf50181e6bb922f80fc695909396460a.jpg
9400 ms
index_bg.gif
433 ms
ui.header.png
702 ms
wechat_log_18x18.png
1071 ms
qrcode.jpg
3088 ms
header_logo.jpg
341 ms
header_title.jpg
2395 ms
topic_ban_30.png
877 ms
focus.jpg
19791 ms
topic_ban.png
1533 ms
ui.index.png
1845 ms
index_7noadd_bg.jpg
2100 ms
index_7noadd.png
9042 ms
ui.index5.png
3500 ms
index_mov_sld1.jpg
18636 ms
index_mov_sld2.jpg
8738 ms
index_mov_bg.png
3422 ms
consulClose2.png
3757 ms
red.png
3943 ms
1.png
19789 ms
ui.floating.png
4809 ms
ui.footer.png
5244 ms
footer_service.png
7834 ms
footer_honor1.jpg
9921 ms
footer_honor2.jpg
10588 ms
footer_honor4.jpg
9410 ms
footer_honor5.jpg
9765 ms
footer_honor3.jpg
10825 ms
footer_honor6.jpg
10353 ms
footer_CRPSC.jpg
11232 ms
idialog.css
10425 ms
piwik.js
3009 ms
h.js
1988 ms
hm.gif
324 ms
mvl.js
52 ms
tk.js
2997 ms
Cyouzishe.js
2539 ms
jquery.placeholder.js
356 ms
ajax-cart-info
530 ms
api
612 ms
icon-new.gif
674 ms
space.gif
938 ms
mba.js
135 ms
mv.js
8 ms
b
1180 ms
t
3343 ms
t
1854 ms
wb.js
8 ms
pixel
19 ms
t.gif
1875 ms
ckmap.htm
519 ms
cm.gif
5114 ms
pixel
15 ms
m
433 ms
m
2430 ms
m
879 ms
m
3782 ms
m
1997 ms
bcore.min.js
1977 ms
m
460 ms
m
1742 ms
t.gif
603 ms
m
1283 ms
clientData.html
448 ms
m
659 ms
PageView.do
535 ms
AddUser.do
537 ms
StdID.do
281 ms
m
444 ms
loading1.gif
3630 ms
bundle.js
1067 ms
idialog_s.png
374 ms
loading.gif
469 ms
hm.gif
324 ms
client.js
2 ms
iframeWidget.js
2 ms
aj_relationship.php
4471 ms
uzise.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
Image elements do not have [alt] attributes
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.
uzise.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
uzise.com SEO score
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 doesn't use legible font sizes
N/A
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uzise.com 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 Chinese. Our system also found out that Uzise.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.
uzise.com
Open Graph description is not detected on the main page of Uzise. 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: