1.2 sec in total
72 ms
776 ms
320 ms
Click here to check amazing HAEGARDA content for United States. Otherwise, check out these important facts you probably never knew about haegarda.com
As a preventive therapy, HAEGARDA can effectively reduce the number of Hereditary Angioedema (HAE) attacks you experience.
Visit haegarda.comWe analyzed Haegarda.com page load time and found that the first response time was 72 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
haegarda.com performance score
name
value
score
weighting
Value2.7 s
60/100
10%
Value10.3 s
0/100
25%
Value5.2 s
60/100
10%
Value140 ms
95/100
30%
Value0.016
100/100
15%
Value9.3 s
31/100
10%
72 ms
136 ms
50 ms
61 ms
42 ms
Our browser made a total of 36 requests to load all elements on the main page. We found that 81% of them (29 requests) were addressed to the original Haegarda.com, 8% (3 requests) were made to Cdn.cookielaw.org and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (416 ms) belongs to the original domain Haegarda.com.
Page size can be reduced by 1.2 MB (30%)
3.8 MB
2.7 MB
In fact, the total size of Haegarda.com main page is 3.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. Images take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 38.2 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 6.5 kB, which is 13% 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 38.2 kB or 78% of the original size.
Potential reduce by 1.1 MB
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, HAEGARDA needs image optimization as it can save up to 1.1 MB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 21.7 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 21.7 kB or 13% of the original size.
Number of requests can be reduced by 7 (29%)
24
17
The browser has sent 24 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HAEGARDA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and as a result speed up the page load time.
haegarda.com
72 ms
www.haegarda.com
136 ms
otSDKStub.js
50 ms
common-css
61 ms
jquery.min.js
42 ms
analytics-core.js
94 ms
jqueryval
58 ms
common
58 ms
22179821-b1f2-4b90-9219-13af86968459.json
189 ms
gtm.js
249 ms
logo-HAEGARDA.svg
186 ms
icon-phone.png
181 ms
Header-text-Graphic.png
192 ms
Icon_6plus.svg
189 ms
99attack.svg
209 ms
95reduced.svg
204 ms
starting-icon.png
204 ms
support-icon.png
202 ms
zahra.png
229 ms
machelle.png
203 ms
trista.png
233 ms
csl-behring-logo-V2.svg
301 ms
vita.png
215 ms
hero-home.png
416 ms
roboto-v20-latin-regular.woff
43 ms
roboto-v20-latin-500.woff
53 ms
roboto-v20-latin-300.woff
54 ms
roboto-v20-latin-100.woff
63 ms
roboto-v20-latin-700.woff
65 ms
roboto-v20-latin-900.woff
65 ms
RobotoCondensed-Regular.woff
119 ms
RobotoCondensed-Light.woff
127 ms
RobotoCondensed-Bold.woff
126 ms
icofont.woff
154 ms
location
38 ms
otBannerSdk.js
22 ms
haegarda.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
[role]s are not contained by their required parent element
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
Image elements do not have [alt] attributes
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
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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.
haegarda.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
General
Impact
Issue
Detected JavaScript libraries
haegarda.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
Image elements do not have [alt] attributes
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 Haegarda.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 Haegarda.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.
haegarda.com
Open Graph description is not detected on the main page of HAEGARDA. 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: