13.1 sec in total
727 ms
12.1 sec
242 ms
Click here to check amazing Junph content for China. Otherwise, check out these important facts you probably never knew about junph.com
龙牙商城成立于2008年,致力于服务那些对生活品质有追求的军迷。在国内初创社区+电商的商业模式,并向国内引进了M65风衣、G-1飞行夹克等经典服装款式。
Visit junph.comWe analyzed Junph.com page load time and found that the first response time was 727 ms and then it took 12.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
junph.com performance score
name
value
score
weighting
Value6.7 s
2/100
10%
Value11.4 s
0/100
25%
Value16.6 s
0/100
10%
Value3,740 ms
1/100
30%
Value0.185
66/100
15%
Value29.5 s
0/100
10%
727 ms
1736 ms
1471 ms
1545 ms
1850 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Junph.com, 17% (13 requests) were made to R.itiexue.net and 15% (12 requests) were made to Webpage.qidian.qq.com. The less responsive or slowest element that took the longest time to load (7.7 sec) relates to the external source Img3.junph.cn.
Page size can be reduced by 156.9 kB (4%)
3.7 MB
3.5 MB
In fact, the total size of Junph.com main page is 3.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. 55% of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.
Potential reduce by 61.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. This page needs HTML code to be minified as it can gain 19.7 kB, which is 27% 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 61.2 kB or 84% of the original size.
Potential reduce by 72.0 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. Junph images are well optimized though.
Potential reduce by 18.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 5.5 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. Junph.com has all CSS files already compressed.
Number of requests can be reduced by 35 (49%)
71
36
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Junph. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
junph.com
727 ms
www.junpin.com
1736 ms
base.css
1471 ms
swiper-bundle.css
1545 ms
base-all-v2.js
1850 ms
public.js
1570 ms
swiper-bundle.min.js
1917 ms
s.js
1667 ms
junpin.js
1568 ms
kf.js
1839 ms
bg.png
1577 ms
20170522050117981.png
1596 ms
20160412102707172.jpg
1168 ms
dianpu_01.jpg
1357 ms
20160527111203407.png
1243 ms
loadlogo400.png
1573 ms
erweima.jpg
1603 ms
weixin.gif
1620 ms
weibo.gif
1629 ms
dianpu_02.jpg
2337 ms
20161228041857424.jpg
2305 ms
ShowShoppingCarts
2250 ms
20220829061927898.jpg
3356 ms
20240429042816834.jpg
5708 ms
20220808101022448.jpg
3754 ms
kf.png
1575 ms
graybg.png
1777 ms
car.png
1783 ms
money.png
1818 ms
shouc.png
1817 ms
erwm.png
1860 ms
top.png
1846 ms
20220808100952956.jpg
7679 ms
20220809045408452.jpg
6585 ms
ico.png
2582 ms
hm.js
1182 ms
push.js
1192 ms
hm.gif
283 ms
bd735d2de17121e43bd5046b515c143b
1241 ms
bdb4adbb36d9db53ba048b63f73cff70
1266 ms
d2900253618582ef0b4e4ffe9a240a51
1266 ms
Suspension
1757 ms
Indexgit
1759 ms
index
197 ms
auto_dup
1532 ms
pk1.js
358 ms
i.js
7 ms
jsonp
1194 ms
getGrayLevel
926 ms
jsonp
1430 ms
getGrayLevel
855 ms
jsonp
2038 ms
getGrayLevel
858 ms
trace
1823 ms
trace
1821 ms
trace
2329 ms
trace
2353 ms
pc.html
503 ms
index.html
1303 ms
initQidianMonitor.js
8 ms
instant.js
5 ms
qidianMonitor.umd.min.js
85 ms
feedback-1.2.27.js
43 ms
trtc_4.14.4.js
28 ms
chunk-vendors.3a947e0a.css
42 ms
pc.736f6799.css
48 ms
chunk-imsdk.ae0a9363.js
41 ms
chunk-vendors.6399c7ff.js
67 ms
pc.9bf0685a.js
65 ms
collect
1584 ms
icomoon.f4992c50.ttf
10 ms
whitelist
1097 ms
qidianMonitor.umd.min.js
5 ms
jquery-1.12.4-fixed.min.js
1 ms
statusManager.js
32 ms
collect
1026 ms
amr.d8ebe3b6.js
17 ms
whitelist
996 ms
junph.com 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
junph.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
junph.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
![]()
ZH
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Junph.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 Junph.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.
junph.com
Open Graph description is not detected on the main page of Junph. 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: