5.1 sec in total
260 ms
4 sec
887 ms
Welcome to ecstasydata.org homepage info - get ready to check Ecstasy Data best content for United States right away, or after learning these important things about ecstasydata.org
DrugsData.org lab analysis and drug checking results
Visit ecstasydata.orgWe analyzed Ecstasydata.org page load time and found that the first response time was 260 ms 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.
ecstasydata.org performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value7.9 s
3/100
25%
Value5.6 s
54/100
10%
Value50 ms
100/100
30%
Value0.004
100/100
15%
Value4.4 s
83/100
10%
260 ms
336 ms
221 ms
293 ms
419 ms
Our browser made a total of 120 requests to load all elements on the main page. We found that all of those requests were addressed to Ecstasydata.org and no external sources were called. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Ecstasydata.org.
Page size can be reduced by 171.9 kB (35%)
495.9 kB
324.0 kB
In fact, the total size of Ecstasydata.org main page is 495.9 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. 25% of websites need less resources to load. Images take 389.6 kB which makes up the majority of the site volume.
Potential reduce by 63.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. This page needs HTML code to be minified as it can gain 8.6 kB, which is 12% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 63.8 kB or 88% of the original size.
Potential reduce by 79.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, Ecstasy Data needs image optimization as it can save up to 79.7 kB or 20% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 28.5 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. Ecstasydata.org needs all CSS files to be minified and compressed as it can save up to 28.5 kB or 84% of the original size.
Number of requests can be reduced by 7 (6%)
117
110
The browser has sent 117 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ecstasy Data. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
ecstasydata.org
260 ms
www.ecstasydata.org
336 ms
nav_styles.css
221 ms
main_styles.css
293 ms
ED_Logo.jpg
419 ms
body_back.jpg
74 ms
nav_back.jpg
514 ms
button_go.png
148 ms
header_button_right.png
149 ms
header_button_left.png
151 ms
tab_selected.gif
150 ms
h_dotted.gif
220 ms
arrow.gif
292 ms
v_dotted.gif
293 ms
filter_back.gif
295 ms
filter_divider.gif
295 ms
table_header_back.gif
365 ms
info_icon.png
439 ms
sorted_icon_down.png
440 ms
4174_sm.jpg
440 ms
4173_sm.jpg
440 ms
4172_sm.jpg
510 ms
4171_sm.jpg
585 ms
4170_sm.jpg
587 ms
4169_sm.jpg
589 ms
4168_sm.jpg
589 ms
4167_sm.jpg
655 ms
4134_sm.jpg
657 ms
4133_sm.jpg
733 ms
4132_sm.jpg
730 ms
4131_sm.jpg
733 ms
4130_sm.jpg
734 ms
4129_sm.jpg
800 ms
4128_sm.jpg
800 ms
4127_sm.jpg
876 ms
4126_sm.jpg
878 ms
4125_sm.jpg
878 ms
4124_sm.jpg
876 ms
4123_sm.jpg
944 ms
4122_sm.jpg
897 ms
4121_sm.jpg
973 ms
4120_sm.jpg
959 ms
4113_sm.jpg
886 ms
4112_sm.jpg
886 ms
4111_sm.jpg
951 ms
4110_sm.jpg
951 ms
4109_sm.jpg
956 ms
4108_sm.jpg
886 ms
4107_sm.jpg
887 ms
4166_sm.jpg
886 ms
4165_sm.jpg
953 ms
4164_sm.jpg
883 ms
4163_sm.jpg
883 ms
4162_sm.jpg
884 ms
4161_sm.jpg
890 ms
4160_sm.jpg
1051 ms
4159_sm.jpg
884 ms
4158_sm.jpg
883 ms
4157_sm.jpg
880 ms
4156_sm.jpg
883 ms
4155_sm.jpg
882 ms
4154_sm.jpg
945 ms
4153_sm.jpg
882 ms
4152_sm.jpg
954 ms
4151_sm.jpg
884 ms
4150_sm.jpg
883 ms
4149_sm.jpg
903 ms
4148_sm.jpg
947 ms
4147_sm.jpg
882 ms
4146_sm.jpg
953 ms
4145_sm.jpg
880 ms
4144_sm.jpg
881 ms
4143_sm.jpg
903 ms
4142_sm.jpg
947 ms
4141_sm.jpg
885 ms
4140_sm.jpg
956 ms
4139_sm.jpg
882 ms
4138_sm.jpg
880 ms
4137_sm.jpg
902 ms
4136_sm.jpg
947 ms
4135_sm.jpg
883 ms
4119_sm.jpg
954 ms
4118_sm.jpg
881 ms
4117_sm.jpg
880 ms
4116_sm.jpg
902 ms
4115_sm.jpg
947 ms
4114_sm.jpg
883 ms
4106_sm.jpg
953 ms
4105_sm.jpg
885 ms
4103_sm.jpg
880 ms
4102_sm.jpg
894 ms
4101_sm.jpg
877 ms
4100_sm.jpg
878 ms
4099_sm.jpg
878 ms
4098_sm.jpg
877 ms
4097_sm.jpg
875 ms
4096_sm.jpg
878 ms
4095_sm.jpg
880 ms
4094_sm.jpg
879 ms
4093_sm.jpg
878 ms
4092_sm.jpg
878 ms
4091_sm.jpg
876 ms
4090_sm.jpg
878 ms
4089_sm.jpg
880 ms
4088_sm.jpg
878 ms
4087_sm.jpg
880 ms
4086_sm.jpg
881 ms
4085_sm.jpg
881 ms
4084_sm.jpg
880 ms
4083_sm.jpg
879 ms
4082_sm.jpg
879 ms
4081_sm.jpg
880 ms
4080_sm.jpg
881 ms
4079_sm.jpg
881 ms
4078_sm.jpg
879 ms
4077_sm.jpg
879 ms
4075_sm.jpg
875 ms
4074_sm.jpg
878 ms
4073_sm.jpg
878 ms
footer_back.gif
1023 ms
ecstasydata.org 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
Some elements have a [tabindex] value greater than 0
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
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
ecstasydata.org 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
ecstasydata.org SEO score
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ecstasydata.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ecstasydata.org 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.
ecstasydata.org
Open Graph description is not detected on the main page of Ecstasy Data. 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: