9.2 sec in total
341 ms
8.2 sec
636 ms
Click here to check amazing Tea Guy content for United States. Otherwise, check out these important facts you probably never knew about tea-guy.com
Notes on my sips of tea, coffee, and other imbibed concoctions.
Visit tea-guy.comWe analyzed Tea-guy.com page load time and found that the first response time was 341 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
tea-guy.com performance score
name
value
score
weighting
Value10.3 s
0/100
10%
Value12.0 s
0/100
25%
Value10.3 s
8/100
10%
Value1,420 ms
15/100
30%
Value0.207
60/100
15%
Value16.3 s
5/100
10%
341 ms
6414 ms
226 ms
211 ms
124 ms
Our browser made a total of 81 requests to load all elements on the main page. We found that 31% of them (25 requests) were addressed to the original Tea-guy.com, 19% (15 requests) were made to Cdn.datatables.net and 6% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (6.4 sec) belongs to the original domain Tea-guy.com.
Page size can be reduced by 1.1 MB (73%)
1.4 MB
385.7 kB
In fact, the total size of Tea-guy.com main page is 1.4 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. Javascripts take 864.7 kB which makes up the majority of the site volume.
Potential reduce by 46.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. 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 46.8 kB or 75% of the original size.
Potential reduce by 3.3 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. Obviously, Tea Guy needs image optimization as it can save up to 3.3 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 594.0 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 594.0 kB or 69% of the original size.
Potential reduce by 408.2 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. Tea-guy.com needs all CSS files to be minified and compressed as it can save up to 408.2 kB or 84% of the original size.
Number of requests can be reduced by 57 (79%)
72
15
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tea Guy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
tea-guy.com
341 ms
www.tea-guy.com
6414 ms
wp-emoji-release.min.js
226 ms
ajax-contact.css
211 ms
jquery.dataTables.min.css
124 ms
buttons.dataTables.min.css
127 ms
select.dataTables.min.css
146 ms
fixedHeader.dataTables.min.css
134 ms
fixedColumns.dataTables.min.css
157 ms
responsive.dataTables.min.css
155 ms
sb-instagram.css
284 ms
font-awesome.min.css
39 ms
style.css
518 ms
css
112 ms
font-awesome.css
340 ms
tweets.css
376 ms
wp-paginate.css
291 ms
jquery.js
501 ms
jquery-migrate.min.js
429 ms
ajax-contact.js
361 ms
jquery.dataTables.min.js
20 ms
dataTables.buttons.min.js
107 ms
buttons.colVis.min.js
91 ms
buttons.print.min.js
90 ms
pdfmake.min.js
91 ms
vfs_fonts.js
86 ms
jszip.min.js
83 ms
buttons.html5.min.js
34 ms
dataTables.select.min.js
95 ms
dataTables.fixedHeader.min.js
109 ms
dataTables.fixedColumns.min.js
103 ms
dataTables.responsive.min.js
103 ms
igsv-datatables.js
475 ms
jsapi
86 ms
igsv-gvizcharts.js
602 ms
buttons.js
104 ms
sb-instagram.js
440 ms
mlt.js
9 ms
lib.js
515 ms
main.js
513 ms
bootstrap.min.js
642 ms
theme.js
515 ms
jquery.cycle.all.min.js
670 ms
wp-embed.min.js
669 ms
mlt.js
32 ms
16 ms
ui+en.css
4 ms
format+en,default+en,ui+en,gauge+en,corechart+en.I.js
22 ms
ga.js
45 ms
Tea-Guy-Header.png
365 ms
Teaity-BW-for-content.png
361 ms
loader.png
364 ms
cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff
46 ms
k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff
47 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
46 ms
fontawesome-webfont.woff
333 ms
fontawesome-webfont.woff
45 ms
__utm.gif
25 ms
U8nJ8H3I90k
275 ms
10268440
199 ms
recent
452 ms
getAllAppDefault.esi
100 ms
www-embed-player-vflfNyN_r.css
26 ms
www-embed-player.js
47 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
46 ms
ad_status.js
45 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
64 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
64 ms
getSegment.php
30 ms
checkOAuth.esi
48 ms
t.dhj
51 ms
12139730_414984828693643_769913279_a.jpg
21 ms
t.dhj
37 ms
cm
14 ms
x35248
122 ms
s-3271.xgi
6 ms
12 ms
6 ms
hbpix
30 ms
xrefid.xgi
4 ms
19505
17 ms
tea-guy.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.
tea-guy.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
Page has valid source maps
tea-guy.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 Tea-guy.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 Tea-guy.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.
tea-guy.com
Open Graph description is not detected on the main page of Tea Guy. 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: