Tools & Wizards About Us
whorunsmydrugplan.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

whorunsmydrugplan.com

PBM Resources

Page Load Speed

5.2 sec in total

First Response

1.7 sec

Resources Loaded

3.2 sec

Page Rendered

181 ms

whorunsmydrugplan.com screenshot

About Website

Welcome to whorunsmydrugplan.com homepage info - get ready to check Whorunsmydrugplan best content right away, or after learning these important things about whorunsmydrugplan.com

PBMs: Contributing to Higher Prescription Drug Costs

Visit whorunsmydrugplan.com

Key Findings

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

Performance Metrics

whorunsmydrugplan.com performance score

0

Network Requests Diagram

pbm-resources

1737 ms

jquery.min.js

10 ms

Telerik.Web.UI.WebResource.axd

81 ms

ncpa_new.css

45 ms

ncpa_new_controls.css

44 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Whorunsmydrugplan.com, 5% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Ncpanet.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 748.1 kB (56%)

Content Size

1.3 MB

After Optimization

596.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whorunsmydrugplan.com main page is 1.3 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. 40% of websites need less resources to load. Javascripts take 668.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 224.0 kB

  • Original 286.8 kB
  • After minification 280.1 kB
  • After compression 62.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 224.0 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 7.7 kB

  • Original 329.7 kB
  • After minification 322.0 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. Whorunsmydrugplan images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 469.7 kB

  • Original 668.6 kB
  • After minification 652.3 kB
  • After compression 198.9 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 469.7 kB or 70% of the original size.

CSS Optimization

-79%

Potential reduce by 46.7 kB

  • Original 59.0 kB
  • After minification 54.4 kB
  • After compression 12.3 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. Whorunsmydrugplan.com needs all CSS files to be minified and compressed as it can save up to 46.7 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (50%)

Requests Now

38

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pbm-resources

pbm-resources

1737 ms

jquery.min.js

jquery.min.js

10 ms

Telerik.Web.UI.WebResource.axd

Telerik.Web.UI.WebResource.axd

81 ms

ncpa_new.css

ncpa_new.css

45 ms

ncpa_new_controls.css

ncpa_new_controls.css

44 ms

ncpa_rwd.css

ncpa_rwd.css

47 ms

WebResource.axd

WebResource.axd

65 ms

ScriptResource.axd

ScriptResource.axd

107 ms

ScriptResource.axd

ScriptResource.axd

85 ms

ScriptResource.axd

ScriptResource.axd

66 ms

ScriptResource.axd

ScriptResource.axd

86 ms

ScriptResource.axd

ScriptResource.axd

114 ms

ScriptResource.axd

ScriptResource.axd

98 ms

ScriptResource.axd

ScriptResource.axd

99 ms

ScriptResource.axd

ScriptResource.axd

104 ms

ScriptResource.axd

ScriptResource.axd

112 ms

ScriptResource.axd

ScriptResource.axd

128 ms

ScriptResource.axd

ScriptResource.axd

141 ms

ScriptResource.axd

ScriptResource.axd

130 ms

ScriptResource.axd

ScriptResource.axd

131 ms

1010-Increase.jpg

1010-Increase.jpg

317 ms

PillBottle-Tile.jpg

PillBottle-Tile.jpg

50 ms

follow-l2.jpg

follow-l2.jpg

51 ms

fip-l2.jpg

fip-l2.jpg

59 ms

a.aspx

a.aspx

112 ms

leftshadow.png

leftshadow.png

23 ms

rightshadow.png

rightshadow.png

23 ms

newlogowide.png

newlogowide.png

24 ms

search-bg.png

search-bg.png

23 ms

facebook-icon.png

facebook-icon.png

27 ms

twitter-icon.png

twitter-icon.png

25 ms

google-icon.png

google-icon.png

44 ms

youtube-icon.png

youtube-icon.png

45 ms

instagram-icon.png

instagram-icon.png

47 ms

linkedin-icon.png

linkedin-icon.png

50 ms

leftclosed.png

leftclosed.png

50 ms

WebResource.axd

WebResource.axd

52 ms

print.css

print.css

31 ms

analytics.js

analytics.js

25 ms

collect

collect

11 ms

SEO Factors

whorunsmydrugplan.com SEO score

0

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 Whorunsmydrugplan.com 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 Whorunsmydrugplan.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

whorunsmydrugplan.com

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