7.6 sec in total
1.6 sec
5.8 sec
312 ms
Visit o5tea.com now to see the best up-to-date O5 TEA content for United States and also check out these interesting facts you probably never knew about o5tea.com
Vancouver Based Tea Shop. Online shopping premium loose-leaf tea, matcha, teaware, and gifts. Free shipping $111.
Visit o5tea.comWe analyzed O5tea.com page load time and found that the first response time was 1.6 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
o5tea.com performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value9.3 s
1/100
25%
Value5.9 s
48/100
10%
Value1,030 ms
26/100
30%
Value0.086
93/100
15%
Value18.0 s
3/100
10%
1578 ms
36 ms
240 ms
182 ms
31 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 50% of them (59 requests) were addressed to the original O5tea.com, 13% (15 requests) were made to Static.xx.fbcdn.net and 11% (13 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain O5tea.com.
Page size can be reduced by 1.1 MB (50%)
2.2 MB
1.1 MB
In fact, the total size of O5tea.com 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. 70% of websites need less resources to load. Images take 815.8 kB which makes up the majority of the site volume.
Potential reduce by 115.5 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 115.5 kB or 80% of the original size.
Potential reduce by 23.1 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. O5 TEA images are well optimized though.
Potential reduce by 277.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 277.7 kB or 69% of the original size.
Potential reduce by 672.0 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. O5tea.com needs all CSS files to be minified and compressed as it can save up to 672.0 kB or 83% of the original size.
Number of requests can be reduced by 80 (73%)
109
29
The browser has sent 109 CSS, Javascripts, AJAX and image requests in order to completely render the main page of O5 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 43 to 1 for JavaScripts and from 33 to 1 for CSS and as a result speed up the page load time.
o5tea.com
1578 ms
css
36 ms
woocommerce-mod.css
240 ms
cff-style.css
182 ms
font-awesome.min.css
31 ms
wordpress-svg-icon-plugin-style.min.css
165 ms
taptap.css
144 ms
css
48 ms
font-awesome.min.css
167 ms
grid.css
156 ms
base.css
213 ms
layout.css
297 ms
shortcodes.css
361 ms
magnific-popup.css
245 ms
mediaelementplayer.css
267 ms
enfold_child.css
376 ms
custom.css
331 ms
style.css
307 ms
widget.css
345 ms
ubermenu.min.css
372 ms
vanilla.css
385 ms
blackwhite2.css
428 ms
font-awesome.min.css
418 ms
genericons.css
451 ms
jetpack.css
463 ms
jquery.js
525 ms
jquery-migrate.min.js
479 ms
taptap-accordion.js
489 ms
avia-compat.js
493 ms
pinit.js
599 ms
wp-emoji-release.min.js
565 ms
style.css
557 ms
woocommerce-mod.js
554 ms
photon.js
554 ms
cff-scripts.js
555 ms
taptap.js
580 ms
jquery.cookie.min.js
599 ms
cart-fragments.min.js
631 ms
wcpbc-frontend.min.js
1995 ms
devicepx-jetpack.js
8 ms
gprofiles.js
54 ms
js
40 ms
e-201611.js
6 ms
add-to-cart.min.js
616 ms
jquery.blockUI.min.js
538 ms
woocommerce.min.js
545 ms
wpgroho.js
561 ms
avia.js
691 ms
shortcodes.js
632 ms
jquery.magnific-popup.min.js
541 ms
mediaelement-and-player.min.js
588 ms
wp-mediaelement.js
558 ms
comment-reply.min.js
554 ms
bj-lazy-load.min.js
600 ms
ubermenu.min.js
595 ms
wp-embed.min.js
574 ms
logo.png
360 ms
logo_mobile.png
387 ms
sdk.js
270 ms
arrow_right.png
361 ms
mobile_o5tea.jpg
603 ms
MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff
18 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
19 ms
entypo-fontello.woff
433 ms
fontawesome-webfont.woff
492 ms
fontawesome-webfont.woff
525 ms
fontawesome-webfont.woff
17 ms
widgets.js
86 ms
pinit_main.js
26 ms
110 ms
xd_arbiter.php
212 ms
xd_arbiter.php
417 ms
print.css
200 ms
o5tea.com
1314 ms
hovercard.css
96 ms
services.css
98 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
115 ms
g.gif
12 ms
Sakura-large.jpg
16 ms
preload-dark-big.gif
151 ms
FullSizeRender-1.jpg
11 ms
page.php
163 ms
syndication
83 ms
610897179708817410
210 ms
4n08FrZmW0I.css
282 ms
6anp_x4LZhS.css
350 ms
ziZi0nPwp2z.css
418 ms
q68gy-v_YMF.js
618 ms
YvxwM8R7ol8.js
618 ms
ihptErjAmMX.js
553 ms
3So47A9WcrL.js
486 ms
cUsKAwzqrQw.js
655 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
30 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.dark.ltr.css
67 ms
O5Tea_normal.jpg
44 ms
Cd8wv7-WAAA6qFp.jpg:small
111 ms
jot
22 ms
546635_440092049339440_1602497548_n.jpg
476 ms
534824_440091759339469_633876179_n.jpg
535 ms
1655929_1300940843254552_6744517313231103706_n.jpg
785 ms
12088182_1301114859903817_6891461686461178290_n.jpg
850 ms
1927778_1301155813233055_6327880439516537489_n.jpg
692 ms
1517457_1299990520016251_7070487850283466968_n.jpg
729 ms
1934551_1300028310012472_7144243633750392977_n.jpg
729 ms
1917151_1300237516658218_5980643908248284645_n.jpg
698 ms
10325752_1300237476658222_3686423193279912989_n.jpg
822 ms
10650012_1299990496682920_4921271659679163465_n.jpg
948 ms
1935187_1299086373439999_4461940067392263674_n.jpg
869 ms
1512578_1299317866750183_1063784465253004377_n.jpg
824 ms
1780762_1299644050050898_6046910718241901383_n.jpg
923 ms
wL6VQj7Ab77.png
81 ms
s7jcwEQH7Sx.png
82 ms
GtIpNnEyqq_.png
82 ms
R9a_DtVRZgv.js
71 ms
cUDgRFxaoIk.js
73 ms
0JBr1QHp8Gi.js
71 ms
kDOzhTr2W91.js
69 ms
o5tea.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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
o5tea.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
o5tea.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 O5tea.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 O5tea.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.
o5tea.com
Open Graph data is detected on the main page of O5 TEA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: