5.8 sec in total
413 ms
4.9 sec
455 ms
Visit herbalflame.com now to see the best up-to-date Herbalflame content and also check out these interesting facts you probably never knew about herbalflame.com
Visit herbalflame.comWe analyzed Herbalflame.com page load time and found that the first response time was 413 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
herbalflame.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value3.6 s
60/100
25%
Value3.3 s
91/100
10%
Value190 ms
91/100
30%
Value0.099
90/100
15%
Value3.9 s
88/100
10%
413 ms
2652 ms
63 ms
51 ms
110 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 65% of them (37 requests) were addressed to the original Herbalflame.com, 9% (5 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Static-v.tawk.to. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Herbalflame.com.
Page size can be reduced by 663.1 kB (48%)
1.4 MB
707.4 kB
In fact, the total size of Herbalflame.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. 50% of websites need less resources to load. Javascripts take 699.3 kB which makes up the majority of the site volume.
Potential reduce by 44.6 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 44.6 kB or 84% of the original size.
Potential reduce by 0 B
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. Herbalflame images are well optimized though.
Potential reduce by 496.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 496.7 kB or 71% of the original size.
Potential reduce by 121.8 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. Herbalflame.com needs all CSS files to be minified and compressed as it can save up to 121.8 kB or 82% of the original size.
Number of requests can be reduced by 27 (60%)
45
18
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Herbalflame. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
herbalflame.com
413 ms
herbalflame.com
2652 ms
wp-emoji-release.min.js
63 ms
jquery-ui.css
51 ms
jquery.timepicker.min.css
110 ms
style.css
165 ms
icons.css
254 ms
css
120 ms
woocommerce.css
285 ms
jquery.js
401 ms
jquery-migrate.min.js
284 ms
core.min.js
301 ms
datepicker.min.js
304 ms
wcj-datepicker.js
312 ms
wcj-weekpicker.js
801 ms
jquery.timepicker.min.js
348 ms
wcj-timepicker.js
375 ms
add-to-cart.min.js
379 ms
jquery.blockUI.min.js
553 ms
woocommerce.min.js
553 ms
jquery.cookie.min.js
553 ms
cart-fragments.min.js
553 ms
navigation.min.js
567 ms
skip-link-focus-fix.min.js
558 ms
header-cart.min.js
558 ms
wp-embed.min.js
553 ms
ga.js
148 ms
cropped-herbal-flame-logo-small-1.png
265 ms
argan-4-oz-galss2-450x450.jpg
207 ms
grape-seed-4-oz-glass-450x450.jpg
524 ms
green-tea-450x407.jpg
591 ms
4oz-hemp-seed-oil-ad-glass-450x450.jpg
402 ms
jojoba-ad-4-oz-glass-450x450.jpg
328 ms
lanolin-4-oz-ad-glass1-450x450.jpg
592 ms
neem-4-oz-ad-glass-450x450.jpg
580 ms
red-tea-450x407.jpg
1368 ms
white-tea-450x407.jpg
657 ms
default
385 ms
ODelI1aHBYDBqgeIAH2zlFzCdIATDt8zXO3QNtzVeJ8.ttf
181 ms
toadOcfmlt9b38dHJxOBGEBls_1aQwi4AfipSOlE3SU.ttf
234 ms
toadOcfmlt9b38dHJxOBGGvd-IutAbwf5FQ8ZpuI2w4.ttf
310 ms
toadOcfmlt9b38dHJxOBGGAlZ1PukdtTN2z-JxSzbe8.ttf
310 ms
toadOcfmlt9b38dHJxOBGOmWm5x7AGfSS0YwqQKRPBc.ttf
309 ms
fontawesome-webfont.woff
948 ms
star.woff
504 ms
__utm.gif
16 ms
collect
196 ms
herbalflame.com
706 ms
icons.png
152 ms
emojione.min.css
145 ms
emojione.min.js
161 ms
1507604226261
329 ms
ajax-loader.gif
135 ms
ajax-loader-3.gif
37 ms
153 ms
46 ms
v3
56 ms
herbalflame.com 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
<frame> or <iframe> elements do not have a title
herbalflame.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
herbalflame.com 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
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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Herbalflame.com 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 Herbalflame.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.
herbalflame.com
Open Graph description is not detected on the main page of Herbalflame. 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: