1.3 sec in total
249 ms
897 ms
170 ms
Welcome to nalgene.com homepage info - get ready to check Nalgene best content for United States right away, or after learning these important things about nalgene.com
Nalgene has a water bottle for every lifestyle and every adventure. BPA free, durable and dishwasher safe.
Visit nalgene.comWe analyzed Nalgene.com page load time and found that the first response time was 249 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
nalgene.com performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value12.1 s
0/100
25%
Value4.1 s
80/100
10%
Value800 ms
36/100
30%
Value0.051
99/100
15%
Value18.0 s
3/100
10%
249 ms
69 ms
24 ms
33 ms
43 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 66% of them (42 requests) were addressed to the original Nalgene.com, 3% (2 requests) were made to Cm.g.doubleclick.net and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (251 ms) belongs to the original domain Nalgene.com.
Page size can be reduced by 822.4 kB (45%)
1.8 MB
991.1 kB
In fact, the total size of Nalgene.com main page is 1.8 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. Javascripts take 943.5 kB which makes up the majority of the site volume.
Potential reduce by 20.0 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 20.0 kB or 80% of the original size.
Potential reduce by 21.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. Nalgene images are well optimized though.
Potential reduce by 679.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 679.9 kB or 72% of the original size.
Potential reduce by 100.9 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. Nalgene.com needs all CSS files to be minified and compressed as it can save up to 100.9 kB or 77% of the original size.
Number of requests can be reduced by 35 (58%)
60
25
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nalgene. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
nalgene.com
249 ms
style.css
69 ms
satelliteLib-9f44369acc489b367840d1861e175d7e33abcd3f.js
24 ms
min-style.css
33 ms
thickbox.css
43 ms
jquery.1.4.3.js
87 ms
jquery-ui-1.8.5.custom.min.js
138 ms
jquery.ticker.min.js
39 ms
thickbox.js
84 ms
styles.css
53 ms
css
25 ms
genericons.css
85 ms
style.css
96 ms
comment-reply.min.js
83 ms
jquery.1.4.3.js
132 ms
jquery-ui-1.8.5.custom.min.js
157 ms
buttons.js
11 ms
public.css
88 ms
flexslider.css
87 ms
jquery.form.min.js
83 ms
scripts.js
83 ms
jquery.masonry.min.js
84 ms
functions.js
97 ms
jquery.flexslider-min.js
127 ms
jQuery.easing.min.js
99 ms
analytics.js
105 ms
s-code-contents-bffa348d12f5b898f5411b86338335e16cd453eb.js
89 ms
getAllAppDefault.esi
14 ms
logo.jpg
57 ms
NavBar_01.png
57 ms
NavBar_05.png
58 ms
NavBar_02.png
59 ms
NavBar_04.png
59 ms
mobileMenu.png
59 ms
15_NAL_FYI_Slider-940x457.jpg
83 ms
15NAL_NalgeneHomepage_SliderImage_Coupon-940x457.jpg
60 ms
drinkup_slider_updated111015-940x457.jpg
67 ms
home11-940x457.jpg
80 ms
15_NAL_FYI_SliderMobile.jpg
79 ms
15NAL_NalgeneMobile_SliderImage_Coupon.jpg
66 ms
15NAL_NalgeneMobile_Slider_GetHydrated.jpg
67 ms
15NAL_NalgeneMobile_Slider_MixItUp.jpg
82 ms
facebook.gif
84 ms
twitter.gif
83 ms
instagram.gif
92 ms
pinterest.gif
93 ms
loadingAnimation.gif
251 ms
collect
27 ms
collect
65 ms
getSegment.php
169 ms
checkOAuth.esi
18 ms
bg_direction_nav.png
46 ms
t.dhj
62 ms
s76502615902572
90 ms
t.dhj
28 ms
cm
28 ms
s-3271.xgi
9 ms
9 ms
13 ms
hbpix
37 ms
pixel
25 ms
xrefid.xgi
7 ms
pixel
15 ms
2981
23 ms
nalgene.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 input fields do not have accessible names
ARIA IDs are not unique
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
Buttons do not have an accessible name
Links do not have a discernible name
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
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>).
nalgene.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
nalgene.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nalgene.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 Nalgene.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.
nalgene.com
Open Graph description is not detected on the main page of Nalgene. 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: