38.2 sec in total
1 sec
32.4 sec
4.7 sec
Click here to check amazing Juanpi content for China. Otherwise, check out these important facts you probably never knew about juanpi.com
卷皮折扣汇聚全网最优质折扣商品,每日精选千款超值折扣商品9.9元起全场包邮1折特卖,每天10点限时秒杀!上卷皮购便宜!
Visit juanpi.comWe analyzed Juanpi.com page load time and found that the first response time was 1 sec and then it took 37.1 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.
juanpi.com performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value16.1 s
0/100
25%
Value18.5 s
0/100
10%
Value1,220 ms
20/100
30%
Value0.084
93/100
15%
Value14.2 s
9/100
10%
1047 ms
1962 ms
1464 ms
1385 ms
1830 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Juanpi.com, 36% (43 requests) were made to S.juancdn.com and 21% (26 requests) were made to S1.juancdn.com. The less responsive or slowest element that took the longest time to load (18.9 sec) relates to the external source S1.juancdn.com.
Page size can be reduced by 1.3 MB (53%)
2.5 MB
1.2 MB
In fact, the total size of Juanpi.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. 55% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 606.9 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 257.5 kB, which is 40% 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 606.9 kB or 95% of the original size.
Potential reduce by 178.5 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, Juanpi needs image optimization as it can save up to 178.5 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 305.8 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 305.8 kB or 73% of the original size.
Potential reduce by 219.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. Juanpi.com needs all CSS files to be minified and compressed as it can save up to 219.4 kB or 86% of the original size.
Number of requests can be reduced by 53 (47%)
113
60
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Juanpi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
juanpi.com
1047 ms
www.juanpi.com
1962 ms
1464 ms
1385 ms
1830 ms
7268 ms
2538 ms
md-h5joa.js
1504 ms
jp.header.js
1872 ms
jp.cart.js
1860 ms
aq_auth.js
3377 ms
3126 ms
1987 ms
1913 ms
3486 ms
2292 ms
bfd.js
2472 ms
md-viewregistreward.js
2729 ms
md-time.js
2665 ms
3450 ms
3417 ms
57061b0492be59f07c8b4570_680x280.jpg
7522 ms
56d795ab92be5964aa8b456e_180x90.png
3027 ms
57038ed292be59b7278b456e_680x280.jpg
6188 ms
57062d3f92be598ba98b4567_680x280.jpg
10461 ms
56a843da92be5916728b4584_180x90.png
4205 ms
5705d08a92be591c958b456d_180x90.png
3380 ms
564d77ae45064_180x90.png
4429 ms
56c6ba8b92be59326b8b456d_180x90.png
6468 ms
568cbe9392be597a3a8b4576_180x90.png
6644 ms
56f8f04892be59b6228b456e_180x90.png
4869 ms
56fa509492be590e158b4567_180x90.png
5267 ms
56396f7dcd6c1_180x90.png
5679 ms
56722bfa92be59dcab8b4577_180x90.png
6171 ms
header-total.gif
749 ms
jp-app-index.png
2489 ms
phone-new-20151119.png
1729 ms
icon-total.png
1029 ms
loading.gif
1501 ms
blank.png
1804 ms
r_315new.gif
1094 ms
r_cnnic.gif
1465 ms
r_gongshang.gif
1783 ms
default-60.jpg
1966 ms
li_cur.png
1833 ms
dotted_line.png
2106 ms
ct_icons.png
2429 ms
icon-arrow.png
2123 ms
icon-arrow-active.png
2261 ms
brand_new.png
2331 ms
icon_new.png
2580 ms
jp-app-90.png
4821 ms
school-ico.png
6649 ms
service_add.gif
2821 ms
sidebar.png
4262 ms
getgroupctag
1781 ms
zhe-item.js
2450 ms
time
2086 ms
h.js
732 ms
piwik.js
3372 ms
analytics.js
120 ms
juanpi_liontrack.min.2.0.js
6019 ms
linkid.js
66 ms
collect
39 ms
collect
180 ms
landcookie.php
2686 ms
juanpiwang.js
2754 ms
1296 ms
hm.gif
341 ms
240
2423 ms
NC
124 ms
57062e9a92be59659d8b458b_36x100.jpg
4372 ms
57062e8992be5998968b4595_130x248.jpg
5261 ms
570627d192be59429a8b456d_124x119.jpg
5247 ms
5706280c92be597e8c8b4576_124x119.jpg
4822 ms
5706287e92be594f988b4582_124x119.jpg
6486 ms
5706284e92be59438a8b459e_124x119.jpg
5260 ms
570628b592be59098a8b4580_250x120.jpg
6258 ms
57062c7f92be59b5948b4589_700x360.jpg
8375 ms
570632d092be59b3ac8b4574_700x360.jpg
9282 ms
570646f392be5914218b4567_700x360.jpg
9707 ms
56fe78ed92be5988738b4577_700x360.jpg
18856 ms
56fe71e892be595a708b456d_700x360.jpg
14854 ms
57062d3692be59dfa88b456a_554x450.png
17860 ms
btn-close.png
2032 ms
sm_124x47.png
5856 ms
brank.png
702 ms
bcore.min.js
6929 ms
list-total.png
393 ms
5705b9cf92be59b04b8b458d_400x400.jpg
6414 ms
56d43cd392be5912068b4577_400x400.jpg
8195 ms
5705baf292be5970448b4586_400x400.jpg
6545 ms
5705d59992be5953908b4585_400x400.jpg
6658 ms
j
437 ms
t
1254 ms
pixel
135 ms
ping.gif
755 ms
cm.gif
1000 ms
t.gif
848 ms
cm.mediav.com
2459 ms
mapping.do
7898 ms
cm.fastapi.net
1009 ms
wisemedia.cm.admaster.com.cn
4605 ms
pixel
31 ms
map
961 ms
m
963 ms
map
1019 ms
map
870 ms
m
852 ms
m
1053 ms
m
1052 ms
map
1006 ms
m
4045 ms
m
1176 ms
m
1164 ms
PageView.do
727 ms
clientData.html
1379 ms
AddUser.do
550 ms
m
9535 ms
StdID.do
360 ms
map
843 ms
juanpi.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-hidden="true"] elements contain focusable descendents
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
juanpi.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
Browser errors were logged to the console
Page has valid source maps
juanpi.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Juanpi.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Juanpi.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.
juanpi.com
Open Graph description is not detected on the main page of Juanpi. 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: