5.5 sec in total
664 ms
4.6 sec
236 ms
Click here to check amazing EN Eloop content. Otherwise, check out these important facts you probably never knew about eneloop.com
Welcome to the global website for Panasonic eneloop rechargeable batteries.
Visit eneloop.comWe analyzed Eneloop.com page load time and found that the first response time was 664 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
eneloop.com performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value14.4 s
0/100
25%
Value8.8 s
15/100
10%
Value260 ms
83/100
30%
Value0.675
8/100
15%
Value11.2 s
20/100
10%
664 ms
412 ms
304 ms
55 ms
316 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Eneloop.com, 55% (63 requests) were made to Panasonic.net and 18% (21 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Panasonic.net.
Page size can be reduced by 884.7 kB (35%)
2.5 MB
1.6 MB
In fact, the total size of Eneloop.com main page is 2.5 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 1.4 MB which makes up the majority of the site volume.
Potential reduce by 26.6 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 26.6 kB or 82% of the original size.
Potential reduce by 3.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. EN Eloop images are well optimized though.
Potential reduce by 683.1 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 683.1 kB or 74% of the original size.
Potential reduce by 171.3 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. Eneloop.com needs all CSS files to be minified and compressed as it can save up to 171.3 kB or 88% of the original size.
Number of requests can be reduced by 54 (49%)
111
57
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EN Eloop. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
eneloop.com
664 ms
412 ms
ga2012_base.css
304 ms
ga2012_googleAnalytics.js
55 ms
ga2012_jquery.js
316 ms
ga2012_jquery.cookie.js
449 ms
ga2012_base.js
295 ms
ga2012_bottomlink.js
289 ms
ga2012_countrySelect_setting.js
290 ms
ga2012_countrySelect.js
564 ms
ms-common.js
527 ms
global-base.css
567 ms
areacountry-data.js
43 ms
jquery.js
678 ms
jquery-ui.js
608 ms
global-base.js
710 ms
pulldown.js
783 ms
jquery.bxslider.css
806 ms
common.css
830 ms
module.css
869 ms
local.css
912 ms
smartRollover.js
944 ms
slide_menu.js
1013 ms
pagetop.js
1053 ms
jquery-1.8.2.min.js
1127 ms
jquery.bxslider.js
1155 ms
heightLine.js
1155 ms
suggest_ext.js
497 ms
ga.js
11 ms
__utm.gif
12 ms
bg-overall-shadow-dark.gif
506 ms
img-nav-global-1px.png
276 ms
lgo-nav-global-panasonic.png
280 ms
img-nav-global-search-cap-left.png
254 ms
img-nav-global-search-cap-right-bg.png
255 ms
img-nav-global-search-1px.png
259 ms
img-nav-global-search-cap-right.png
95 ms
slideimg_10th.jpg
628 ms
slideimg_sp_10th.jpg
719 ms
slideimg_solarstorage.jpg
719 ms
slideimg_sp_solarstorage.jpg
719 ms
slideimg_b1.jpg
717 ms
slideimg_sp_b1.jpg
718 ms
slideimg_a1.jpg
755 ms
slideimg_sp_a1.jpg
954 ms
slideimg_b2.jpg
1001 ms
slideimg_sp_b2.jpg
1151 ms
slideimg_a2.jpg
1081 ms
slideimg_sp_a2.jpg
1009 ms
btn_mainarea01.jpg
1057 ms
btn_mainarea02.jpg
1249 ms
btn01.jpg
1312 ms
btn02.jpg
1313 ms
btn03.jpg
1355 ms
btn04.jpg
1368 ms
bnr01.jpg
1430 ms
bnr02.jpg
1523 ms
bnr03.jpg
1581 ms
icn-print.gif
1585 ms
icn-footer-arrow-up.gif
1600 ms
icn-close.gif
1614 ms
pagetop.gif
1683 ms
jqueryg.min.js
638 ms
jsonp.min.js
252 ms
yahoo-min.js
561 ms
dom-min.js
606 ms
initJSONPSuggest.js
599 ms
view.js
599 ms
OpenSans-CondBold-webfont.svg
1817 ms
OpenSans-CondBold-webfont.woff
1847 ms
likebox.php
293 ms
likebox.php
257 ms
likebox.php
317 ms
ebiMDO3r-8l.css
62 ms
jGc-59L_9lo.css
44 ms
6qHpHChjY_J.css
33 ms
ztINr5qMqM_.css
34 ms
uVjHKJ0glvg.css
48 ms
q68gy-v_YMF.js
70 ms
FJmpeSpHpjS.js
68 ms
0wM5s1Khldu.js
102 ms
1bNoFZUdlYZ.js
100 ms
njO1TPvGzoR.js
106 ms
1QuX41zDRrx.js
100 ms
Oagsvfb4VWi.js
100 ms
LTv6ZK-5zxz.js
112 ms
1FCa-btixu2.js
111 ms
12705487_1064831956891612_2020621590004247150_n.jpg
167 ms
I6-MnjEovm5.js
76 ms
pQrUxxo5oQp.js
74 ms
1173798_591696894205123_1660564224_n.png
58 ms
1915032_959414277440095_403398315206262718_n.jpg
67 ms
12814274_959414384106751_7659792363062084167_n.jpg
69 ms
10703935_959414247440098_8670947133516251388_n.jpg
68 ms
10398094_959414294106760_1804202679410453341_n.jpg
69 ms
1557590_959193580795498_4420033642406353705_n.jpg
73 ms
1933793_959193587462164_1016560248003118279_n.jpg
70 ms
12804859_959193577462165_200086747695743865_n.jpg
69 ms
12143121_959193674128822_214477408393714294_n.jpg
70 ms
1097939_959106957470827_6592941675644890191_n.jpg
71 ms
1010340_959106964137493_7511080562494981243_n.jpg
70 ms
7472_959106970804159_5512541767668877963_n.jpg
71 ms
12790970_959107047470818_7517886125545415073_n.jpg
71 ms
12705622_1074457749262366_3916163447910451834_n.jpg
71 ms
1924026_957816600933196_5703288402319571677_n.png
71 ms
wL6VQj7Ab77.png
51 ms
s7jcwEQH7Sx.png
51 ms
QDwYpIaRyfG.png
56 ms
sSwLTfB7PfP.png
55 ms
K00K-UgnsKu.png
64 ms
ga2012_blank.gif
1157 ms
bx_loader.gif
1324 ms
pager.png
1179 ms
ga2012_print.css
297 ms
eneloop.com accessibility score
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
Links do not have a discernible name
eneloop.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
Missing source maps for large first-party JavaScript
eneloop.com 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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eneloop.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 Eneloop.com main page’s claimed encoding is iso-8859-1. 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.
eneloop.com
Open Graph description is not detected on the main page of EN Eloop. 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: