2.1 sec in total
407 ms
1.5 sec
135 ms
Visit pureleaf.com now to see the best up-to-date Pure Leaf content for United States and also check out these interesting facts you probably never knew about pureleaf.com
Pure Leaf Iced Tea
Visit pureleaf.comWe analyzed Pureleaf.com page load time and found that the first response time was 407 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
pureleaf.com performance score
name
value
score
weighting
Value4.3 s
17/100
10%
Value5.3 s
22/100
25%
Value4.3 s
75/100
10%
Value1,200 ms
20/100
30%
Value0.075
95/100
15%
Value13.0 s
12/100
10%
407 ms
16 ms
74 ms
253 ms
36 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pureleaf.com, 33% (23 requests) were made to Static.tumblr.com and 20% (14 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (650 ms) relates to the external source 40.media.tumblr.com.
Page size can be reduced by 851.3 kB (16%)
5.5 MB
4.6 MB
In fact, the total size of Pureleaf.com main page is 5.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 63.4 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 8.4 kB, which is 11% 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 63.4 kB or 83% of the original size.
Potential reduce by 126.5 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. Pure Leaf images are well optimized though.
Potential reduce by 525.6 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 525.6 kB or 66% of the original size.
Potential reduce by 135.8 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. Pureleaf.com needs all CSS files to be minified and compressed as it can save up to 135.8 kB or 85% of the original size.
Number of requests can be reduced by 29 (52%)
56
27
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pure Leaf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
pureleaf.com
407 ms
pre_tumblelog.js
16 ms
bootstrap.min.css
74 ms
minimal_v2_min.css
253 ms
main-1.21.16.css
36 ms
byn3yyq.js
241 ms
jquery.1.11.1.min.js
42 ms
bootstrap.3.2.0.min.js
32 ms
imagesloaded.3.1.8.min.js
28 ms
modernizr.2.8.2.js
38 ms
jquery.infinitescroll.2.0.2.min.js
29 ms
jquery.photoset-grid.min.js
32 ms
shuffle.2.1.2.min.js
40 ms
hammer.1.1.3.min.js
46 ms
jquery.hammer.1.1.3.min.js
36 ms
carousel.nav.js
37 ms
footer.nav.js
37 ms
social.templates.js
41 ms
social.links-01.22.16.js
42 ms
grid.manager.js
39 ms
main-1.21.16.js
41 ms
tumblelog_post_message_queue.js
9 ms
stylesheet.css
9 ms
index.js
12 ms
pureleaf.com
141 ms
analytics.js
119 ms
nav-logo.jpg
118 ms
tumblr_o3dloxCgQh1ttc8c3o1_500.png
126 ms
like_iframe.html
122 ms
tumblr_o3dlfwuTnM1ttc8c3o1_500.png
372 ms
tumblr_o3dlchYPSZ1ttc8c3o1_500.png
448 ms
tumblr_o3dkvklsVT1ttc8c3o1_500.png
595 ms
tumblr_o3dkzhnWtQ1ttc8c3o1_500.png
594 ms
tumblr_o3dkohefOB1ttc8c3o1_500.png
580 ms
tumblr_o1vt7oaUX21ttc8c3o1_500.png
650 ms
tumblr_o1vteodcH71ttc8c3o1_500.png
593 ms
sprite-8.28.png
115 ms
hero_slide_1_2016.jpg
118 ms
panel_1_pure_leaf_unsweet_m.jpg
116 ms
hero_slide_2_2016_v1.jpg
120 ms
panel_2_pure_leaf_thc_m_v1.jpg
118 ms
tumblr_o3dl7psPx41ttc8c3o1_500.png
119 ms
tumblr_o1vt3mrXGj1ttc8c3o1_500.png
116 ms
impixu
132 ms
impixu
37 ms
ajax-loader.gif
36 ms
analytics.html
78 ms
login_check.html
20 ms
TYTen-sUS8BYc3zqyABV01AmPUhe5CIgD_qN3UivXG3ff4kfggMWeMJ6Mk6g5MFfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
40 ms
n10zCbjtfC3srjo7uxXwL8GQD0giMPgAvLfKDx3FF7bffJhRgsMWeMJ6Mk6g5Msfb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
77 ms
VkvbSgA3MtCZgNPhq51cl7TgndDyMcoGMlcdF5uhM-CffwQHggMWeMJ6Mk6g5Mifb2iRZeFKF2sKZQsyFhsK526aFhZcjQmRw2M3FhJtZebtFRmKwh4KjDwtwD6DwAZ8wcmywQSaZRjkwR9ajQqU5QI.woff
106 ms
DtGi3u243NNTMcySLTceq2_f3cQeXmF1_DMCFR7EPz9ffFKUgsMWeMJ6Mk6f5Mt.woff
145 ms
FIG9k8zP40jIfi_VYHJeg6SZcr9CUT33yU_p45fniFvffFfUgsMWeMJ6Mk6f5gI.woff
137 ms
uqyX8XkT7Dz4S__AHeIt_EiT1ekK9JhGIASOxZJVF7MffFpUgsMWeMJ6Mk6f5Mb.woff
137 ms
ctr31cwneEDqRvDDGHSM47PYXMwVOcgVD4B2W_iyrVtffwrUgsMWeMJ6Mk6f5MS.woff
143 ms
UhLh0vgt7HMKGsAYDiBD1d3EEl2gXear1KAmf2wEzkbff5pCMUMWeMJ6Mk6f5Mt.woff
144 ms
Ur75HYCgRDQY38s4VH7rKvhJMp8RMxBRjh4jDLfmLNtff5kCMUMWeMJ6Mk6f5gI.woff
143 ms
z-Sn3JB4mkGq2uEEa250qyO4-K6tPjYRoEXgLNMqprIff5KCMUMWeMJ6Mk6f5Mb.woff
180 ms
JnTLefQ6nWoDkdE3SyIfjpoz_NppNMQ7at-4uTpckVXff50CMUMWeMJ6Mk6f5MS.woff
180 ms
sWZz9XidAdDP9rXponSkhb6DwOG_zvP10NJzpjPYvaIff5hCMUMWeMJ6Mk6f5Mq.woff
180 ms
collect
16 ms
rapid-3.36.js
30 ms
rapidworker-1.2.js
36 ms
ga.js
50 ms
analytics.js
67 ms
cs.js
76 ms
__utm.gif
17 ms
p.gif
119 ms
cedexis.radar.js
20 ms
pureleaf.com accessibility score
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
pureleaf.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
Issues were logged in the Issues panel in Chrome Devtools
pureleaf.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
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 Pureleaf.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 Pureleaf.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.
pureleaf.com
Open Graph data is detected on the main page of Pure Leaf. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: