4.8 sec in total
157 ms
3.9 sec
795 ms
Click here to check amazing Lithia Spring Water content. Otherwise, check out these important facts you probably never knew about lithiaspringwater.com
Boosting health since 1888 Lithia Spring Water® is a rare nutrient-rich alkaline spring water enriched with Lithium, trace minerals, elements, ionic electrolytes.
Visit lithiaspringwater.comWe analyzed Lithiaspringwater.com page load time and found that the first response time was 157 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
lithiaspringwater.com performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value11.4 s
0/100
25%
Value6.3 s
41/100
10%
Value1,190 ms
21/100
30%
Value0.407
24/100
15%
Value10.3 s
25/100
10%
157 ms
261 ms
60 ms
237 ms
177 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 71% of them (56 requests) were addressed to the original Lithiaspringwater.com, 9% (7 requests) were made to Fonts.gstatic.com and 4% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Lithiaspringwater.com.
Page size can be reduced by 295.2 kB (8%)
3.9 MB
3.6 MB
In fact, the total size of Lithiaspringwater.com main page is 3.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. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 32.2 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 7.7 kB, which is 18% 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 32.2 kB or 77% of the original size.
Potential reduce by 252.0 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. Lithia Spring Water images are well optimized though.
Potential reduce by 5.8 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. This website has mostly compressed JavaScripts.
Potential reduce by 5.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. Lithiaspringwater.com has all CSS files already compressed.
Number of requests can be reduced by 26 (39%)
66
40
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lithia Spring Water. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
lithiaspringwater.com
157 ms
lithiaspringwater.com
261 ms
responsive.css
60 ms
bootstrap.css
237 ms
style.css
177 ms
bootstrap.css
183 ms
style.css
180 ms
camera.css
179 ms
font-awesome.css
188 ms
touchTouch.css
235 ms
jquery.js
243 ms
jquery-migrate-1.2.1.min.js
242 ms
superfish.js
243 ms
jquery.easing.1.3.js
243 ms
jquery.mobilemenu.js
294 ms
jquery.ui.totop.js
294 ms
jquery.equalheights.js
295 ms
camera.js
298 ms
jquery.mobile.customized.min.js
299 ms
js
61 ms
freshwidget.js
14 ms
widget.js
32 ms
bootstrap.min.js
300 ms
tm-scripts.js
351 ms
price-table.css
178 ms
css
24 ms
css
34 ms
css
40 ms
logonew1.png
253 ms
menu-marker.png
99 ms
251263774
210 ms
227519532
215 ms
analytics.js
96 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
123 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
123 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
124 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
123 ms
feature.png
125 ms
img87.jpg
398 ms
img88.jpg
227 ms
img89.jpg
201 ms
img72.jpg
201 ms
img73.jpg
224 ms
img74.jpg
338 ms
page1_pic2.jpg
285 ms
page1_pic3.jpg
290 ms
page1_pic7a.jpg
341 ms
img71a.jpg
466 ms
img72a.jpg
402 ms
img73a.jpg
407 ms
img2b.jpg
454 ms
page1_pic5.jpg
457 ms
img68.jpg
514 ms
img57A.jpg
460 ms
img57C.jpg
466 ms
img57B.jpg
571 ms
img18mid.jpg
575 ms
lithiaspringwaterlogorefresh.png
577 ms
bg_pic2.jpg
2887 ms
freshwidget.css
95 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjo0oSmb2Rm.ttf
82 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjojISmb2Rm.ttf
81 ms
BngbUXZYTXPIvIBgJJSb6s3BzlRRfKOFbvjoa4Omb2Rm.ttf
82 ms
fontawesome-webfont.woff
485 ms
collect
78 ms
677571126-963b3723c80ee96913c075499156a482318cd54a7ae5dc88f2e80f523152b759-d
20 ms
menu-marker2.png
377 ms
prev.png
389 ms
next.png
435 ms
camera-loader.gif
435 ms
picture10.jpg
786 ms
collect
33 ms
647348491-da8c665e17f6a7ac5edc8b40ba0e18ae514f0864d27cdf784ed96dd1ebc13b2c-d
10 ms
ga-audiences
34 ms
picture4.jpg
349 ms
top.png
59 ms
supportbuttonsmallA.png
60 ms
loading.html
19 ms
supportbuttonsmallA.png
60 ms
lithiaspringwater.com 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.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
lithiaspringwater.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
lithiaspringwater.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 Lithiaspringwater.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 Lithiaspringwater.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.
lithiaspringwater.com
Open Graph description is not detected on the main page of Lithia Spring Water. 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: