1.6 sec in total
194 ms
1 sec
339 ms
Welcome to pharmacycard.org homepage info - get ready to check Pharmacy Card best content for United States right away, or after learning these important things about pharmacycard.org
We provide the best overall savings available on a free prescription discount card. Average savings typically reaching over 60%.
Visit pharmacycard.orgWe analyzed Pharmacycard.org page load time and found that the first response time was 194 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
pharmacycard.org performance score
194 ms
8 ms
44 ms
18 ms
17 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 43% of them (28 requests) were addressed to the original Pharmacycard.org, 12% (8 requests) were made to Apis.google.com and 11% (7 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (489 ms) belongs to the original domain Pharmacycard.org.
Page size can be reduced by 116.8 kB (24%)
496.2 kB
379.4 kB
In fact, the total size of Pharmacycard.org main page is 496.2 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. Images take 245.3 kB which makes up the majority of the site volume.
Potential reduce by 22.0 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 3.4 kB, which is 11% 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 22.0 kB or 72% of the original size.
Potential reduce by 29.1 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, Pharmacy Card needs image optimization as it can save up to 29.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 39.5 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 39.5 kB or 21% of the original size.
Potential reduce by 26.2 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. Pharmacycard.org needs all CSS files to be minified and compressed as it can save up to 26.2 kB or 75% of the original size.
Number of requests can be reduced by 31 (52%)
60
29
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pharmacy Card. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.
pharmacycard.org
194 ms
cloudflare.min.js
8 ms
jsapi
44 ms
style.css
18 ms
home_slide.js
17 ms
jquery.validate.js
18 ms
registration.js
19 ms
getseal
170 ms
element.js
44 ms
jquery.min.js
7 ms
ga.js
9 ms
bg.jpg
7 ms
img.gif
6 ms
bg_topnav.gif
46 ms
bg_header.jpg
6 ms
logo.gif
8 ms
social_email.gif
42 ms
social_buzz.gif
44 ms
social_twitter.gif
42 ms
social_facebook.gif
44 ms
bg_nav_divider.jpg
45 ms
home_rxcard.png
49 ms
divider.jpg
47 ms
button_printrxcard.gif
49 ms
logo_pharmacy_3.gif
47 ms
check.gif
46 ms
bag2
50 ms
__utm.gif
20 ms
www.pharmacycard.org
102 ms
rss2.gif
246 ms
plusone.js
75 ms
bg_nav.jpg
21 ms
translateelement.css
74 ms
main.js
112 ms
bg_wrapper.gif
37 ms
home_headline.png
12 ms
home_photo_doc2.png
14 ms
css3buttons_backgrounds.png
11 ms
bag2
489 ms
like.php
160 ms
bg_wrapper_bottom.gif
36 ms
cb=gapi.loaded_0
29 ms
cb=gapi.loaded_1
45 ms
fastbutton
80 ms
element_main.js
61 ms
likebox.php
173 ms
postmessageRelay
116 ms
cb=gapi.loaded_0
83 ms
cb=gapi.loaded_1
82 ms
translate_24dp.png
64 ms
l
56 ms
grlryt2bdKIyfMSOhzd1eA.woff
54 ms
googlelogo_color_42x16dp.png
66 ms
3193398744-postmessagerelay.js
28 ms
rpc:shindig_random.js
39 ms
cb=gapi.loaded_0
5 ms
ebiMDO3r-8l.css
174 ms
Pa4LYC3smxF.js
259 ms
FJmpeSpHpjS.js
370 ms
0wM5s1Khldu.js
297 ms
1bNoFZUdlYZ.js
295 ms
pixel.gif
7 ms
pixel.gif
8 ms
I6-MnjEovm5.js
41 ms
pQrUxxo5oQp.js
42 ms
pharmacycard.org SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pharmacycard.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 Pharmacycard.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.
pharmacycard.org
Open Graph data is detected on the main page of Pharmacy Card. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: