6.6 sec in total
215 ms
5.5 sec
893 ms
Click here to check amazing Fresh Pure content. Otherwise, check out these important facts you probably never knew about freshpure.com
Visit freshpure.comWe analyzed Freshpure.com page load time and found that the first response time was 215 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
freshpure.com performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value9.0 s
1/100
25%
Value9.6 s
11/100
10%
Value450 ms
63/100
30%
Value0.013
100/100
15%
Value9.2 s
32/100
10%
215 ms
1937 ms
249 ms
263 ms
253 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 88% of them (43 requests) were addressed to the original Freshpure.com, 4% (2 requests) were made to Googletagmanager.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Freshpure.com.
Page size can be reduced by 131.1 kB (67%)
196.2 kB
65.1 kB
In fact, the total size of Freshpure.com main page is 196.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. HTML takes 175.2 kB which makes up the majority of the site volume.
Potential reduce by 131.1 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 131.1 kB or 75% of the original size.
Potential reduce by 50 B
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.
Number of requests can be reduced by 23 (58%)
40
17
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fresh Pure. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
freshpure.com
215 ms
www.freshpure.com
1937 ms
styles.min.css
249 ms
magnific-popup.min.css
263 ms
core.min.css
253 ms
style.min.css
326 ms
css
60 ms
js
108 ms
et-core-unified-7.min.css
270 ms
mediaelementplayer-legacy.min.css
248 ms
wp-mediaelement.min.css
469 ms
jquery.min.js
469 ms
jquery-migrate.min.js
632 ms
magnific-popup.js
631 ms
main.min.js
705 ms
dtq-default-vb.js
711 ms
scripts.min.js
859 ms
jquery.fitvids.js
713 ms
jquery.mobile.js
802 ms
frontend-bundle.min.js
801 ms
common.js
883 ms
mediaelement-and-player.min.js
1422 ms
mediaelement-migrate.min.js
927 ms
wp-mediaelement.min.js
976 ms
analytics.js
161 ms
js
197 ms
preloader.gif
621 ms
Icons-pH.svg
288 ms
Border-DI.svg
294 ms
Icons-DI.svg
297 ms
Quotation.svg
290 ms
bottle_outline.svg
281 ms
bttf_container2.svg
301 ms
et-divi-dynamic-tb-484-tb-370-7-late.css
626 ms
modules.ttf
1180 ms
collect
108 ms
Border-RO.svg
1024 ms
Icons-RO.svg
1025 ms
Freshpure_Waters_Horizontal_Logo_Reverse_RGB.svg
1097 ms
swiggle-primary.svg
1172 ms
Dispenser-2-copy.svg
1164 ms
collect
35 ms
Border-ph.svg
1141 ms
bottle_outline.svg
1104 ms
Icons-pH.svg
1173 ms
Quotation.svg
1196 ms
Border-DI.svg
1288 ms
Icons-DI.svg
1312 ms
bttf_container2.svg
1292 ms
freshpure.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
freshpure.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
Page has valid source maps
freshpure.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
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 Freshpure.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 Freshpure.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.
freshpure.com
Open Graph description is not detected on the main page of Fresh Pure. 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: