6 sec in total
1.1 sec
4.1 sec
779 ms
Click here to check amazing Curlytea content for United States. Otherwise, check out these important facts you probably never knew about curlytea.com
INGREDIENTS Get important information about some of the most common ingredients used to make the formulas here! Read more CURLBLOG Some things require more than just a twitter post. Check the CU...
Visit curlytea.comWe analyzed Curlytea.com page load time and found that the first response time was 1.1 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
curlytea.com performance score
name
value
score
weighting
Value10.8 s
0/100
10%
Value13.5 s
0/100
25%
Value19.8 s
0/100
10%
Value3,180 ms
2/100
30%
Value0.048
99/100
15%
Value30.2 s
0/100
10%
1141 ms
311 ms
157 ms
316 ms
425 ms
Our browser made a total of 150 requests to load all elements on the main page. We found that 66% of them (99 requests) were addressed to the original Curlytea.com, 6% (9 requests) were made to Apis.google.com and 5% (7 requests) were made to Ssl.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Curlytea.com.
Page size can be reduced by 768.3 kB (49%)
1.6 MB
809.6 kB
In fact, the total size of Curlytea.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. 70% of websites need less resources to load. Images take 630.9 kB which makes up the majority of the site volume.
Potential reduce by 71.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 71.2 kB or 80% of the original size.
Potential reduce by 53.6 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. Curlytea images are well optimized though.
Potential reduce by 329.2 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 329.2 kB or 68% of the original size.
Potential reduce by 314.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. Curlytea.com needs all CSS files to be minified and compressed as it can save up to 314.2 kB or 84% of the original size.
Number of requests can be reduced by 83 (57%)
145
62
The browser has sent 145 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Curlytea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 35 to 1 for CSS and as a result speed up the page load time.
www.curlytea.com
1141 ms
uikit.min.css
311 ms
template.css
157 ms
widgetkit-ebc62e5d.css
316 ms
bootstrap.css
425 ms
style.css
171 ms
allmode-default.css
175 ms
mootools-core.js
464 ms
core.js
258 ms
jquery.min.js
524 ms
jquery-noconflict.js
348 ms
jquery-migrate.min.js
389 ms
widgetkit-23ff87e7.js
392 ms
base.css
437 ms
layout.css
485 ms
menus.css
486 ms
modules.css
500 ms
tools.css
556 ms
system.css
558 ms
extensions.css
559 ms
custom.css
560 ms
corners.css
577 ms
worldmap_beige.css
609 ms
roboto.css
615 ms
marvel.css
615 ms
marvel.css
627 ms
style.css
626 ms
print.css
654 ms
roboto.css
696 ms
marvel.css
701 ms
warp.js
690 ms
accordionmenu.js
697 ms
dropdownmenu.js
698 ms
template.js
732 ms
search.js
768 ms
adsbygoogle.js
21 ms
platform.js
81 ms
recent_comments_widget.js
167 ms
uikit.min.js
717 ms
lightbox.js
239 ms
mediaelement-and-player.js
386 ms
spotlight.js
246 ms
base.css
265 ms
layout.css
302 ms
menus.css
315 ms
modules.css
327 ms
tools.css
330 ms
system.css
337 ms
system.css
374 ms
system-all.css
388 ms
print.css
314 ms
virgin-coconut-oil-gold-label-1-pint-p5-medium.jpg
226 ms
New-BBC-Banner-8.png
227 ms
special-price-organic-raw-honey-17-6-oz-glass-jar-p2039-medium.jpg
393 ms
beige_bg.jpg
212 ms
beige.jpg
560 ms
curlytealogo10.png
225 ms
searchbox_magnifier_rounded.png
137 ms
twitter-2.png
136 ms
Tumblr-icon01.png
210 ms
youtube.png
224 ms
pinterest.png
222 ms
instagram.png
379 ms
facebook.png
394 ms
greensmoothie_4608efb96b2d7d9b790d3ee3f2a72c79.jpg
390 ms
youtryit004_d9a925a48c7e16fed81a79fd3ad77a31.png
389 ms
tb.php
758 ms
tb.php
390 ms
tb.php
493 ms
tb.php
489 ms
tb.php
490 ms
tb.php
492 ms
tb.php
568 ms
tb.php
567 ms
tb.php
567 ms
tb.php
579 ms
tb.php
648 ms
tb.php
689 ms
tb.php
689 ms
tb.php
687 ms
tb.php
689 ms
tb.php
741 ms
tb.php
743 ms
tb.php
742 ms
tb.php
743 ms
tb.php
765 ms
stitcherradio.jpg
821 ms
itunes.jpg
817 ms
onetimeonlyCORRECT_ad.png
818 ms
light_bulb_32.png
805 ms
ca-pub-4468625191558316.js
164 ms
zrt_lookup.html
332 ms
show_ads_impl.js
85 ms
type-01.png
420 ms
Roboto-Regular-webfont.woff
698 ms
ads
577 ms
marvel-regular-webfont.woff
757 ms
hair10142014p1_wm.jpg
1296 ms
toolbar.png
722 ms
osd.js
181 ms
menubar.png
878 ms
menu_dropdown_level1.png
714 ms
line_dotted_v.png
712 ms
widgets.js
133 ms
plusone.js
131 ms
all.js
72 ms
cb=gapi.loaded_0
38 ms
cb=gapi.loaded_1
58 ms
subscribe_embed
122 ms
icons.png
611 ms
module_badges.png
646 ms
button_more.png
645 ms
module_box_black.png
647 ms
module_box_color.png
659 ms
postmessageRelay
95 ms
close.png
589 ms
blank.gif
610 ms
menu_dropdown_level3.png
634 ms
www-subscribe-embed-vflTum1sJ.css
114 ms
photo.jpg
153 ms
www-subscribe-embed.js
125 ms
152 ms
cb=gapi.loaded_2
40 ms
xd_arbiter.php
55 ms
xd_arbiter.php
64 ms
3193398744-postmessagerelay.js
65 ms
rpc:shindig_random.js
46 ms
www-hitchhiker-vflvB63an.png
23 ms
cb=gapi.loaded_0
16 ms
cb=gapi.loaded_0
11 ms
cb=gapi.loaded_3
4 ms
border_3.gif
12 ms
subscribe_embed
64 ms
spacer.gif
12 ms
border_3.gif
6 ms
bubbleSprite_3.png
6 ms
bubbleDropR_3.png
8 ms
bubbleDropB_3.png
6 ms
css
67 ms
m_js_controller.js
44 ms
abg.js
44 ms
www-subscribe-embed-card-vflqARhQ4.css
3 ms
www-subscribe-embed-card.js
4 ms
favicon
89 ms
nessie_icon_tiamat_white.png
47 ms
s
36 ms
googlelogo_color_112x36dp.png
68 ms
x_button_blue2.png
54 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
29 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
71 ms
curlytea.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
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
curlytea.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Missing source maps for large first-party JavaScript
curlytea.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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 Curlytea.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 Curlytea.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.
curlytea.com
Open Graph description is not detected on the main page of Curlytea. 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: