Tools & Wizards About Us
destinationrx.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

destinationrx.com

You are not authorized to view this page

Page Load Speed

3.1 sec in total

First Response

478 ms

Resources Loaded

2.5 sec

Page Rendered

169 ms

destinationrx.com screenshot

About Website

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

DRX is the leading provider of technology solutions for web-based prescription drug comparison and Medicare health plan services.

Visit destinationrx.com

Key Findings

We analyzed Destinationrx.com page load time and found that the first response time was 478 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

destinationrx.com performance score

0

Network Requests Diagram

www.drx.com

478 ms

wp-emoji-release.min.js

127 ms

style.css

179 ms

style.css

319 ms

gglcptch.css

190 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Destinationrx.com, 7% (4 requests) were made to S7.addthis.com and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Drx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 813.2 kB (57%)

Content Size

1.4 MB

After Optimization

602.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Destinationrx.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. 45% of websites need less resources to load. Javascripts take 894.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 122.9 kB

  • Original 159.3 kB
  • After minification 159.2 kB
  • After compression 36.3 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 122.9 kB or 77% of the original size.

Image Optimization

-5%

Potential reduce by 14.0 kB

  • Original 276.2 kB
  • After minification 262.2 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. Destinationrx images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 603.1 kB

  • Original 894.2 kB
  • After minification 890.0 kB
  • After compression 291.1 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 603.1 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 73.2 kB

  • Original 86.0 kB
  • After minification 67.9 kB
  • After compression 12.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. Destinationrx.com needs all CSS files to be minified and compressed as it can save up to 73.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (58%)

Requests Now

55

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Destinationrx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.drx.com

www.drx.com

478 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

127 ms

style.css

style.css

179 ms

style.css

style.css

319 ms

gglcptch.css

gglcptch.css

190 ms

drx.css

drx.css

185 ms

hacks.css

hacks.css

190 ms

jquery.min.js

jquery.min.js

75 ms

jquery.cycle.js

jquery.cycle.js

205 ms

api.js

api.js

49 ms

script.js

script.js

267 ms

tabs_slides.js

tabs_slides.js

277 ms

tabs_slides_opt_loader.js

tabs_slides_opt_loader.js

299 ms

jquery.bxSlider.min.js

jquery.bxSlider.min.js

370 ms

addthis_widget.js

addthis_widget.js

33 ms

superfish.min.js

superfish.min.js

259 ms

superfish.args.min.js

superfish.args.min.js

305 ms

superfish.compat.min.js

superfish.compat.min.js

324 ms

recaptcha__en.js

recaptcha__en.js

188 ms

ga.js

ga.js

34 ms

sm-share-en.gif

sm-share-en.gif

68 ms

background.jpg

background.jpg

183 ms

header-backg.jpg

header-backg.jpg

589 ms

logo.png

logo.png

335 ms

search.png

search.png

197 ms

facebook_16.png

facebook_16.png

228 ms

twitter_16.png

twitter_16.png

226 ms

linkedin_16.png

linkedin_16.png

257 ms

timthumb.php

timthumb.php

985 ms

timthumb.php

timthumb.php

904 ms

timthumb.php

timthumb.php

975 ms

timthumb.php

timthumb.php

658 ms

timthumb.php

timthumb.php

891 ms

timthumb.php

timthumb.php

902 ms

logos1.gif

logos1.gif

952 ms

logos2.gif

logos2.gif

1100 ms

logos3.gif

logos3.gif

1067 ms

logos4.gif

logos4.gif

993 ms

footer-logo.gif

footer-logo.gif

1032 ms

__utm.gif

__utm.gif

156 ms

nav-backg.jpg

nav-backg.jpg

1020 ms

home-middle-backg.jpg

home-middle-backg.jpg

1072 ms

icon-news-events.png

icon-news-events.png

1024 ms

icon-newsletter.png

icon-newsletter.png

1051 ms

icon-contact.png

icon-contact.png

1093 ms

footer-top.png

footer-top.png

1101 ms

300lo.json

300lo.json

45 ms

__utm.gif

__utm.gif

39 ms

bg.png

bg.png

1044 ms

next.png

next.png

1047 ms

prev.png

prev.png

1066 ms

arrow_bg.png

arrow_bg.png

1081 ms

gray_prev.png

gray_prev.png

1096 ms

gray_next.png

gray_next.png

1109 ms

sh.7c7179124ea24ac6ba46caac.html

sh.7c7179124ea24ac6ba46caac.html

32 ms

layers.3643cb2e25fb91c29386.js

layers.3643cb2e25fb91c29386.js

12 ms

SEO Factors

destinationrx.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

Social Sharing Optimization

destinationrx.com

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