2.4 sec in total
225 ms
1.5 sec
733 ms
Welcome to dataessence.com homepage info - get ready to check DataEssence best content right away, or after learning these important things about dataessence.com
dataEssence software manages formulations, ingredients, and regulatory compliance for Flavour, Fragrance and Essential Oil Industries.
Visit dataessence.comWe analyzed Dataessence.com page load time and found that the first response time was 225 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
dataessence.com performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value9.6 s
0/100
25%
Value5.6 s
52/100
10%
Value450 ms
63/100
30%
Value0.741
6/100
15%
Value9.0 s
34/100
10%
225 ms
411 ms
28 ms
13 ms
28 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 48% of them (54 requests) were addressed to the original Dataessence.com, 48% (54 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (661 ms) relates to the external source Moderate10-v4.cleantalk.org.
Page size can be reduced by 274.2 kB (48%)
566.8 kB
292.6 kB
In fact, the total size of Dataessence.com main page is 566.8 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only a small number of websites need less resources to load. HTML takes 314.5 kB which makes up the majority of the site volume.
Potential reduce by 269.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 269.8 kB or 86% of the original size.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 2.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. Dataessence.com needs all CSS files to be minified and compressed as it can save up to 2.0 kB or 29% of the original size.
Number of requests can be reduced by 23 (41%)
56
33
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DataEssence. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
dataessence.com
225 ms
dataessence.com
411 ms
cleantalk-public.min.css
28 ms
style.min.css
13 ms
jquery.min.js
28 ms
jquery-migrate.min.js
38 ms
apbct-public-bundle.min.js
70 ms
782488.js
70 ms
css
41 ms
css
26 ms
mediaelementplayer-legacy.min.css
25 ms
wp-mediaelement.min.css
24 ms
hooks.min.js
24 ms
i18n.min.js
26 ms
web-components.esm.js
37 ms
scripts.min.js
48 ms
jquery.fitvids.js
31 ms
easypiechart.js
38 ms
salvattore.js
37 ms
frontend-bundle.min.js
41 ms
common.js
49 ms
mediaelement-and-player.min.js
89 ms
mediaelement-migrate.min.js
49 ms
wp-mediaelement.min.js
87 ms
sticky-elements.js
89 ms
gtm.js
358 ms
c88e3f4adac8f84a58501f3c1e4c7f3e.gif
661 ms
et-divi-dynamic-tb-989-tb-934-827-late.css
35 ms
logo-dataEssence.webp
30 ms
background-home-1.webp
137 ms
icon-simplified-compliance-scaled.webp
33 ms
icon-improved-efficiency-scaled.webp
136 ms
icon-increased-accuracy-scaled.webp
74 ms
icon-regulatory-compliance.webp
138 ms
icon-formulation-development.webp
330 ms
icon-chemical-management.webp
137 ms
icon-product-management.webp
314 ms
icon-customer-support.webp
328 ms
icon-sds-service.webp
329 ms
icon-dataEssence-core-solution.webp
329 ms
icon-dataEssence-enterprise-solution.webp
329 ms
logo-lush.webp
384 ms
logo-senses.webp
384 ms
logo-elixarome.webp
385 ms
logo-industrial-fragrances.webp
383 ms
logo-de-monchy-aromatics.webp
391 ms
logo-kimex.webp
386 ms
logo-omega-ingredients.webp
393 ms
logo-authentic-oil-co.webp
393 ms
blog-what-to-do-when-you-receive-a-safety-data-sheet-sds.webp
399 ms
blog-navigating-eu-and-uk-classification-divergence.webp
400 ms
blog-how-to-comply-with-the-ifra-standards.webp
401 ms
guide-guide-on-clp-labelling-for-producers-of-fragranced-consumer-products.webp
409 ms
logo-the-international-fragrance-association.webp
401 ms
logo-the-uk-flavour-association.webp
405 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff
128 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aX8.ttf
321 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff
326 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aX8.ttf
325 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff
326 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aX8.ttf
325 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aXw.woff
374 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw3aX8.ttf
373 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aXw.woff
372 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw3aX8.ttf
374 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aXw.woff
374 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w3aX8.ttf
373 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff
381 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aX8.ttf
383 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aXw.woff
380 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w3aX8.ttf
380 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aXw.woff
380 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w3aX8.ttf
383 ms
modules.woff
582 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrc.woff
259 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCGPrQ.ttf
256 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrc.woff
256 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCGPrQ.ttf
256 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrc.woff
259 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCGPrQ.ttf
258 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrc.woff
262 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCGPrQ.ttf
261 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrc.woff
263 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCGPrQ.ttf
265 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrc.woff
263 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCGPrQ.ttf
265 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrc.woff
268 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCGPrQ.ttf
269 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrc.woff
268 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCGPrQ.ttf
271 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrc.woff
272 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CGPrQ.ttf
270 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXZ0oA.woff
272 ms
background-footer.webp
180 ms
logo-dataEssence.webp
106 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXZ0ow.ttf
88 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXZ0oA.woff
83 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXZ0ow.ttf
87 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXZ0oA.woff
85 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXZ0ow.ttf
85 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9WXZ0oA.woff
118 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9WXZ0ow.ttf
120 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8WXZ0oA.woff
121 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8WXZ0ow.ttf
120 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXZ0oA.woff
118 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXZ0ow.ttf
119 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXZ0oA.woff
115 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXZ0ow.ttf
116 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXZ0oA.woff
115 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXZ0ow.ttf
116 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16WXZ0oA.woff
114 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16WXZ0ow.ttf
114 ms
logo-dataEssence.webp
15 ms
dataessence.com accessibility score
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.
dataessence.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
dataessence.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
![]()
EN
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dataessence.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 Dataessence.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.
dataessence.com
Open Graph data is detected on the main page of DataEssence. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: