1.6 sec in total
157 ms
1.1 sec
294 ms
Click here to check amazing Hi Tea content. Otherwise, check out these important facts you probably never knew about hitea.com
Since 1995, Hawaiian Islands Tea has been producing flavorful tropical teas. We blend, flavor and package our green tea, black tea and herbal tea in Hawaii.
Visit hitea.comWe analyzed Hitea.com page load time and found that the first response time was 157 ms and then it took 1.4 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.
hitea.com performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value12.0 s
0/100
25%
Value17.2 s
0/100
10%
Value32,400 ms
0/100
30%
Value0.098
90/100
15%
Value41.7 s
0/100
10%
157 ms
478 ms
45 ms
16 ms
51 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hitea.com, 43% (32 requests) were made to Cdn2.bigcommerce.com and 26% (19 requests) were made to Cdn4.bigcommerce.com. The less responsive or slowest element that took the longest time to load (478 ms) relates to the external source Hawaiicoffeecompany.com.
Page size can be reduced by 300.6 kB (19%)
1.6 MB
1.3 MB
In fact, the total size of Hitea.com main page is 1.6 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. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 26.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. This page needs HTML code to be minified as it can gain 5.1 kB, which is 16% 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 26.0 kB or 81% of the original size.
Potential reduce by 39.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. Hi Tea images are well optimized though.
Potential reduce by 191.3 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 191.3 kB or 70% of the original size.
Potential reduce by 43.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. Hitea.com needs all CSS files to be minified and compressed as it can save up to 43.9 kB or 80% of the original size.
Number of requests can be reduced by 38 (53%)
72
34
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hi Tea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
hitea.com
157 ms
478 ms
css
45 ms
styles.css
16 ms
styles.css
51 ms
iselector.css
19 ms
flexslider.css
18 ms
slide-show.css
53 ms
styles-slide-show.css
18 ms
social.css
47 ms
white.css
47 ms
imodal.css
53 ms
product.attributes.css
50 ms
ui.all.css
44 ms
product.quickview.css
44 ms
jquery.min.js
77 ms
menudrop.js
49 ms
common.js
44 ms
iselector.js
49 ms
jquery.autobox.js
44 ms
init.js
43 ms
imagesLoaded.js
48 ms
imodal.js
40 ms
jquery-ui.min.js
96 ms
jquery.validate.js
40 ms
product.functions.js
51 ms
product.attributes.js
51 ms
quickview.js
51 ms
quickview.initialise.js
49 ms
quicksearch.js
50 ms
simpletabs_1.3.js
132 ms
simpletabs.css
161 ms
dc.js
47 ms
analytics.min.js
46 ms
beacon_api.js
21 ms
__utm.gif
30 ms
ajax-loader.gif
60 ms
HCC30px.png
59 ms
hdr-hawaiitea.png
98 ms
300px-tea-1.png
61 ms
300px-tea-2.png
62 ms
300px-tea-3.png
81 ms
category-tea-blacktea.png
83 ms
category-tea-greentea.png
61 ms
category-tea-rooibos.png
83 ms
category-tea-gifts.png
80 ms
category-commercial-tea.png
80 ms
category-tea-club.png
91 ms
category-blank.gif
90 ms
icon-heart.png
89 ms
fornax.min.js
43 ms
ts1
71 ms
ico-phone.png
43 ms
ico-cart.png
41 ms
best-tea-1.gif
44 ms
best-tea-2.gif
50 ms
best-tea-3.gif
53 ms
best-tea-4.gif
54 ms
best-tea-5.gif
55 ms
best-tea-6.gif
54 ms
best-tea-7.gif
55 ms
best-tea-8.gif
56 ms
best-tea-9.gif
57 ms
best-tea-10.gif
58 ms
best-tea-11.gif
59 ms
best-tea-12.gif
59 ms
best-tea-13.gif
60 ms
best-tea-14.gif
61 ms
best-tea-15.gif
62 ms
best-tea-16.gif
64 ms
sprite-social-default.png
26 ms
dotted.gif
105 ms
footerbgtea.png
299 ms
ts.php
28 ms
hitea.com 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.
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
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
hitea.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
Missing source maps for large first-party JavaScript
hitea.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
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 Hitea.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 Hitea.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.
hitea.com
Open Graph description is not detected on the main page of Hi Tea. 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: