1.3 sec in total
197 ms
725 ms
423 ms
Welcome to teaware.house homepage info - get ready to check Teaware best content for United States right away, or after learning these important things about teaware.house
Teaware.house has the best teaware selection anywhere: teapots, teacups, gaiwans, teapets, tea trays and all the tea accessories you need to brew gongfu tea.
Visit teaware.houseWe analyzed Teaware.house page load time and found that the first response time was 197 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.
teaware.house performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value8.3 s
2/100
25%
Value5.0 s
63/100
10%
Value380 ms
69/100
30%
Value0.716
7/100
15%
Value12.0 s
16/100
10%
197 ms
42 ms
44 ms
54 ms
43 ms
Our browser made a total of 42 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Teaware.house, 45% (19 requests) were made to Cdn.shopify.com and 12% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (227 ms) relates to the external source Api.instagram.com.
Page size can be reduced by 298.2 kB (13%)
2.2 MB
1.9 MB
In fact, the total size of Teaware.house main page is 2.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. 60% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 28.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.0 kB, which is 22% 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 28.4 kB or 79% of the original size.
Potential reduce by 10.4 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. Teaware images are well optimized though.
Potential reduce by 185.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 185.7 kB or 61% of the original size.
Potential reduce by 73.7 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. Teaware.house needs all CSS files to be minified and compressed as it can save up to 73.7 kB or 82% of the original size.
Number of requests can be reduced by 19 (54%)
35
16
The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Teaware. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
teaware.house
197 ms
css
42 ms
styles.scss.css
44 ms
jquery.min.js
54 ms
app.js
43 ms
cloudzoom.js
37 ms
option_selection-04f21dade47c181126ac61b64d757485f84671daadfa90e4956a522cda4c2948.js
33 ms
ga_urchin_forms-0826cdefee6590321eb5c0c435eeebf7a8425a5493a9e95059c40e07e069ad52.js
38 ms
shopify_stats.js
124 ms
trekkie.storefront.min.js
170 ms
shop_events_listener-dabe00038c134ebede3c66ef50bfdcedb847ac379226dfb9a22bbf438ac8dbef.js
124 ms
widgets.js
118 ms
join-our-newsletter.json
151 ms
search
227 ms
logo_home.png
40 ms
slideshow_1.jpg
195 ms
slideshow_2.jpg
126 ms
slideshow_3.jpg
124 ms
slideshow_4.jpg
124 ms
feature1.jpg
124 ms
feature2.jpg
122 ms
feature3.jpg
151 ms
cc-paypal-light.png
145 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
37 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
38 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
41 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
41 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
41 ms
OutOfTheSandbox.woff
143 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
89 ms
identify
136 ms
record.gif
76 ms
analytics.js
26 ms
syndication
117 ms
319998048782647298
131 ms
mailchimp_twh_popup_header.jpg
46 ms
collect
9 ms
collect
59 ms
page
89 ms
105 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
4 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
6 ms
teaware.house 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.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
teaware.house 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
teaware.house SEO score
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 Teaware.house 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 Teaware.house 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.
teaware.house
Open Graph data is detected on the main page of Teaware. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: