Tools & Wizards About Us
drugline.org screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

drugline.org

The domain name drugline.org is for sale

Page Load Speed

883 ms in total

First Response

87 ms

Resources Loaded

640 ms

Page Rendered

156 ms

drugline.org screenshot

About Website

Visit drugline.org now to see the best up-to-date Drugline content for United States and also check out these interesting facts you probably never knew about drugline.org

The domain name drugline.org is for sale. Make an offer or buy it now at a set price.

Visit drugline.org

Key Findings

We analyzed Drugline.org page load time and found that the first response time was 87 ms and then it took 796 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

drugline.org performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value4,590 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.262

47/100

15%

TTI (Time to Interactive)

Value13.7 s

10/100

10%

Network Requests Diagram

drugline.org

87 ms

i.css

9 ms

jquery.auto-complete.css

17 ms

jquery-1.4.4.min.js

47 ms

jquery.auto-complete.js

21 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 43% of them (16 requests) were addressed to the original Drugline.org, 22% (8 requests) were made to Apis.google.com and 14% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (293 ms) relates to the external source Apis.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.7 kB (41%)

Content Size

290.7 kB

After Optimization

171.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Drugline.org main page is 290.7 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. 50% of websites need less resources to load. Javascripts take 135.3 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 18.9 kB

  • Original 25.0 kB
  • After minification 24.5 kB
  • After compression 6.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 18.9 kB or 75% of the original size.

Image Optimization

-21%

Potential reduce by 25.8 kB

  • Original 123.1 kB
  • After minification 97.3 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, Drugline needs image optimization as it can save up to 25.8 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-52%

Potential reduce by 69.7 kB

  • Original 135.3 kB
  • After minification 129.4 kB
  • After compression 65.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 69.7 kB or 52% of the original size.

CSS Optimization

-73%

Potential reduce by 5.4 kB

  • Original 7.3 kB
  • After minification 6.2 kB
  • After compression 1.9 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. Drugline.org needs all CSS files to be minified and compressed as it can save up to 5.4 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (64%)

Requests Now

36

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Drugline. 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 as a result speed up the page load time.

Network Requests Diagram

drugline.org

drugline.org

87 ms

i.css

i.css

9 ms

jquery.auto-complete.css

jquery.auto-complete.css

17 ms

jquery-1.4.4.min.js

jquery-1.4.4.min.js

47 ms

jquery.auto-complete.js

jquery.auto-complete.js

21 ms

i.js

i.js

20 ms

show_ads.js

show_ads.js

10 ms

plusone.js

plusone.js

106 ms

ga.js

ga.js

105 ms

ca-pub-1358993158890239.js

ca-pub-1358993158890239.js

134 ms

zrt_lookup.html

zrt_lookup.html

129 ms

show_ads_impl.js

show_ads_impl.js

129 ms

logo.jpg

logo.jpg

99 ms

sbar.jpg

sbar.jpg

93 ms

flags_preview.png

flags_preview.png

214 ms

arrow_bottom.png

arrow_bottom.png

92 ms

menu_fon.png

menu_fon.png

93 ms

medicine_apk_en.png

medicine_apk_en.png

107 ms

line-green.gif

line-green.gif

106 ms

line-yellow.gif

line-yellow.gif

197 ms

line-red.gif

line-red.gif

198 ms

line-blue.gif

line-blue.gif

195 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

198 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

232 ms

fastbutton

fastbutton

293 ms

__utm.gif

__utm.gif

24 ms

ads

ads

141 ms

expansion_embed.js

expansion_embed.js

61 ms

osd.js

osd.js

89 ms

ads

ads

221 ms

postmessageRelay

postmessageRelay

65 ms

abg.js

abg.js

58 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

61 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

38 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

40 ms

rpc:shindig_random.js

rpc:shindig_random.js

39 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

Accessibility Review

drugline.org accessibility score

52

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

drugline.org best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

drugline.org SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Drugline.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 Drugline.org 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.

Social Sharing Optimization

drugline.org

Open Graph description is not detected on the main page of Drugline. 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: