Tools & Wizards About Us
ww2.duracell.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ww2.duracell.com

Duracell Batteries | AA, AAA, Rechargeable, Coin Button

Page Load Speed

3 sec in total

First Response

22 ms

Resources Loaded

2.9 sec

Page Rendered

80 ms

ww2.duracell.com screenshot

About Website

Visit ww2.duracell.com now to see the best up-to-date Ww 2 Duracell content for United States and also check out these interesting facts you probably never knew about ww2.duracell.com

Explore AA, rechargeable batteries, chargers, coin button batteries and more from Duracell, the longer lasting and #1 trusted battery brand.

Visit ww2.duracell.com

Key Findings

We analyzed Ww2.duracell.com page load time and found that the first response time was 22 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

ww2.duracell.com performance score

0

Network Requests Diagram

index.jspx

22 ms

501 ms

vendor.css

96 ms

fonts.css

221 ms

bootstrap.css

256 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Ww2.duracell.com, 35% (13 requests) were made to Duracell.com and 22% (8 requests) were made to . The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source D2ei442zrkqy2u.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (76%)

Content Size

2.9 MB

After Optimization

698.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ww2.duracell.com main page is 2.9 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. Javascripts take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 8.8 kB

  • Original 12.6 kB
  • After minification 11.4 kB
  • After compression 3.8 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 8.8 kB or 70% of the original size.

Image Optimization

-7%

Potential reduce by 128 B

  • Original 1.8 kB
  • After minification 1.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. Ww 2 Duracell images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 1.8 MB

  • Original 2.3 MB
  • After minification 1.7 MB
  • After compression 465.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 1.8 MB or 80% of the original size.

CSS Optimization

-60%

Potential reduce by 342.1 kB

  • Original 570.1 kB
  • After minification 536.1 kB
  • After compression 228.0 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. Ww2.duracell.com needs all CSS files to be minified and compressed as it can save up to 342.1 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (74%)

Requests Now

23

After Optimization

6

  • Images
  • JavaScript
  • CSS

The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ww 2 Duracell. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

index.jspx

index.jspx

22 ms

501 ms

vendor.css

vendor.css

96 ms

fonts.css

fonts.css

221 ms

bootstrap.css

bootstrap.css

256 ms

main.css

main.css

282 ms

front.css

front.css

174 ms

detection.js

detection.js

188 ms

vendor.js

vendor.js

866 ms

scripts.js

scripts.js

417 ms

bvapi.js

bvapi.js

39 ms

ps-widget.js

ps-widget.js

66 ms

wp-embed.min.js

wp-embed.min.js

271 ms

576671928E08653BD.css

576671928E08653BD.css

1098 ms

gtm.js

gtm.js

155 ms

1x-s0cffc46cd7.png

1x-s0cffc46cd7.png

133 ms

0VDh8

0VDh8

39 ms

a53yktVTwx8UqYPgY4TGR8f6zy20+NvpPoJxDc4cA==

a53yktVTwx8UqYPgY4TGR8f6zy20+NvpPoJxDc4cA==

38 ms

txeVGMPQKm7FVPQdgsM9NwId8mQ3ULOABe93vVNeqnpi4JMyfQh0nMj4+FjnsZ0efyPVTzSPOIw=

txeVGMPQKm7FVPQdgsM9NwId8mQ3ULOABe93vVNeqnpi4JMyfQh0nMj4+FjnsZ0efyPVTzSPOIw=

38 ms

WJuCd66qKAP7dnlRjD0CpuxVT0LYLDHTcCHfJkN1CzgAXvt71TXqp6YuCTMn0IdJjI+PhY57GdHn4j1S8UeTiE

WJuCd66qKAP7dnlRjD0CpuxVT0LYLDHTcCHfJkN1CzgAXvt71TXqp6YuCTMn0IdJjI+PhY57GdHn4j1S8UeTiE

38 ms

F9QZfpbgFUp0ddO2SnLF9G8iOZJ0RxrpZy6PRe+uj6c4M31WyiyLI95zfMzsR8lUaYPeGVwQqIW7kf1ibgneuqigD+3Z5UYw9AqbsVU9C2Cwx03Ah3yZDdQs4AF77e9U16qemLgkzJ9CHSYyPj4WOexnR5+I9Uv9FQ4fA==

F9QZfpbgFUp0ddO2SnLF9G8iOZJ0RxrpZy6PRe+uj6c4M31WyiyLI95zfMzsR8lUaYPeGVwQqIW7kf1ibgneuqigD+3Z5UYw9AqbsVU9C2Cwx03Ah3yZDdQs4AF77e9U16qemLgkzJ9CHSYyPj4WOexnR5+I9Uv9FQ4fA==

37 ms

a53yktVTwx8UqYPgY4TGR8f6zy20+NvpPoJxDc4cA==

a53yktVTwx8UqYPgY4TGR8f6zy20+NvpPoJxDc4cA==

38 ms

I9VPNI84jA==

I9VPNI84jA==

37 ms

F9QZfpbgFUp0ddO2SnLF9G8iOZJ0RxrpZy6PRe+uj6c4M31WyiyLI95zfMzsR8lUaYPeGVwQqIW7kf1ibgneuqigD+3Z5UYw9AqbsVU9C2Cwx03Ah3yZDdQs4AF77e9U16qemLgkzJ9CHSYyPj4WOexnR5+I9UvFHk4hA==

F9QZfpbgFUp0ddO2SnLF9G8iOZJ0RxrpZy6PRe+uj6c4M31WyiyLI95zfMzsR8lUaYPeGVwQqIW7kf1ibgneuqigD+3Z5UYw9AqbsVU9C2Cwx03Ah3yZDdQs4AF77e9U16qemLgkzJ9CHSYyPj4WOexnR5+I9UvFHk4hA==

37 ms

2FBDFD_0_0.woff

2FBDFD_0_0.woff

212 ms

2FCE65_1_0.woff

2FCE65_1_0.woff

230 ms

2FCE65_0_0.woff

2FCE65_0_0.woff

212 ms

config.js

config.js

196 ms

h1.js

h1.js

15 ms

analytics.js

analytics.js

14 ms

jquery-bv%401.11.1%2Blodash-bv%401.2.0.js

jquery-bv%401.11.1%2Blodash-bv%401.2.0.js

37 ms

bv-primary.js

bv-primary.js

75 ms

6959.js

6959.js

13 ms

collect

collect

48 ms

collect

collect

15 ms

icong2.png

icong2.png

3 ms

screen.css

screen.css

55 ms

SEO Factors

ww2.duracell.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ww2.duracell.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ww2.duracell.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.

Social Sharing Optimization

ww2.duracell.com

Open Graph data is detected on the main page of Ww 2 Duracell. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: