1.7 sec in total
121 ms
974 ms
622 ms
Visit mercksource.com now to see the best up-to-date Merck Source content and also check out these interesting facts you probably never knew about mercksource.com
At Merck, we're following the science to tackle some of the world's greatest health threats. Get a glimpse of how we work to improve lives.
Visit mercksource.comWe analyzed Mercksource.com page load time and found that the first response time was 121 ms and then it took 1.6 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.
mercksource.com performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value5.5 s
19/100
25%
Value6.4 s
40/100
10%
Value1,160 ms
22/100
30%
Value1.399
0/100
15%
Value9.2 s
32/100
10%
121 ms
295 ms
21 ms
91 ms
62 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Mercksource.com, 67% (47 requests) were made to Merckengage.com and 9% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (295 ms) relates to the external source Merckengage.com.
Page size can be reduced by 817.2 kB (44%)
1.8 MB
1.0 MB
In fact, the total size of Mercksource.com main page is 1.8 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. 65% of websites need less resources to load. Javascripts take 784.2 kB which makes up the majority of the site volume.
Potential reduce by 65.9 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 65.9 kB or 72% of the original size.
Potential reduce by 41.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. Merck Source images are well optimized though.
Potential reduce by 538.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 538.5 kB or 69% of the original size.
Potential reduce by 171.6 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. Mercksource.com needs all CSS files to be minified and compressed as it can save up to 171.6 kB or 85% of the original size.
Number of requests can be reduced by 22 (37%)
59
37
The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Merck Source. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
mercksource.com
121 ms
ms_transition.aspx
295 ms
404.aspx
21 ms
home
91 ms
css
62 ms
bootstrap.min.css
64 ms
merckengage.css
73 ms
addthis_widget.js
10 ms
jquery-1.11.2.min.js
79 ms
jquery.mobile.custom.min.js
61 ms
bootstrap.min.js
61 ms
merckengage.js
59 ms
WebResource.axd
60 ms
oct.js
56 ms
adherence-widget-merck.js
106 ms
utag.js
173 ms
fbds.js
189 ms
adsct
293 ms
adsct
55 ms
background-header-2.png
30 ms
logo.png
27 ms
btn-chevron.png
24 ms
medicine-matters.jpg
150 ms
me-video.jpg
122 ms
device-integration.jpg
123 ms
allergy-map.jpg
123 ms
my-diary.jpg
134 ms
acorn-squash-filled-with-creamy-chicken.jpg
132 ms
pp-quiz.jpg
151 ms
vaccines.jpg
149 ms
cookbook.jpg
148 ms
carousel-arrow-left.png
148 ms
carousel-arrow-right.png
148 ms
bg.jpg
181 ms
icon.png
232 ms
alpha-30.png
232 ms
facebook-cta.png
235 ms
device-integration.png
236 ms
healthy-recipe.jpg
237 ms
daily-push.jpg
245 ms
circle-eating.png
242 ms
home.jpg
258 ms
logo.png
258 ms
new-window-lg.png
256 ms
background-footer.jpg
259 ms
facebook-footer.png
254 ms
twitter-footer.png
256 ms
youtube-footer.png
261 ms
merck-logo.png
257 ms
essential-access-icon.png
261 ms
truste.png
260 ms
share-this-facebook.png
259 ms
share-this-twitter.png
261 ms
share-this-pinterest.png
261 ms
cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff
133 ms
MTP_ySUJH_bn48VBG8sNSqRDOzjiPcYnFooOUGCOsRk.woff
218 ms
k3k702ZOKiLJc3WVjuplzKRDOzjiPcYnFooOUGCOsRk.woff
246 ms
6498.js
102 ms
adherence-widget-merck.css
95 ms
boost
97 ms
300lo.json
151 ms
glyphicons-halflings-regular.woff
156 ms
xjAJXh38I15wypJXxuGMBrrIa-7acMAeDBVuclsi6Gc.woff
146 ms
PRmiXeptR36kaC0GEAetxuw_rQOTGi-AJs5XCWaKIhU.woff
144 ms
PRmiXeptR36kaC0GEAetxhbnBKKEOwRKgsHDreGcocg.woff
144 ms
sh.07f0d9bf220d07a763adad1e.html
63 ms
alpha-80.png
143 ms
utag.5.js
63 ms
114 ms
analytics.js
22 ms
mercksource.com accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
mercksource.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
mercksource.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
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mercksource.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 Mercksource.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.
mercksource.com
Open Graph description is not detected on the main page of Merck Source. 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: