2 sec in total
228 ms
1.7 sec
104 ms
Click here to check amazing Enamine content for Ukraine. Otherwise, check out these important facts you probably never knew about enamine.net
Enamine - smart chemistry solutions.
Visit enamine.netWe analyzed Enamine.net page load time and found that the first response time was 228 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
enamine.net performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value15.7 s
0/100
25%
Value6.4 s
41/100
10%
Value240 ms
86/100
30%
Value0.801
5/100
15%
Value8.8 s
35/100
10%
228 ms
457 ms
123 ms
250 ms
128 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 87% of them (59 requests) were addressed to the original Enamine.net, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (690 ms) belongs to the original domain Enamine.net.
Page size can be reduced by 785.9 kB (80%)
985.4 kB
199.4 kB
In fact, the total size of Enamine.net main page is 985.4 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. 35% of websites need less resources to load. Javascripts take 891.0 kB which makes up the majority of the site volume.
Potential reduce by 20.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 20.6 kB or 80% of the original size.
Potential reduce by 3.7 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, Enamine needs image optimization as it can save up to 3.7 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 716.6 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 716.6 kB or 80% of the original size.
Potential reduce by 45.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. Enamine.net needs all CSS files to be minified and compressed as it can save up to 45.0 kB or 85% of the original size.
Number of requests can be reduced by 23 (37%)
63
40
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Enamine. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
enamine.net
228 ms
www.enamine.net
457 ms
lightbox.css
123 ms
jquery-ui.css
250 ms
style.css
128 ms
preload.js
131 ms
jquery-1.7.1.js
512 ms
jquery-1.7.2.min.js
317 ms
lightbox.js
182 ms
tabs.js
194 ms
jquery-ui.js
690 ms
googlestuff.js
243 ms
tools.js
260 ms
targeted_libraries_on.gif
66 ms
screening_collection_on.gif
126 ms
tangible_building_blocks_on.gif
74 ms
real_database_on.gif
137 ms
product_focus_on.gif
129 ms
pre-plated_sets_on.gif
199 ms
fragment_library_on.gif
188 ms
building_blocks_on.gif
193 ms
targeted_libraries_off.gif
199 ms
screening_collection_off.gif
285 ms
tangible_building_blocks_off.gif
284 ms
real_database_off.gif
284 ms
product_focus_off.gif
284 ms
pre-plated_sets_off.gif
319 ms
fragment_library_off.gif
320 ms
building_blocks_off.gif
322 ms
gtm.js
47 ms
__top-left.gif
74 ms
squares_rigt.gif
70 ms
enaminestore_v1.gif
68 ms
facebook.png
69 ms
twitter.png
69 ms
linkedin.png
69 ms
google.png
120 ms
youtube.png
133 ms
feed.png
134 ms
menu_q.gif
133 ms
menu_bg.gif
104 ms
free.gif
103 ms
menu_b.gif
152 ms
__bottom-left.gif
164 ms
request-product-information.png
166 ms
news_block_top.gif
168 ms
news_block_bot.gif
163 ms
slash_1.gif
167 ms
building_blocks_name.gif
213 ms
screening_collection_name.gif
230 ms
tangible_building_blocks_name.gif
229 ms
targeted_libraries_name.gif
226 ms
fragment_library_name.gif
227 ms
pre-plated_sets_name.gif
227 ms
copy.gif
276 ms
search_button.png
290 ms
3_copy.gif
290 ms
backgrnd_submenu.png
293 ms
loading.gif
293 ms
close.png
292 ms
analytics.js
7 ms
conversion_async.js
20 ms
collect
7 ms
collect
72 ms
45 ms
39 ms
ga-audiences
40 ms
30 ms
enamine.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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
enamine.net 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
enamine.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Enamine.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 Enamine.net main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
enamine.net
Open Graph description is not detected on the main page of Enamine. 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: