3 sec in total
126 ms
2.4 sec
463 ms
Welcome to pur.com homepage info - get ready to check PUR best content for United States right away, or after learning these important things about pur.com
PUR filtration makes filtering tap water easy
Visit pur.comWe analyzed Pur.com page load time and found that the first response time was 126 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
pur.com performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value16.2 s
0/100
25%
Value16.1 s
0/100
10%
Value7,870 ms
0/100
30%
Value0.011
100/100
15%
Value37.4 s
0/100
10%
126 ms
1142 ms
106 ms
107 ms
102 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 59% of them (46 requests) were addressed to the original Pur.com, 12% (9 requests) were made to and 3% (2 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Pur.com.
Page size can be reduced by 476.0 kB (23%)
2.0 MB
1.6 MB
In fact, the total size of Pur.com main page is 2.0 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. 50% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 27.8 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 27.8 kB or 75% of the original size.
Potential reduce by 121.8 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. PUR images are well optimized though.
Potential reduce by 123.9 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 123.9 kB or 70% of the original size.
Potential reduce by 202.5 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. Pur.com needs all CSS files to be minified and compressed as it can save up to 202.5 kB or 81% of the original size.
Number of requests can be reduced by 25 (40%)
62
37
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PUR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
pur.com
126 ms
www.pur.com
1142 ms
css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css
106 ms
css__LeQxW73LSYscb1O__H6f-j_jdAzhZBaesGL19KEB6U.css
107 ms
css_3CipKsIyR_a44djIKpN36C99fuF0JBoTxWRbv_uwTqc.css
102 ms
css_iJmzJFz7yuQAJsBNhqqF7Ctyoko1ydBiMUviVE44Qrg.css
92 ms
193c593e-7667-4e73-ba2e-4b5d320e140f.css
60 ms
bootstrap.min.css
6 ms
css_qPF2ynre1KaxKMlw31T_597na4Ibq5O8Ca1VpaFgIJo.css
95 ms
jquery.min.js
33 ms
js_3TykeRWpejhD4-J3vdlaNXdULg9xhOZhbsppK0o2bUs.js
148 ms
jquery-ui.min.js
55 ms
js_yAicZujtqUhpCyuBiQyVA1uGwMX8V0A0ym_4Jb35kBQ.js
193 ms
bootstrap.min.js
14 ms
js_xIea6GlElRO_RuZ4Hiwwd2qd6_9b6zj6CsA9Xzbt_5k.js
193 ms
js_lOFYmvpVUooLpbgqmQ-ASON8F4h99UzX8RL1vzhqHgQ.js
220 ms
js_4LZNBFcM47PGDBbGYL2rC5t7UVuIR4deGvmkWSwDGzI.js
185 ms
js_JxE7T8sGoE-ZgdmSd1wA2uoa_ON3iR_5CHnPBBBcDtg.js
199 ms
901c7c9a-fade-4141-be72-1e67a1a13ab7.css
55 ms
rjr4snx.js
54 ms
js_B2uv6dkjoYobfQVyuXdchgrpnnx4oM0TkP_bDVf8Qrg.js
314 ms
analytics.js
102 ms
v.gif
143 ms
activityi;src=962105;type=purdi0;cat=homep0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=9430867568589.746
140 ms
gtm.js
98 ms
redirect
159 ms
pur-home-header-main.png
436 ms
logo-white.png
138 ms
search.png
239 ms
faucet_filters_thumb.png
246 ms
pitchers_thumb.png
239 ms
replacement_filters_thumb.png
249 ms
maxion_background.png
451 ms
maxion_logo.png
430 ms
why_filter_bg.png
429 ms
contaminants.png
380 ms
health.png
399 ms
cleaner.png
511 ms
savings.png
519 ms
info-box-bg.png
647 ms
click-call-help.png
575 ms
pur-savings.png
596 ms
twitter.png
537 ms
google-plus.png
607 ms
facebook.png
612 ms
youtube.png
629 ms
terracycle.png
704 ms
nsf.png
725 ms
water_quality.png
734 ms
ff.png
702 ms
p.png
722 ms
rf.png
739 ms
tw.png
801 ms
fb.png
797 ms
gp.png
813 ms
yt.png
813 ms
d
302 ms
iu3
42 ms
din-light.ttf
804 ms
nobel-light.ttf
875 ms
collect
35 ms
activityi;src=4279183;type=home-571;cat=home_820;ord=4465755095775;~oref=http%3A%2F%2Fwww.pur.com%2F
41 ms
iui3
33 ms
chip=cf4e1b20c1b50132ff3d0024e87a30c2.gif
223 ms
18 ms
20 ms
19 ms
J5hoksmmmGqa6WaYaZbZ5phrnvkWWGiRxZZYapnlVlhpldXWWBsnZ70NNtpksy222ma7HXbaZbc99tpnvwMOOuSwI4465rgTspx0ymlnnHUuO00uuuSyK6665robbrrltjvuuue+Bx565LEnnnrmuRdeeuW1N97+70n+DowVtKc=
15 ms
Q4r5n36AAAA
14 ms
Z70NNtpksy222ma7HXbaZbc99tpnvwMOOuSwI7IcdcxxJ5x0ymlnnHUu+5tcdMllV1x1zXU33HTLbXfcdc99Dzz0yGNPPPXMcy+89Mprb7z9DivmffoAAAA=
13 ms
Aw465LAjshx1zHEnnHTKaWecdS77m1x0yWVXXHXNdTfcdMttd9x1z30PPPTIY0889cxzL7z0ymtvvP0OK+Z9+gAAAA==
12 ms
Z70NNtpksy222ma7HXbaZbc99tpnvwMOOuSwI7IcdcxxJ5x0ymlnnHUu+5tcdMllV1x1zXU33HTLbXfcdc99Dzz0yGNPPPXMcy+89Mprb7z9DivmffoAAAA=
11 ms
Q4r5n36AAAA
10 ms
Z70NNtpksy222ma7HXbaZbc99tpnvwMOOuSwI7IcdcxxJ5x0ymlnnHUu+5tcdMllV1x1zXU33HTLbXfcdc99Dzz0yGNPPPXMcy+89Mprb7z9DivmffoAAAA=
8 ms
Z70NNtpksy222ma7HXbaZbc99tpnvwMOOuSwI7IcdcxxJ5x0ymlnnHUu+5tcdMllV1x1zXU33HTLbXfcdc99Dzz0yGNPPPXMcy+89Mprb7z9DivmffoAAAA=
8 ms
Z70NNtpksy222ma7HXbaZbc99tpnvwMOOuSwI7IcdcxxJ5x0ymlnnHUu+5tcdMllV1x1zXU33HTLbXfcdc99Dzz0yGNPPPXMcy+89Mprb7z9DivmffoAAAA=
8 ms
demconf.jpg
5 ms
p.gif
116 ms
pur.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
button, link, and menuitem elements do not have accessible names.
ARIA input fields do not have accessible names
ARIA IDs are not unique
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
[id] attributes on active, focusable elements are not unique
Some elements have a [tabindex] value greater than 0
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
pur.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
pur.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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pur.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 Pur.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.
pur.com
Open Graph description is not detected on the main page of PUR. 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: