3.5 sec in total
171 ms
2.7 sec
626 ms
Visit blinkhealth.com now to see the best up-to-date Blinkhealth content for United States and also check out these interesting facts you probably never knew about blinkhealth.com
Use Blink Health to find prescription drug prices, discounts and information. The Blink Price is available at virtually every U.S. pharmacy, including Duane Reade, Walgreens, CVS, Walmart and Rite Aid...
Visit blinkhealth.comWe analyzed Blinkhealth.com page load time and found that the first response time was 171 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
blinkhealth.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value5.9 s
14/100
25%
Value4.4 s
75/100
10%
Value960 ms
29/100
30%
Value0.071
96/100
15%
Value7.9 s
43/100
10%
171 ms
609 ms
153 ms
78 ms
107 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 7% of them (7 requests) were addressed to the original Blinkhealth.com, 27% (26 requests) were made to D1wxsnwfph0vhx.cloudfront.net and 8% (8 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (926 ms) relates to the external source Api.segment.io.
Page size can be reduced by 512.2 kB (40%)
1.3 MB
783.7 kB
In fact, the total size of Blinkhealth.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. 60% of websites need less resources to load. Images take 486.2 kB which makes up the majority of the site volume.
Potential reduce by 115.4 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 115.4 kB or 86% of the original size.
Potential reduce by 32.6 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. Blinkhealth images are well optimized though.
Potential reduce by 165.8 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 165.8 kB or 54% of the original size.
Potential reduce by 198.4 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. Blinkhealth.com needs all CSS files to be minified and compressed as it can save up to 198.4 kB or 54% of the original size.
Number of requests can be reduced by 40 (49%)
82
42
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blinkhealth. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
blinkhealth.com
171 ms
www.blinkhealth.com
609 ms
fonts.css
153 ms
main-79e60bea7d90a8d4b62d.css
78 ms
seal
107 ms
112 ms
vendor-6b89eb862d24bd7db311.js
113 ms
main-79e60bea7d90a8d4b62d.js
124 ms
client.js
110 ms
App-Download@2xabcfb6077b16e58a138a6f638ff2d4c3.png
101 ms
apple-store@2x36ce2c6e2337e80f18578a4d8bfd53f2.png
100 ms
google-play@2x3cd99c6e6afd5fe020885908d24d9272.png
101 ms
getseal
42 ms
DBF8E1D01960FB5A2.css
17 ms
getseal
9 ms
account
313 ms
medications
335 ms
wallet
508 ms
cards
439 ms
analytics.min.js
103 ms
map-1800.png
100 ms
Pillustration@2x.png
42 ms
mark.png
41 ms
mark-top.png
41 ms
nyt.png
41 ms
nbc.png
40 ms
huffpo.png
79 ms
today.png
78 ms
nytimes-logoe8e9a0e7f4311dd4bdb37c7cc79f93fc.png
79 ms
pharmacy-logos-color-10246bc2e2a713f81d5ce6e2649c7a25bef1.png
77 ms
howitworks-onebe8074e69f74aff6ae724f079b064ff1.png
77 ms
howitworks-two0fd52b1645a41cfb0f242fc641cc4a63.png
79 ms
howitworks-threeb3d75b3afbba094f25e046af9c79f9b8.png
81 ms
testimonial-jacobya3f6e9e276b147c5b3fc0dd89ec991c3.jpg
91 ms
testimonial-tawandab9e7146fd0d359ed5711ec089509c1bb.jpg
86 ms
testimonial-morgan84166d4990a743a67c69ec1cddf2314a.jpg
79 ms
testimonial-phoebe9abf2783fb9e201c14033917a02ee650.jpg
92 ms
nbc8175760705441513b3ec7004aa3357b1.png
93 ms
nabp26f915ec17c09dd1f6ec5319a2c67313.png
93 ms
+X8jfIt0Mh
29 ms
5fyN3bWQw0=
28 ms
lL5eYQxU=
27 ms
VDGQ==
26 ms
KeTJHV4eWFVoFP8s1g2T1WU7tVHBreGkFGfQN1p6MVZ9h8C4l07IRJbhbqEUBStZrzrWvtLlSMLP8+Qu1nEc49OzXWZ3cnxRit9K+j5l
30 ms
cb=gapi.loaded_0
73 ms
channel.html
73 ms
postmessageRelay
225 ms
p
722 ms
t
917 ms
t
925 ms
t
926 ms
i
922 ms
conversion_async.js
144 ms
bat.js
390 ms
fbevents.js
429 ms
analytics.js
120 ms
heap-1983607188.js
239 ms
tracker.js
302 ms
gtm.js
194 ms
inspectlet.js
148 ms
collect
119 ms
collect
349 ms
collect
214 ms
collect
215 ms
collect
215 ms
322 ms
3193398744-postmessagerelay.js
302 ms
rpc:shindig_random.js
178 ms
273088524
345 ms
intercom.21a35ffd.js
412 ms
spp.pl
351 ms
a.js;m=11247200796080;cache=0.5263016510289162
243 ms
a.js;m=11247200796080;cache=0.15962605830281973
336 ms
spp.pl
357 ms
activityi;src=5273119;type=confun;cat=blink000;u9=false;u7=null;u11=0;u10=0;ord=3776865641004;~oref=https%3A%2F%2Fwww.blinkhealth.com%2F
353 ms
activityi;src=5273119;type=confun;cat=blink0;u9=false;u7=null;ord=6533665351360;~oref=https%3A%2F%2Fwww.blinkhealth.com%2F
293 ms
h
280 ms
h
278 ms
pv
260 ms
477 ms
485 ms
508 ms
527 ms
529 ms
527 ms
531 ms
529 ms
cb=gapi.loaded_0
106 ms
442 ms
12939
384 ms
tag
129 ms
tag
344 ms
tag
342 ms
tag
340 ms
echo.515e8809.js
232 ms
pdata
21 ms
blinkhealth.com accessibility score
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
button, link, and menuitem elements do not have accessible names.
[aria-hidden="true"] elements contain focusable descendents
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
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
<object> elements do not have alternate text
blinkhealth.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
blinkhealth.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blinkhealth.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Blinkhealth.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.
blinkhealth.com
Open Graph data is detected on the main page of Blinkhealth. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: