1.5 sec in total
13 ms
1 sec
483 ms
Visit norvasc.com now to see the best up-to-date NORVASC content for United States and also check out these interesting facts you probably never knew about norvasc.com
Learn about NORVASC® (amlodipine besylate) high blood pressure medicine. Read about the risks and benefits of NORVASC®.
Visit norvasc.comWe analyzed Norvasc.com page load time and found that the first response time was 13 ms and then it took 1.5 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.
norvasc.com performance score
name
value
score
weighting
Value8.1 s
0/100
10%
Value25.2 s
0/100
25%
Value11.1 s
6/100
10%
Value730 ms
40/100
30%
Value0.525
14/100
15%
Value25.4 s
0/100
10%
13 ms
11 ms
203 ms
11 ms
85 ms
Our browser made a total of 154 requests to load all elements on the main page. We found that 90% of them (139 requests) were addressed to the original Norvasc.com, 8% (12 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Cdn.jwplayer.com. The less responsive or slowest element that took the longest time to load (391 ms) belongs to the original domain Norvasc.com.
Page size can be reduced by 2.7 MB (72%)
3.7 MB
1.1 MB
In fact, the total size of Norvasc.com main page is 3.7 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. Only a small number of websites need less resources to load. Javascripts take 2.7 MB which makes up the majority of the site volume.
Potential reduce by -8 B
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 web page is already compressed.
Potential reduce by 68.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, NORVASC needs image optimization as it can save up to 68.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.2 MB
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 2.2 MB or 79% of the original size.
Potential reduce by 444.5 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. Norvasc.com needs all CSS files to be minified and compressed as it can save up to 444.5 kB or 86% of the original size.
Number of requests can be reduced by 112 (81%)
139
27
The browser has sent 139 CSS, Javascripts, AJAX and image requests in order to completely render the main page of NORVASC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 88 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
norvasc.com
13 ms
www.norvasc.com
11 ms
www.norvasc.com
203 ms
bootstrap-grid-24.css
11 ms
mediaelementplayer.css
85 ms
mediaelementplayer-legacy.css
98 ms
font-awesomemin.css
103 ms
fullcalendar.css
113 ms
jquerymcustomscrollbar.css
99 ms
jquery-ui.css
101 ms
author.css
109 ms
core.css
134 ms
file-type-icons.css
134 ms
grayscale-mode.css
133 ms
reset.css
148 ms
ada-theme.css
140 ms
forms.css
149 ms
interstitials.css
164 ms
jquery-uimin.css
162 ms
scrollbar.css
161 ms
faq.css
167 ms
about.css
177 ms
style.css
179 ms
mobile-isi.css
182 ms
subpages.css
205 ms
responsive.css
201 ms
norvasc.css
202 ms
norvasc_mobile.css
208 ms
jquery-351.js
218 ms
wusB1GPX.js
22 ms
ie-origin-fix.js
216 ms
xaquery.js
258 ms
moment.js
216 ms
lo-dash.js
312 ms
modernizr.js
313 ms
galleria-157.js
390 ms
fullcalendar.js
391 ms
gcal.js
389 ms
jqueryuitouch-punchmin.js
389 ms
hammer.js
387 ms
backbone-min.js
383 ms
typeahead.js
330 ms
jquerymcustomscrollbar.js
319 ms
flash-polyfill.js
317 ms
mediaelement-and-player.js
316 ms
dailymotion.js
314 ms
facebook.js
308 ms
soundcloud.js
389 ms
twitch.js
369 ms
vimeo.js
367 ms
xa.js
366 ms
observer.js
359 ms
partial-design-highlight.js
351 ms
google-maps-connector.js
370 ms
component-location-service.js
356 ms
component-map.js
372 ms
component-location-service.js
354 ms
component-search.js
370 ms
component-search-ajax.js
361 ms
css2
32 ms
component-search-base-model.js
363 ms
component-search-base-view.js
363 ms
component-search-box.js
341 ms
component-search-facet-data.js
341 ms
component-search-facet-summary.js
339 ms
component-search-facet-dropdown.js
338 ms
gtm.js
201 ms
component-search-facet-managed-range.js
356 ms
component-search-facet-range-slider.js
357 ms
component-search-facet-slider.js
316 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
158 ms
KFOlCnqEu92Fr1MmYUtvAw.ttf
238 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
254 ms
KFOmCnqEu92Fr1Me5Q.ttf
255 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
255 ms
KFOkCnqEu92Fr1MmgWxP.ttf
254 ms
component-search-load-more.js
318 ms
component-search-location-filter.js
261 ms
component-search-page-selector.js
186 ms
component-search-page-size.js
188 ms
component-search-parameters.js
190 ms
component-search-query.js
192 ms
component-search-radius-filter.js
190 ms
component-search-results.js
189 ms
component-search-results-count.js
173 ms
component-search-results-filter.js
172 ms
component-search-sort.js
172 ms
component-search-url.js
173 ms
component-search-variant-filter.js
174 ms
component-search-service.js
174 ms
component-search-router.js
175 ms
KFOkCnqEu92Fr1Mu52xP.ttf
98 ms
KFOjCnqEu92Fr1Mu51S7ABc9.ttf
125 ms
KFOjCnqEu92Fr1Mu51TjARc9.ttf
122 ms
KFOiCnqEu92Fr1Mu51QrIzc.ttf
122 ms
KFOjCnqEu92Fr1Mu51TzBhc9.ttf
123 ms
KFOjCnqEu92Fr1Mu51TLBBc9.ttf
122 ms
component-search-facet-daterange.js
94 ms
accessibility.js
95 ms
component-accordions.js
97 ms
component-archive.js
97 ms
component-breadcrumb.js
96 ms
component-carousel.js
92 ms
component-container.js
81 ms
component-disqus.js
83 ms
component-facebook.js
68 ms
component-flash.js
67 ms
component-flip.js
64 ms
component-fullcalendar.js
65 ms
component-galleria.js
60 ms
component-language-selector.js
61 ms
component-navigation.js
62 ms
component-overlay.js
65 ms
component-snippet.js
63 ms
component-social.js
39 ms
component-tabs.js
39 ms
component-toggle.js
43 ms
component-video.js
44 ms
component-video-playlist.js
43 ms
details-polyfill.js
42 ms
fixheight.js
46 ms
search-fixheight.js
47 ms
resolveconflicts.js
49 ms
ada-theme.js
50 ms
apiscripts.js
50 ms
common.js
52 ms
faq.js
52 ms
interstitials.js
56 ms
sidebar.js
56 ms
viatris_logo_header.png
94 ms
nor_logo_rerelease.png
91 ms
norvasc_savings_card_0.png
93 ms
saving_mobile_logo.png
89 ms
expand-collapse-close-button.png
87 ms
25_years.png
88 ms
blood_pressure_icon.png
93 ms
ongoing_commitment_to_product_quality_and_safety_monitoring.png
92 ms
daw.png
115 ms
rx.png
116 ms
pill_bottle.png
115 ms
norvasc_25.png
107 ms
norvasc_5.png
132 ms
norvasc_10.png
132 ms
norvasc_savings_card_0_564x369.png
131 ms
expand-collapse-button.png
129 ms
footer-viatris-logo.png
176 ms
about_bg.png
129 ms
savings_bg.png
147 ms
faq_bg.png
135 ms
resources_bg.png
140 ms
norvasc_background_desktop_cj.jpg
134 ms
select-arrow.png
151 ms
anchor-blue-arrow.png
140 ms
loader.gif
143 ms
norvasc.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
norvasc.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
norvasc.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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Norvasc.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 Norvasc.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.
norvasc.com
Open Graph description is not detected on the main page of NORVASC. 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: