3.7 sec in total
789 ms
2.6 sec
249 ms
Visit teagenie.net now to see the best up-to-date Teagenie content and also check out these interesting facts you probably never knew about teagenie.net
A Tea Search Engine - Tell the Tea Genie what you wish for in your cup and then view a wall of teas that fit your criteria. Select a tea and get coupons.
Visit teagenie.netWe analyzed Teagenie.net page load time and found that the first response time was 789 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
teagenie.net performance score
name
value
score
weighting
Value1.1 s
99/100
10%
Value1.1 s
100/100
25%
Value1.6 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.1 s
100/100
10%
789 ms
362 ms
310 ms
431 ms
432 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 77% of them (47 requests) were addressed to the original Teagenie.net, 7% (4 requests) were made to Code.jquery.com and 3% (2 requests) were made to Assets.pinterest.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Teagenie.net.
Page size can be reduced by 507.1 kB (48%)
1.1 MB
545.3 kB
In fact, the total size of Teagenie.net main page is 1.1 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. 45% of websites need less resources to load. Images take 479.8 kB which makes up the majority of the site volume.
Potential reduce by 34.2 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 34.2 kB or 77% of the original size.
Potential reduce by 106.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. Obviously, Teagenie needs image optimization as it can save up to 106.4 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 256.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 256.3 kB or 66% of the original size.
Potential reduce by 110.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. Teagenie.net needs all CSS files to be minified and compressed as it can save up to 110.2 kB or 78% of the original size.
Number of requests can be reduced by 42 (72%)
58
16
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Teagenie. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
teagenie.net
789 ms
wp-emoji-release.min.js
362 ms
wpfp.css
310 ms
button.css
431 ms
form.css
432 ms
font-awesome.css
427 ms
public.css
129 ms
css
24 ms
prettyPhoto.css
389 ms
wp-video-lightbox.css
393 ms
style.css
451 ms
postratings-css.css
459 ms
unsemantic-grid.css
477 ms
style.css
500 ms
mobile.css
504 ms
superfish.css
507 ms
font-awesome.min.css
515 ms
style.css
553 ms
addtoany.min.css
576 ms
jquery.js
703 ms
jquery-migrate.min.js
619 ms
usernoise.js
587 ms
button.js
591 ms
jquery.prettyPhoto.js
635 ms
video-lightbox.js
650 ms
wpfp.js
660 ms
jquery-ui.css
13 ms
jquery-1.10.2.js
13 ms
jquery-ui.js
12 ms
teasearch.js
676 ms
style.css
1335 ms
pinit.js
15 ms
parallax.js
766 ms
postratings-js.js
765 ms
navigation.js
766 ms
superfish.js
767 ms
hoverIntent.min.js
768 ms
masonry.min.js
765 ms
jquery.masonry.min.js
763 ms
scripts.js
798 ms
imagesloaded.pkgd.min.js
797 ms
ga.js
21 ms
__utm.gif
34 ms
collect
117 ms
backgroundbody.png
149 ms
star.png
157 ms
tea-genie3.png
214 ms
facebook.png
189 ms
google.png
199 ms
twitter.png
221 ms
pinterest.png
230 ms
youtube.png
261 ms
ok.png
272 ms
fbds.js
28 ms
background8.png
552 ms
page.js
68 ms
rating_over.gif
72 ms
ui-bg_flat_75_ffffff_40x100.png
7 ms
pinit_main.js
419 ms
18 ms
widget_v2.134.js
14 ms
teagenie.net accessibility score
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
Document doesn't have a <title> element
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
teagenie.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
teagenie.net SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Teagenie.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Teagenie.net 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.
teagenie.net
Open Graph data is detected on the main page of Teagenie. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: