8.5 sec in total
941 ms
7 sec
579 ms
Visit jd.id now to see the best up-to-date JD content for Indonesia and also check out these interesting facts you probably never knew about jd.id
JD.com is the largest retailer in China, a member of the NASDAQ100 and a Fortune Global 500 company.
Visit jd.idWe analyzed Jd.id page load time and found that the first response time was 941 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
jd.id performance score
name
value
score
weighting
Value10.6 s
0/100
10%
Value23.0 s
0/100
25%
Value40.2 s
0/100
10%
Value2,500 ms
4/100
30%
Value0.18
67/100
15%
Value24.1 s
0/100
10%
941 ms
1206 ms
1995 ms
2553 ms
2129 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 4% of them (5 requests) were addressed to the original Jd.id, 56% (64 requests) were made to Img.360buyimg.jd.id and 23% (26 requests) were made to St.jd.id. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source St.jd.id.
Page size can be reduced by 608.0 kB (15%)
4.1 MB
3.5 MB
In fact, the total size of Jd.id main page is 4.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. 75% 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 3.3 MB which makes up the majority of the site volume.
Potential reduce by 272.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. This page needs HTML code to be minified as it can gain 136.0 kB, which is 46% 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 272.7 kB or 92% of the original size.
Potential reduce by 63.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. JD images are well optimized though.
Potential reduce by 189.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 189.0 kB or 48% of the original size.
Potential reduce by 82.6 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.id needs all CSS files to be minified and compressed as it can save up to 82.6 kB or 78% of the original size.
Number of requests can be reduced by 30 (27%)
111
81
The browser has sent 111 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 19 to 1 for JavaScripts and as a result speed up the page load time.
jd.id
941 ms
www.jd.id
1206 ms
base.css
1995 ms
2553 ms
st.jd.id
2129 ms
2043 ms
2051 ms
2057 ms
nHBfsgAAAwAAAAwAAVPLSAABRuw.png
2022 ms
nHBfsgAACAAAAAEAARvD2QAATlg.jpg
1962 ms
nHBfsgAAAgAAAA0AAVH0zQAA4T8.jpg
1988 ms
nHBfsgAACgAAABoAASHweQAAeg0.jpg
1962 ms
nHBfsgAABgAAABcAAbd1fQAAQsE.jpg
1937 ms
nHBfsgAACQAAABoAAX0rYAABJbw.jpg
1997 ms
nHBfsgAACgAAABQAAS2tIAAAqm8.jpg
1996 ms
nHBfsgAACgAAABMAAS2P3gAAyRU.jpg
2019 ms
nHBfsgAABgAAAAMAAZfEJgABKh8.jpg
2046 ms
nHBfsgAAAgAAAA4AAVFWlQABT5s.png
2071 ms
nHBfsgAACAAAAB0AAWAy2wAA8TM.jpg
2048 ms
nHBfsgAAAQAAABwAAUc0AAABFjg.jpg
2051 ms
nHBfsgAABwAAAAkAAQv2ywAARn4.jpg
2047 ms
nHBfsgAAAwAAAB4AATPHCwAAVHI.jpg
2044 ms
nHBfsgAAAwAAAAgAAP4yWAABODI.jpg
2095 ms
nHBfsgAACQAAABsAAV9UJgAAZDo.jpg
2071 ms
nHBfsgAAAwAAAAcAAVjU-AABSIQ.jpg
2098 ms
nHBfsgAACAAAAAoAAXEfYgAFGVk.png
2183 ms
nHBfsgAABwAAABwAAb11pQAAQxk.jpg
2080 ms
nHBfsgAACAAAABAAAgj76QABtJE.jpg
2150 ms
nHBfsgAACAAAAAQAAYxjYAABsU4.png
2156 ms
nHBfsgAABQAAAAsAAL1IxAABOz4.jpg
2137 ms
nHBfsgAABgAAABwAAU4xVwADorw.jpg
2198 ms
nHBfsgAAAgAAABQAAWXmcwABUfc.jpg
2151 ms
qrcode_android.png
50 ms
blank.gif
556 ms
blank.gif
51 ms
gtm.js
51 ms
nHBfsgAABAAAABcAAOMkhAAAlI0.jpg
2145 ms
nHBfsgAACAAAAAgAAOMdWwAAlI0.jpg
2157 ms
nHBfsgAABwAAABkAAQuNyAAAlI0.jpg
2157 ms
nHBfsgAAAgAAABAAAOlrpwAAlI0.jpg
2162 ms
nHBfsgAABQAAABcAAL5y9QAAlI0.jpg
2173 ms
nHBfsgAACAAAAAUAARKHsQAAlI0.jpg
2184 ms
nHBfsgAABAAAABYAAM3j5QAAlI0.jpg
2186 ms
nHBfsgAACgAAABsAAQSaaQAAlI0.jpg
2188 ms
nHBfsgAABgAAABEAAS_4KQAAlI0.jpg
2189 ms
nHBfsgAACQAAAAMAANCvWgAAlI0.jpg
2203 ms
nHBfsgAAAQAAAA0AATa4TgAAlI0.jpg
2203 ms
logo.png
73 ms
icon.png
73 ms
icon.png
72 ms
icon.png
73 ms
ico_cat.png
73 ms
loading.gif
74 ms
bg-bd.png
50 ms
icon.png
51 ms
ui.js
553 ms
ja.js
60 ms
analytics.js
8 ms
conversion.js
88 ms
ec.js
8 ms
collect
68 ms
collect
4 ms
collect
2 ms
collect
76 ms
view-uuid
2079 ms
log.gif
2081 ms
ga-audiences
52 ms
567 ms
552 ms
common.js
563 ms
st.jd.id
561 ms
nHBfsgAABgAAAAcAAX7jvgAABJM.png
1032 ms
icon_editor_recommend.png
42 ms
fetch_cart_num.html
709 ms
element.js
46 ms
helloService
515 ms
category.html
72 ms
superDeal.html
333 ms
firstCmCat.html
61 ms
translateelement.css
55 ms
main.js
70 ms
548 ms
element_main.js
39 ms
translate_24dp.png
23 ms
l
46 ms
super_deals_icon.png
30 ms
helloService
1040 ms
nHBfsgAACAAAAAIAAgFndAAABKY.png
302 ms
nHBfsgAACgAAAAYAAVRq5gAABG8.png
283 ms
nHBfsgAAAQAAABAAAWT_tgAABMA.png
286 ms
nHBfsgAAAQAAABEAAaQFRgAABUE.png
270 ms
nHBfsgAABQAAABsAAYaJ1gAABQY.png
264 ms
nHBfsgAAAgAAABsAAVx0eQAABsk.png
272 ms
nHBfsgAAAwAAABkAAUKgKwAABuo.png
248 ms
nHBfsgAAAgAAAAYAAbw7BAAABog.png
249 ms
nHBfsgAACQAAAAwAAYcZ5wADzDY.png
316 ms
nHBfsgAAAQAAAAEAAYol8wAFtuM.png
311 ms
nHBfsgAABwAAABkAAfet1AACde4.png
325 ms
nHBfsgAACgAAAAcAAXPj8gAF4yQ.png
352 ms
nHBfsgAABAAAABoAAXMBjwABd4U.png
269 ms
nHBfsgAABAAAAA4AAUL0rQAFatY.png
305 ms
nHBfsgAAAwAAAAoAATbr-QAFA5M.png
383 ms
nHBfsgAAAgAAAA8AAaRXHgADU4M.png
326 ms
nHBfsgAAAgAAAAUAAXRXGwAD76g.png
348 ms
nHBfsgAACAAAAAEAAZfo3AABWZQ.png
331 ms
nHBfsgAABgAAAAcAAYDYFgAB9X0.png
266 ms
nHBfsgAABgAAAAEAAK212wABcjo.jpg
277 ms
nHBfsgAAAwAAABQAAHB7eQAA8II.jpg
279 ms
nHBfsgAABwAAAA4AAOVQhgAEFw8.jpg
303 ms
nHBfsgAACgAAABMAAGDrhQAB-Lk.jpg
315 ms
nHBfsgAAAQAAAAsAAI3OzwABz9U.jpg
308 ms
nHBfsgAAAgAAAAMAAFT7WgAAsG0.jpg
279 ms
nHBfsgAACAAAAAsAAGB_WwAAUNE.jpg
287 ms
nHBfsgAABQAAAAEAAC8plQAA4o0.jpg
297 ms
nHBfsgAABgAAAAwAAIiKOgAAhMc.jpg
289 ms
jd.id 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
Image elements do not have [alt] attributes
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.
jd.id best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
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
jd.id 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 doesn't use legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jd.id 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.id 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.
jd.id
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: