1.4 sec in total
139 ms
1 sec
252 ms
Visit espring.com now to see the best up-to-date ESpring content and also check out these interesting facts you probably never knew about espring.com
Discover the eSpring water purifier from Amway and how you can enjoy purified, quality water right at home. Learn about features, benefits, and more today!
Visit espring.comWe analyzed Espring.com page load time and found that the first response time was 139 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
espring.com performance score
name
value
score
weighting
Value7.1 s
2/100
10%
Value22.9 s
0/100
25%
Value14.5 s
1/100
10%
Value2,750 ms
4/100
30%
Value0.737
7/100
15%
Value31.0 s
0/100
10%
139 ms
331 ms
20 ms
12 ms
14 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Espring.com, 92% (57 requests) were made to Amway.com and 5% (3 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (331 ms) relates to the external source Amway.com.
Page size can be reduced by 1.9 MB (72%)
2.6 MB
745.8 kB
In fact, the total size of Espring.com main page is 2.6 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. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 64.5 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 19.1 kB, which is 24% 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 64.5 kB or 82% of the original size.
Potential reduce by 18.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. ESpring images are well optimized though.
Potential reduce by 1.2 MB
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.2 MB or 76% of the original size.
Potential reduce by 566.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. Espring.com needs all CSS files to be minified and compressed as it can save up to 566.0 kB or 85% of the original size.
Number of requests can be reduced by 31 (53%)
58
27
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ESpring. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
espring.com
139 ms
eSpring
331 ms
dtagent622_nr23_1019.js
20 ms
base.css
12 ms
print.css
14 ms
TeaLeafCfg.js
15 ms
TeaLeaf.js
14 ms
espring-landing-standard.css
168 ms
Head-min.js
42 ms
WebResource.axd
44 ms
WebResource.axd
44 ms
ScriptResource.axd
105 ms
prototype-core.ashx
104 ms
converter.ashx
102 ms
type.ashx
106 ms
WebResource.axd
42 ms
satelliteLib-2ea5493e9558ac89c44cdbd79d4b186865a28f3d.js
103 ms
Main-min.js
41 ms
reset.css
19 ms
product_management_base.css
20 ms
cart_management_base.css
30 ms
los_base.css
37 ms
user_management_base.css
40 ms
content_base.css
52 ms
icons.css
61 ms
espring-standard.css
92 ms
logo_amway_en.png
65 ms
logo-amway-greyscale.png
85 ms
bkg.button.sprite.gif
29 ms
ico_nav_pipe.gif
33 ms
lan_pop.png
30 ms
ico_sprite_right.gif
31 ms
nutrilite-megamenu-logo.jpg
30 ms
artistry-megamenu-logo.jpg
32 ms
eSpring-megamenu-logo.jpg
32 ms
espring-BE-overview-background.gif
89 ms
GBL_ESP_LANDING_T1_IMG_1.jpg
35 ms
heroNav_TileBorderRight.gif
31 ms
GBL_ESP_LANDING_T1_THUMB_1.jpg
32 ms
GBL_ESP_LANDING_T2_THUMB_1.jpg
33 ms
GBL_ESP_LANDING_T3_THUMB_1.jpg
37 ms
GBL_ESP_LANDING_T4_THUMB_1.jpg
33 ms
GBL_ESP_LANDING_T5_THUMB_1.jpg
34 ms
heroNav_TileShadow.gif
35 ms
BE_espring_bottomrule_390.png
34 ms
BE_espring_bottomrule_360.png
104 ms
GBL_ESP_PROMO_IMG_1.jpg
36 ms
GBL_ESP_PROMO_IMG_3.jpg
36 ms
GBL_ESP_PROMO_IMG_2.jpg
38 ms
GBL_ESP_PROMO_IMG_4.jpg
36 ms
GBL_ESP_SOCIAL_IMG_2.jpg
37 ms
BE_footer_background.gif
39 ms
footer_BBB_logo.gif
37 ms
footer_RSA_logo.gif
38 ms
footer_DB_logo.gif
40 ms
footer_IBOIA_logo.gif
49 ms
footer_DSA_logo.gif
39 ms
s-code-contents-afd4986fee5b6ac60664a557386d8f9de7d18abf.js
28 ms
ico_nav_arrowDown.gif
5 ms
404.aspx
72 ms
s57884421462658
8 ms
satellite-5474a7bf37643500187a0100.js
30 ms
espring.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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>).
espring.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
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
espring.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
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Espring.com 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 Espring.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.
espring.com
Open Graph description is not detected on the main page of ESpring. 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: