9.6 sec in total
1.1 sec
7.1 sec
1.4 sec
Welcome to lifestraw.com homepage info - get ready to check Life Straw best content for United States right away, or after learning these important things about lifestraw.com
Everyone deserves access to safe drinking water. Our products provide the highest protection from unsafe water and positively impact on people and planet.
Visit lifestraw.comWe analyzed Lifestraw.com page load time and found that the first response time was 1.1 sec and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lifestraw.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value11.1 s
0/100
25%
Value10.7 s
7/100
10%
Value4,010 ms
1/100
30%
Value0
100/100
15%
Value23.7 s
1/100
10%
1145 ms
186 ms
187 ms
185 ms
187 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 93% of them (77 requests) were addressed to the original Lifestraw.com, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to S0.wp.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Lifestraw.com.
Page size can be reduced by 933.0 kB (25%)
3.7 MB
2.8 MB
In fact, the total size of Lifestraw.com main page is 3.7 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. 65% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 349.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. 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 349.9 kB or 83% of the original size.
Potential reduce by 6.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. Life Straw images are well optimized though.
Potential reduce by 288.4 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 288.4 kB or 70% of the original size.
Potential reduce by 288.2 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. Lifestraw.com needs all CSS files to be minified and compressed as it can save up to 288.2 kB or 84% of the original size.
Number of requests can be reduced by 43 (58%)
74
31
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Life Straw. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 22 to 1 for CSS and as a result speed up the page load time.
lifestraw.com
1145 ms
language-selector.css
186 ms
navigation.css
187 ms
cms-navigation-base.css
185 ms
cms-navigation.css
187 ms
polyfill.object-fit.css
188 ms
style.min.css
647 ms
jetpack.css
463 ms
prefixfree.min.js
284 ms
jquery.js
554 ms
jquery-migrate.min.js
284 ms
jquery.cookie.js
366 ms
browser-redirect.js
370 ms
wp-emoji-release.min.js
356 ms
formreset.min.css
186 ms
formsmain.min.css
495 ms
readyclass.min.css
279 ms
browsers.min.css
282 ms
devicepx-jetpack.js
12 ms
Chart.min.js
504 ms
jquery.flexslider.js
505 ms
jquery.waypoints.min.js
493 ms
jquery.cookie.min.js
504 ms
jquery.magnific-popup.min.js
505 ms
plugins.js
505 ms
app.min.js
505 ms
ajax-pagination.js
505 ms
wp-embed.min.js
505 ms
sitepress.js
559 ms
jquery.json.js
578 ms
gravityforms.min.js
579 ms
placeholders.jquery.min.js
579 ms
e-201611.js
7 ms
analytics.js
116 ms
LifestrawSteel-Masked-sm1.png
139 ms
Lifestraw-Masked-sm1.png
138 ms
LifestrawMission-Masked-sm1.png
306 ms
LifestrawGo-Masked-sm1.png
304 ms
LifestrawFamily-Masked-sm1.png
305 ms
LifestrawCC-Masked-sm1.png
490 ms
logo-header--black.png
302 ms
IMG_6752-Edit-e1452000082737.jpg
5366 ms
lifestyle-rollover-lifestraw-new1.png
320 ms
lifestyle-rollover-lifestraw.png
400 ms
lifestyle-rollover-mission-copy.png
401 ms
lifestyle-rollover-lifestrawgo.png
480 ms
lifestyle-rollover-family1.png
402 ms
lifestyle-rollover-carboncredit.png
493 ms
bg--ftl-interstitial.jpg
678 ms
10413853_907209079395339_496943120_n.jpg
589 ms
12558904_1723418777872136_185702127_n.jpg
664 ms
12501478_207205236294430_638374459_n.jpg
673 ms
10601808_874053662717125_1923617840_n.jpg
586 ms
press-bbc.jpg
679 ms
press-nytimes.jpg
682 ms
language-selector.css
757 ms
navigation.css
748 ms
cms-navigation-base.css
766 ms
cms-navigation.css
784 ms
polyfill.object-fit.css
800 ms
style.min.css
885 ms
jetpack.css
832 ms
press-cnn1.jpg
870 ms
press-fastcompany.jpg
870 ms
lifestraw-whiteboard.png
870 ms
OpenSans-Light.woff
956 ms
collect
55 ms
OpenSans-Regular.woff
897 ms
OpenSans-Bold.woff
883 ms
fontawesome-webfont.woff
884 ms
calibri-bold.woff
913 ms
calibri.woff
912 ms
freeland.woff
1075 ms
86 ms
icomoon.woff
770 ms
formreset.min.css
770 ms
formsmain.min.css
833 ms
g.gif
9 ms
readyclass.min.css
880 ms
browsers.min.css
894 ms
nav-arrow-down.png
844 ms
1-top.svg
95 ms
1-bottom.svg
96 ms
lifestraw.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
[aria-hidden="true"] elements contain focusable descendents
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Image elements do not have [alt] attributes
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>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lifestraw.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
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
lifestraw.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
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
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lifestraw.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 Lifestraw.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.
lifestraw.com
Open Graph data is detected on the main page of Life Straw. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: