2 sec in total
127 ms
1.7 sec
269 ms
Visit teapeople.us now to see the best up-to-date Tea People content for United States and also check out these interesting facts you probably never knew about teapeople.us
Our mission at Tea People is to make tea approachable.
Visit teapeople.usWe analyzed Teapeople.us page load time and found that the first response time was 127 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
teapeople.us performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value12.4 s
0/100
25%
Value8.6 s
17/100
10%
Value580 ms
51/100
30%
Value0.001
100/100
15%
Value14.0 s
10/100
10%
127 ms
111 ms
133 ms
127 ms
136 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 5% of them (3 requests) were addressed to the original Teapeople.us, 51% (30 requests) were made to Use.typekit.net and 24% (14 requests) were made to Static1.squarespace.com. The less responsive or slowest element that took the longest time to load (576 ms) relates to the external source Use.typekit.net.
Page size can be reduced by 364.9 kB (31%)
1.2 MB
801.1 kB
In fact, the total size of Teapeople.us main page is 1.2 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. 70% of websites need less resources to load. Images take 672.4 kB which makes up the majority of the site volume.
Potential reduce by 100.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. 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 100.2 kB or 79% of the original size.
Potential reduce by 28.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. Tea People images are well optimized though.
Potential reduce by 236.7 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 236.7 kB or 65% of the original size.
Number of requests can be reduced by 15 (52%)
29
14
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tea People. 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 as a result speed up the page load time.
www.teapeople.us
127 ms
eTKnbWSFHCv29ZtGIA4hsjVBn4gOZ79R1HhRHAVs2L3fe0w2fFHN4UJLFRbh52jhWD9DjDwX52mqZQsKw2bk52SowhbtjQqDFsTLiaiaO1s8jWg8dagCZPouSkUXZAB3ZAN3de90iWwCdeNRjAUGdaFXOYs8jPu3ZAN3de90SaBujW48Sagyjh90jhNlOfG0iemyOWg8dagCZPoDSWmyScmDSeBRZPoRdhXK2YgkdayTdAIldcNhjPJbZ148-AiGifuDjAoDOWgkdkG4fHCgIMMjMPMfH6qJnMIbMg6OJMJ7fbRKHyMMeMw6MKG4f5w7IMMj2PMfH6qJn3IbMg6IJMJ7fbK3MsMMeMt6MKGHfO2IMsMMeM96MKGHfOYIMsMMeMv6MKG4fHXgIMMjgKMfH6qJn6IbMg6bJMJ7fbKOMsMMeMS6MKG4fJ3gIMMjIPMfH6qJ7bIbMg6JJMJ7fbK7MsMMegJ6MKG4fJqgIMMjfPMfH6qJK6IbMg6QJMJ7fbKb-sMgeMw6MKG4f4BTIMIj2PMfH6qJk89bMs6IJMJ7fbKF-sMgeMt6MKG4f44TIMIjgPMfH6qJqhqbMs6VJMJ7fbK9-sMgeMj6MKG4f4mTIMIjIfMfH6qJRcqbMs6YJMJ7fbKV-sMgegI6MKG4f4ZTIMIjfPMfH6qJ8hqbMs6QJMHbMiVf6OIB.js
111 ms
embed.js
133 ms
no-hover-on-scroll.js
127 ms
lazyload.js
136 ms
sticky.js
134 ms
centernav.js
147 ms
index-gallery.js
145 ms
site.js
144 ms
helpers.js
144 ms
authenticated.js
150 ms
www.teapeople.us
249 ms
common-3827d4107f55ae912a8c-min.js
72 ms
commerce-cf5ca5fa5feb9716f7f4-min.js
51 ms
commerce-7f4130fee43d9b486ac93410db2112d3-min.css
39 ms
site.css
29 ms
form-settings
75 ms
ga.js
68 ms
social-accounts.svg
52 ms
xh_HFQE_qiw2ZOCXpF45Zy2mZedkNlAawcJiDVV9LRJffF7AggMdeMJ6Mk6f5Mb.woff
314 ms
5DHgtgBjUCiHkhLJ7KhZALvJHXXc0-_vkht-ysoil4vffFkAggMdeMJ6Mk6f5M9.woff
314 ms
2rLS_N3GGI8WfQ2-DvjwJEWJ7z6VX7kJt_io66sHfFtffFKAggMdeMJ6Mk6f5Mw.woff
314 ms
EyRWEy9ydsJENU0MwD_atQd6kLc_Y9Q3TSPFqbiqKo9ffFEAggMdeMJ6Mk6f5Mj.woff
500 ms
CEH2DrwgjeDUdOMRehdELQOVrnM8ZVTg1FIMcxLsDdMff5fAggMdeMJ6Mk6f5MS.woff
502 ms
MuBiA0fDINwGm5MqXSK9aIEx18uz6NHHmEAYBynEWdwff5HAggMdeMJ6Mk6f5Mq.woff
575 ms
squarespace-ui-font.svg
311 ms
iFtCRXuGomJGndf054Mx1oyo2-w8vbrtQykkKmKtBuwffOeREN32IgCjMKM2HMJtg3.woff
575 ms
90Os1WQYOzXn14sPoPwvT94XnZ-Lj8cRawFxvbrkCRjffO5REN32IgCjMKM2HMJtfM.woff
576 ms
dgDiodgawpxOH-HxC7W9boSKPy4DOKMslSn8huYnjhXffHrREN32IgCjMKM2HMJtfb.woff
571 ms
sZqw0BeOokIUXxHaXeJCmT6us5b-fw1GREgUAYifXAqffO0REN32IgCjMKM2HMJtg6.woff
572 ms
Uuu7ewJv8n6WjLWtGzCNacF9ePSeJeV8Vtbh6GtoQ2JffOpREN32IgCjMKM2HMJtgb.woff
572 ms
ypvk_yI2b-_vul5TuOuCZyV2eGRIe_yhSVroliFb0uCffOcREN32IgCjMKM2HMJtgM.woff
576 ms
Zh5r25ARMZ8rfY1Piu1rM0PozEbdFcGLyXSqcZf6Yj6ffOAREN32IgCjMKM2HMJtM3.woff
576 ms
hCVvsRTUKDJOgMwfK8xY-zXLcnH34Yq5lKzYBDMehvtffOhREN32IgCjMKM2HMJtMb.woff
576 ms
RecordHit
560 ms
381 ms
count.js
327 ms
__utm.gif
119 ms
popup.js
271 ms
qmaKzj-INAJVvl17sVU9bx2-BZOq1_ck83YAuT8XAGqffFcAggMdeMJ6Mk6f5MX.woff
174 ms
bKCDtsrKI1m3xDTTnZygIiz6ATVMDQZTWxuBj0qlWOCffF0AggMdeMJ6Mk6f5Mt.woff
175 ms
vINZ9u5kDR_gbw03sZBCWSXQdPKBzfhGg_uTsJrym6CffFhAggMdeMJ6Mk6f5Mv.woff
177 ms
MpjIzDVwm-mIOENwNIZEiHd5n_1bS-eHlgPAebTnYBjffFrAggMdeMJ6Mk6f5gM.woff
241 ms
0zrX4aOtAlzJBY9mfN3wR7i5fNHHdqCUqMjJs1cY2xSff5eAggMdeMJ6Mk6f5gI.woff
241 ms
YrhtQ-0pAikdzUFNamiHbbpl88FGa67TyjAb456HM-Jff55AggMdeMJ6Mk6f5gw.woff
241 ms
eEz9g_9rffkCFnCz-m4hWBw7yz5s4qlfnmBYBBdZFrXffOEREN32IgCjMKM2HMJtf3.woff
240 ms
xqVP_NlehvgpJO5h_V34xXezRxrbA32DzQeKgbWOwj3ffO-REN32IgCjMKM2HMJt2b.woff
241 ms
0jy7OQTIhMkCdK0oczhImj9i8C3QSRmxfh6p5h-3G6qffO7REN32IgCjMKM2HMJt26.woff
241 ms
LMWHf8Ko-ZpX3JOMkwGuejjLtfAWzZgJ7aHnbMNm2GvffOKREN32IgCjMKM2HMJt23.woff
255 ms
pCd-eSxohJzlFG_mee9Rq96Hk8NChPkZPrZV8D98qnjffOkREN32IgCjMKM2HMJtIM.woff
255 ms
FPSxGKpQSYNMa2DaoLxRzUPuCX7OhtO9wpajvAWtLGwffOHREN32IgCjMKM2HMJtIb.woff
256 ms
6-De3LrFTse0zpnJGFz6DI-zD_WTbOTAHFg5VCDeVwjffOPREN32IgCjMKM2HMJtI6.woff
255 ms
Fgblcw2ZBBZyou4ZuGTbvANKw4T2df8EXLkIJ8nuzK3ffOfREN32IgCjMKM2HMJtI3.woff
255 ms
hp_promo_sourcing.jpg
167 ms
hp_promo_shop.jpg
112 ms
hp_promo_teaware2.jpg
83 ms
collect
156 ms
pinterest-e9d4ace67f203ae5895e-min.js
107 ms
hp_promo_labs.jpg
88 ms
teapeople.us 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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
teapeople.us 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
Registers an unload listener
Detected JavaScript libraries
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
teapeople.us 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 Teapeople.us 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 Teapeople.us 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.
teapeople.us
Open Graph data is detected on the main page of Tea People. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: