4.2 sec in total
87 ms
3.4 sec
695 ms
Click here to check amazing Teabox content for India. Otherwise, check out these important facts you probably never knew about teabox.com
Enjoy India's finest tea selection. Buy 100% fresh, delicious organic teas direct from the source. Free express shipping on orders above $75.
Visit teabox.comWe analyzed Teabox.com page load time and found that the first response time was 87 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
teabox.com performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value2.7 s
85/100
25%
Value9.5 s
12/100
10%
Value2,150 ms
6/100
30%
Value0.503
16/100
15%
Value18.3 s
3/100
10%
87 ms
186 ms
101 ms
189 ms
6 ms
Our browser made a total of 196 requests to load all elements on the main page. We found that 3% of them (5 requests) were addressed to the original Teabox.com, 24% (47 requests) were made to Cdn.teabox.com and 6% (12 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (861 ms) relates to the external source Ref-r.com.
Page size can be reduced by 1.1 MB (38%)
2.8 MB
1.7 MB
In fact, the total size of Teabox.com main page is 2.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. 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 1.3 MB which makes up the majority of the site volume.
Potential reduce by 253.8 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 33.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 253.8 kB or 82% of the original size.
Potential reduce by 25.2 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. Teabox images are well optimized though.
Potential reduce by 489.5 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 489.5 kB or 62% of the original size.
Potential reduce by 314.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. Teabox.com needs all CSS files to be minified and compressed as it can save up to 314.9 kB or 82% of the original size.
Number of requests can be reduced by 116 (69%)
167
51
The browser has sent 167 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Teabox. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and as a result speed up the page load time.
teabox.com
87 ms
www.teabox.com
186 ms
d5b51057752a4ddcce2464f7d4b3ea86.css
101 ms
container-10341.html
189 ms
oct.js
6 ms
teabox-005.js
72 ms
conversion.js
18 ms
dc63c6455a914694c068eda55960e849.js
143 ms
a.js
179 ms
analytics.js
21 ms
nudgespot.js
42 ms
rtrg
449 ms
collect
135 ms
collect
230 ms
adsct
257 ms
adsct
137 ms
invite-referrals-1.0.js
247 ms
sdk.js
222 ms
Teabox_WB.svg
116 ms
Teabox_LogoW.jpg
112 ms
gtm.js
192 ms
api.min.js
93 ms
DownArrowWhite.svg
83 ms
WomensDay.svg
84 ms
newsletter.jpg
164 ms
SearchN.svg
161 ms
Featured_Gifts.jpg
163 ms
Nilgiris_HP.jpg
279 ms
Nilgiris_MB.jpg
170 ms
CXOG_1.jpg
159 ms
STUMNB_2.jpg
335 ms
CXOGI_3.jpg
191 ms
Women_s-Day_HP.jpg
198 ms
ffmhmw_1_1.jpg
188 ms
Star.svg
189 ms
ffgdww_1_1.jpg
198 ms
ffshg_1.jpg
196 ms
ffnreb_1_2.jpg
196 ms
ffmib_1_2.jpg
277 ms
carat_1_1.jpg
277 ms
TOW_H.jpg
276 ms
Tea-transformed-new.jpg
557 ms
Tea_Transformed_1.svg
316 ms
Tea_Transformed_2.svg
331 ms
Tea_Transformed_3.svg
328 ms
nyt.png
328 ms
wired-logo.png
362 ms
CNN.jpg
356 ms
1000px-The_Sydney_Morning_Herald_logo.svg.png
360 ms
forbes-new.png
359 ms
beacon.js
310 ms
a
422 ms
jquery.min.js
138 ms
proximanova-light.ttf
213 ms
proximanova-bold.ttf
214 ms
proximanova-regular.ttf
225 ms
teabox_stencil_medium.ttf
228 ms
proximanova-semibold.ttf
227 ms
AvenirLTStd-Book.woff
226 ms
Refer_a_friend.svg
230 ms
Social_White_Instagram.svg
228 ms
Social_White_Pinterest.svg
402 ms
Social_White_Twitter.svg
399 ms
Social_White_Facebook.svg
395 ms
ga-audiences
181 ms
a
488 ms
tnp_js_modal.css
74 ms
ga.js
72 ms
8955.js
274 ms
504 ms
xd_arbiter.php
380 ms
xd_arbiter.php
643 ms
analytics.min.js
390 ms
381 ms
fbds.js
380 ms
345 ms
3d74178d-d449-4ce9-97fd-01b4e5b7e2c2
584 ms
267049
290 ms
layerpop-bg.png
161 ms
scp-ajax-loader.gif
111 ms
__utm.gif
191 ms
ping
194 ms
tc.min.js
193 ms
__utm.gif
132 ms
121 ms
p
525 ms
t
521 ms
webfont.js
53 ms
58 ms
xd_arbiter.php
245 ms
conversion_async.js
44 ms
amplitude-2.9.0-min.gz.js
46 ms
blueshift.js
357 ms
fbevents.js
125 ms
heap-1405870418.js
123 ms
roundtrip.js
40 ms
55bf42df1acd32ac7d000a5a.js
38 ms
ca.html
101 ms
ca.html
114 ms
adsct
110 ms
8dc51c145d371437398643-Signup.jpg
473 ms
442 ms
pixel
300 ms
Pug
281 ms
cx
181 ms
rum
246 ms
adb.gif
211 ms
1
295 ms
cs
487 ms
sync
273 ms
sync
284 ms
Pug
267 ms
pixel
280 ms
cs
472 ms
adb.gif
203 ms
1
284 ms
cx
204 ms
rum
266 ms
api.amplitude.com
373 ms
LocationN.svg
165 ms
LoginN.svg
149 ms
CartN.svg
215 ms
200 ms
184 ms
h
151 ms
h
151 ms
xrefid.xgi
141 ms
demconf.jpg
139 ms
pixel
174 ms
xrefid.xgi
138 ms
mapuid
203 ms
rum
148 ms
lr.gif
172 ms
demconf.jpg
105 ms
360947.gif
126 ms
sd
125 ms
pixel.gif
165 ms
cm
120 ms
cm
138 ms
rum
101 ms
pixel.gif
141 ms
xrefid.xgi
110 ms
360947.gif
109 ms
sd
88 ms
cm
103 ms
cm
124 ms
125 ms
cx
119 ms
lr.gif
107 ms
362378.gif
79 ms
cm
81 ms
tap.php
143 ms
tap.php
152 ms
80 ms
cx
60 ms
SI2WDJECOFEKBES2TYM53J.js
148 ms
60 ms
29 ms
api.amplitude.com
163 ms
23 ms
pixel.gif
23 ms
out
29 ms
tr
29 ms
36 ms
tr
54 ms
tr
98 ms
tr
78 ms
tr
96 ms
tr
109 ms
out
18 ms
out
20 ms
out
26 ms
out
26 ms
out
28 ms
out
47 ms
out
47 ms
out
45 ms
tap.php
346 ms
40 ms
u.php
103 ms
sync
31 ms
adsct
66 ms
pixel
91 ms
sd
34 ms
377928.gif
30 ms
in
15 ms
in
20 ms
nr-768.min.js
104 ms
inspectlet.js
17 ms
settings
861 ms
95 ms
unity.gif
847 ms
unity.gif
847 ms
1600546893
85 ms
unity.gif
759 ms
75cb555927
714 ms
teabox.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements 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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
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.
teabox.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
Missing source maps for large first-party JavaScript
teabox.com 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 Teabox.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 Teabox.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.
teabox.com
Open Graph description is not detected on the main page of Teabox. 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: