Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

jd.id

JD.com, Inc.

Page Load Speed

8.5 sec in total

First Response

941 ms

Resources Loaded

7 sec

Page Rendered

579 ms

jd.id screenshot

About Website

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.id

Key Findings

We 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 80% of websites can load faster.

Performance Metrics

jd.id performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value23.0 s

0/100

25%

SI (Speed Index)

Value40.2 s

0/100

10%

TBT (Total Blocking Time)

Value2,500 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.18

67/100

15%

TTI (Time to Interactive)

Value24.1 s

0/100

10%

Network Requests Diagram

jd.id

941 ms

www.jd.id

1206 ms

base.css

1995 ms

2553 ms

st.jd.id

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 Optimization Overview & Recommendations

Page size can be reduced by 571.5 kB (14%)

Content Size

4.1 MB

After Optimization

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. 80% 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.

HTML Optimization

-92%

Potential reduce by 272.7 kB

  • Original 297.7 kB
  • After minification 161.7 kB
  • After compression 24.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 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.

Image Optimization

-2%

Potential reduce by 63.6 kB

  • Original 3.3 MB
  • After minification 3.3 MB

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.

JavaScript Optimization

-43%

Potential reduce by 152.5 kB

  • Original 357.1 kB
  • After minification 356.2 kB
  • After compression 204.6 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 152.5 kB or 43% of the original size.

CSS Optimization

-78%

Potential reduce by 82.6 kB

  • Original 106.5 kB
  • After minification 106.0 kB
  • After compression 23.9 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.

Requests Breakdown

Number of requests can be reduced by 30 (27%)

Requests Now

111

After Optimization

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.

Accessibility Review

jd.id accessibility score

59

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

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

High

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

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

jd.id best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the geolocation permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

jd.id SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: