23.9 sec in total
1.3 sec
21 sec
1.7 sec
Visit jd.com now to see the best up-to-date JD content for China and also check out these interesting facts you probably never knew about jd.com
JD.com is the largest retailer in China, a member of the NASDAQ100 and a Fortune Global 500 company.
Visit jd.comWe analyzed Jd.com page load time and found that the first response time was 1.3 sec and then it took 22.6 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.
jd.com performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value9.4 s
1/100
25%
Value12.5 s
3/100
10%
Value50 ms
100/100
30%
Value0
100/100
15%
Value7.2 s
51/100
10%
1308 ms
900 ms
750 ms
83 ms
1015 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Jd.com, 21% (21 requests) were made to Img12.360buyimg.com and 19% (19 requests) were made to Misc.360buyimg.com. The less responsive or slowest element that took the longest time to load (3.5 sec) relates to the external source D.3.cn.
Page size can be reduced by 521.2 kB (25%)
2.1 MB
1.6 MB
In fact, the total size of Jd.com main page is 2.1 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.5 MB which makes up the majority of the site volume.
Potential reduce by 188.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. 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 188.2 kB or 77% of the original size.
Potential reduce by 83.7 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. JD images are well optimized though.
Potential reduce by 240.5 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 240.5 kB or 68% of the original size.
Potential reduce by 8.7 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. Jd.com needs all CSS files to be minified and compressed as it can save up to 8.7 kB or 81% of the original size.
Number of requests can be reduced by 18 (19%)
97
79
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JD. 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 as a result speed up the page load time.
jd.com
1308 ms
www.jd.com
900 ms
jd2015img.png
750 ms
56f4e6b8N940f608c.png
83 ms
5707bf81N82331e7b.jpg
1015 ms
misc.360buyimg.com
744 ms
init.js
708 ms
wl.js
723 ms
cookie_check
1664 ms
55fa82feN72ffadc6.png
71 ms
55fa838bNd53c791c.png
73 ms
logo-201305.png
699 ms
loading.gif
816 ms
misc.360buyimg.com
51 ms
log.gif
1686 ms
main.js
422 ms
insertStyles.js
187 ms
301 ms
focus
1977 ms
blank.gif
395 ms
57067372Ndcdee854.jpg
1167 ms
hotWords.php
1391 ms
helloService.ashx
2401 ms
todays.js
52 ms
guess-like.js
95 ms
special-buy-v4.js
90 ms
banner.js
87 ms
index-1-floor1-floor_index.js
3542 ms
common.css
52 ms
diviner
2026 ms
loading.gif
74 ms
homebg.png
87 ms
price.js
74 ms
57069931N9a652df0.jpg
72 ms
57077871N38dab416.jpg
215 ms
57077a22N482b73b4.jpg
312 ms
57015e33N4b44a302.jpg
2032 ms
toolbar.png
246 ms
loading.gif
238 ms
5703e6a1N6f9449a6.jpg
239 ms
56fba0f3Nc3db1a17.jpg
241 ms
56e8f995N517fa0fa.jpg
238 ms
56e23586Nb9a1fd16.jpg
311 ms
56fba0d6Nc038a475.jpg
230 ms
5703cc24Nc1bb000f.jpg
270 ms
5707e098N1abb4d10.jpg
202 ms
56efab44N0eb64646.jpg
173 ms
56c6dc40Nae0b6ede.jpg
177 ms
5703e9eaNeac1f077.jpg
293 ms
56e235a2Nd380a436.jpg
238 ms
56de6ae1N9058b7e7.jpg
246 ms
5703e701N03ee50ab.jpg
243 ms
5703bb28N504d341f.jpg
319 ms
5703d295N3d28e002.jpg
285 ms
57082d39N111a2656.jpg
1966 ms
5707d930Nbd3b4619.jpg
1874 ms
56f5135cN2a0fe57c.jpg
1968 ms
56e2356aNf323c281.jpg
1964 ms
56fb9f5fNd4a1f470.jpg
1968 ms
5707f279N5b6363ca.jpg
1964 ms
diviner
1955 ms
log.gif
522 ms
56fb8e45N750ef315.jpg
1344 ms
56f8033cN33b0ed06.jpg
1109 ms
5707807eNc0222675.jpg
1105 ms
5704f696N9f57344e.jpg
1106 ms
log.gif
348 ms
useripinfo.php
317 ms
54cef1e3N796d7688.jpg
31 ms
5706e806N9504f7d5.jpg
172 ms
5706e84eNeb1569f4.jpg
65 ms
5706e605N06c657d1.jpg
63 ms
5706e15eN18cff214.jpg
169 ms
56fcf9e6Ne2463ade.png
64 ms
56fc7909N6863ca92.jpg
65 ms
56fcfa58N8e1449e1.png
65 ms
floor.js
62 ms
5706e765Nd5bb5d34.jpg
172 ms
5706e6abN099f49c2.jpg
79 ms
5706e6f2N53fb856b.jpg
78 ms
5706e713Nc495d91a.jpg
77 ms
55f29088Naf3168a0.jpg
79 ms
56f2100cN901551ae.jpg
164 ms
5706e645N0b1e950f.jpg
165 ms
57063a33Na12a7111.jpg
141 ms
5703ed98N1fe2ef70.jpg
143 ms
56fce844N47350d4e.jpg
151 ms
569ef889N6fb99488.jpg
164 ms
5706e696N396f1252.jpg
146 ms
5706e6d0N60c4fe92.jpg
137 ms
5706e72bNdbf4f524.jpg
137 ms
57032002N60155d8a.jpg
140 ms
floor1new.png
136 ms
clothesicon.png
135 ms
5704faeeN8412a727.jpg
127 ms
5703e014Nf5725ff0.jpg
1085 ms
cm.mediav.com
1170 ms
57078f71N6a539ffa.jpg
209 ms
get
1807 ms
5707c251Ne6b7eb7a.jpg
119 ms
jd.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-*] attributes do not match their roles
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
jd.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
jd.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 uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
GBK
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jd.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Jd.com main page’s claimed encoding is gbk. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
jd.com
Open Graph description is not detected on the main page of JD. 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: