2.5 sec in total
12 ms
1.9 sec
550 ms
Visit dupont.co.jp now to see the best up-to-date Du Pont content for Japan and also check out these interesting facts you probably never knew about dupont.co.jp
DuPont is using science and innovation to make the world a safer, healthier, and better place to live. It’s how we’re helping to invent a better now.
Visit dupont.co.jpWe analyzed Dupont.co.jp page load time and found that the first response time was 12 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
dupont.co.jp performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value15.4 s
0/100
25%
Value10.4 s
8/100
10%
Value2,340 ms
5/100
30%
Value0.001
100/100
15%
Value17.3 s
4/100
10%
12 ms
110 ms
53 ms
77 ms
101 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 80% of them (48 requests) were addressed to the original Dupont.co.jp, 12% (7 requests) were made to Dupont.scene7.com and 5% (3 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (987 ms) relates to the external source Dupont.scene7.com.
Page size can be reduced by 672.6 kB (30%)
2.2 MB
1.6 MB
In fact, the total size of Dupont.co.jp main page is 2.2 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. Only a small number of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 52.3 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 10.0 kB, which is 16% 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 52.3 kB or 82% of the original size.
Potential reduce by 92.8 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. Du Pont images are well optimized though.
Potential reduce by 527.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 527.5 kB or 76% of the original size.
Potential reduce by 0 B
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. Dupont.co.jp has all CSS files already compressed.
Number of requests can be reduced by 14 (33%)
42
28
The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Du Pont. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
dupont.co.jp
12 ms
www.dupont.co.jp
110 ms
clientlib-dependencies.min.css
53 ms
jquery.min.js
77 ms
clientlib-dependencies.min.js
101 ms
jquery-ui.min.css
62 ms
clientlib-global.min.css
71 ms
clientlib-base.min.css
292 ms
all.css
100 ms
contexthub
97 ms
launch-025f15007675.min.js
308 ms
clientlibs.min.css
291 ms
clientlibs.min.css
308 ms
clientlibs.min.js
305 ms
clientlibs.min.js
304 ms
jquery-ui.min.js
544 ms
clientlib-global.min.js
559 ms
clientlib-base.min.js
549 ms
back-arrow.svg
543 ms
DuPont_tm_rgb.png
545 ms
search.png
546 ms
noun-user.svg
550 ms
noun-user-active2.svg
549 ms
Play-Button.svg
551 ms
Now%20video_family%20on%20couch.jpg
557 ms
icon-linkedin.svg
550 ms
icon-youtube.svg
561 ms
icon-twitter.svg
558 ms
icon-facebook.svg
558 ms
token.json
431 ms
mAfZobkEOvojiRe0U2ya.infinity.json
213 ms
contexthub.pagedata.json
94 ms
www.dupont.co.jp.seg.js
75 ms
contexthub.commerce.orderhistory.json
89 ms
contexthub.commerce.relatedproducts.json
70 ms
contexthub.commerce.smartlists.json
89 ms
contexthub.commerce.cart.json
213 ms
corporate-connectivity-and-mobility-305x259
360 ms
nav-globe-icon.png
156 ms
corporate-urbanization-and-safety-305x259
688 ms
corporate-environmental-protection-305x259
686 ms
contexthub.commerce.orderhistory.json
32 ms
green-forest-sustainability-650x650
419 ms
DWS-CW-logo-image
415 ms
climate-video-sustainability-thumbnail
301 ms
corp-news-cleanroom-silicone-1440x700
987 ms
noto-sans-v8-latin-regular.woff
295 ms
noto-sans-v8-latin-regular.woff
294 ms
NotoSans-Regular.woff
293 ms
Diodrum-Medium.woff
298 ms
Diodrum-Medium.woff
412 ms
DiodrumCyrillic-Medium.woff
204 ms
Diodrum-Regular.woff
295 ms
Diodrum-Regular.woff
407 ms
DiodrumCyrillic-Regular.woff
409 ms
fa-solid-900.woff
48 ms
fa-regular-400.woff
48 ms
Diodrum-Semibold.woff
211 ms
Diodrum-Semibold.woff
212 ms
DiodrumCyrillic-Semibold.woff
102 ms
dupont.co.jp 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Form elements do not have associated labels
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>).
dupont.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
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
Missing source maps for large first-party JavaScript
dupont.co.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dupont.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Dupont.co.jp 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.
dupont.co.jp
Open Graph data is detected on the main page of Du Pont. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: