6 sec in total
131 ms
5 sec
848 ms
Welcome to amgen.eu homepage info - get ready to check Amgen best content right away, or after learning these important things about amgen.eu
A biotechnology pioneer, Amgen has grown to be world's leading independent biotech company. We discover, develop, manufacture & deliver human therapeutics.
Visit amgen.euWe analyzed Amgen.eu page load time and found that the first response time was 131 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
amgen.eu performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value10.3 s
0/100
25%
Value8.7 s
16/100
10%
Value820 ms
35/100
30%
Value0
100/100
15%
Value14.6 s
8/100
10%
131 ms
268 ms
965 ms
52 ms
73 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 94% of them (137 requests) were addressed to the original Amgen.eu, 3% (5 requests) were made to Use.typekit.net and 1% (1 request) were made to Consent.cookiebot.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Amgen.eu.
Page size can be reduced by 630.6 kB (23%)
2.7 MB
2.1 MB
In fact, the total size of Amgen.eu main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 178.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. This page needs HTML code to be minified as it can gain 56.2 kB, which is 27% 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 178.4 kB or 86% of the original size.
Potential reduce by 328.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, Amgen needs image optimization as it can save up to 328.1 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 61.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. This website has mostly compressed JavaScripts.
Potential reduce by 62.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. Amgen.eu needs all CSS files to be minified and compressed as it can save up to 62.3 kB or 37% of the original size.
Number of requests can be reduced by 106 (81%)
131
25
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Amgen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 78 to 1 for JavaScripts and from 30 to 1 for CSS and as a result speed up the page load time.
amgen.eu
131 ms
amgen.eu
268 ms
www.amgen.eu
965 ms
uc.js
52 ms
gtm.js
73 ms
bootstrap-grid.css
70 ms
mediaelementplayer.css
141 ms
mediaelementplayer-legacy.css
193 ms
font-awesomemin.css
195 ms
fullcalendar.css
198 ms
jquerymCustomScrollbar.css
202 ms
jquery-ui.css
200 ms
author.css
207 ms
core.css
256 ms
file-type-icons.css
263 ms
grayscale-mode.css
258 ms
reset.css
264 ms
search-results-pagination.css
265 ms
search-results-style.css
277 ms
search-suggest-style.css
322 ms
GDPR.css
322 ms
GDPR.css
332 ms
ccpa.css
333 ms
global-styles.css
398 ms
amgen-eu-custom.css
455 ms
cl-8shapes-custom-CL.css
442 ms
cl-bootstrap-custom.css
424 ms
cl-customizedsearch.css
428 ms
main.css
463 ms
overlay.css
491 ms
privacy-warning.css
514 ms
search-custom.css
526 ms
styles.css
540 ms
amgen-eu.css
570 ms
amgen-eu-style.css
557 ms
VisitorIdentification.js
565 ms
jquery-331min.js
588 ms
svg4everybodymin-1.js
606 ms
polyfillmin.js
667 ms
jquery-ui.js
697 ms
bootstrap.js
622 ms
searchinputsanitizer.js
576 ms
ie-origin-fix.js
516 ms
xaquery.js
646 ms
moment.js
582 ms
lo-dash.js
583 ms
modernizr.js
577 ms
galleria-161.js
578 ms
fullcalendar.js
779 ms
gcal.js
577 ms
jqueryuitouch-punchmin.js
575 ms
hammer.js
572 ms
backbone-min.js
675 ms
typeahead.js
762 ms
jquerymCustomScrollbar.js
748 ms
flash-polyfill.js
704 ms
mediaelement-and-player.js
774 ms
dailymotion.js
699 ms
facebook.js
775 ms
soundcloud.js
683 ms
twitch.js
678 ms
vimeo.js
679 ms
xa.js
650 ms
observer.js
722 ms
partial-design-highlight.js
718 ms
QueryStringProcessor.js
692 ms
accessibility.js
671 ms
component-accordions.js
655 ms
component-archive.js
639 ms
component-breadcrumb.js
658 ms
component-carousel.js
661 ms
component-container.js
636 ms
component-disqus.js
623 ms
component-facebook.js
622 ms
component-flash.js
600 ms
component-flip.js
649 ms
component-fullcalendar.js
643 ms
component-galleria.js
622 ms
index.html
303 ms
component-language-selector.js
536 ms
component-navigation.js
530 ms
component-overlay.js
530 ms
component-snippet.js
579 ms
d
289 ms
d
329 ms
d
356 ms
d
356 ms
d
376 ms
component-social.js
580 ms
component-tabs.js
537 ms
component-toggle.js
540 ms
component-video.js
543 ms
component-video-playlist.js
438 ms
details-polyfill.js
463 ms
fixheight.js
417 ms
search-fixheight.js
413 ms
resolveconflicts.js
410 ms
AccordinGtmTracking.js
414 ms
BrightCoverVideoGTMTracking.js
378 ms
GTMinlineScript.js
395 ms
GTMinlineScriptCL.js
389 ms
trackGTM.js
398 ms
cl-search-results.js
401 ms
cl-search-suggest.js
405 ms
GDPR.js
380 ms
8shapes-custom-CL.js
410 ms
amgen-eu-custom.js
412 ms
cl-footer-CL.js
414 ms
cl-header-nav-CL.js
486 ms
cl-search-component.js
432 ms
jscookie.js
426 ms
modal-popup.js
468 ms
quantum-CL.js
463 ms
search-custom.js
469 ms
selectHide.js
483 ms
modal-popup-custom.js
487 ms
brightcove.js
683 ms
amgen-eu.svg
466 ms
search_new.svg
494 ms
fontawesome-webfont.woff
514 ms
fontawesome-webfont-woff.woff
784 ms
fontawesome-webfont-woff.woff
530 ms
amgen-eu.svg
504 ms
search_new.svg
506 ms
logo-amgen_1.svg
728 ms
logo-amgen.svg
725 ms
an-investment-we-cant-ignore-home-page.jpg
720 ms
healthcare-as-an-investment-tile.jpg
719 ms
home-eu-phrma.jpg
772 ms
Together-we-can-do-anything-thumbnail.jpg
705 ms
Report-image.png
791 ms
Teaser-image-_experts.jpg
708 ms
flag-thumbnail.jpg
697 ms
AmgenHistory_FeaturedNews_HomepageImage.jpg
790 ms
amgen-blue.svg
799 ms
amgen-new-header-no-logo-01.jpg
885 ms
overlay-pattern.png
755 ms
Amgen_VPII_website.jpg
786 ms
overlay-pattern.png
827 ms
Amgen_SD-website-banner.jpg
838 ms
amgen-inspires.png
890 ms
bg-openings.jpg
817 ms
404
1076 ms
fontawesome-webfont.ttf
82 ms
404
638 ms
amgen.eu accessibility score
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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.
amgen.eu 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
amgen.eu 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
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Amgen.eu 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 Amgen.eu main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
amgen.eu
Open Graph description is not detected on the main page of Amgen. 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: