Tools & Wizards About Us
benefix.com screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

benefix.com

Home | BeneFɪx (Coagulation Factor IX [Recombinant]) | Safety Info

Page Load Speed

3.5 sec in total

First Response

258 ms

Resources Loaded

3 sec

Page Rendered

258 ms

benefix.com screenshot

About Website

Welcome to benefix.com homepage info - get ready to check Bene F IX best content for United States right away, or after learning these important things about benefix.com

See risks & benefits. Learn about BeneFɪx (Coagulation Factor IX [Recombinant]) for once-weekly prophylaxis and on-demand use in patients with hemophilia B.

Visit benefix.com

Key Findings

We analyzed Benefix.com page load time and found that the first response time was 258 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 60% of websites can load faster.

Performance Metrics

benefix.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value2,080 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0.945

3/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

benefix.com

258 ms

www.benefix.com

502 ms

bootstrap.js

223 ms

hydration.css

46 ms

launch-EN1368dd8ee61d44a39fc66850d298a763.min.js

53 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 74% of them (59 requests) were addressed to the original Benefix.com, 13% (10 requests) were made to Use.typekit.net and 9% (7 requests) were made to Pkg-cdn.digitalpfizer.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Benefix.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 217.5 kB (17%)

Content Size

1.3 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Benefix.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. 50% of websites need less resources to load. Images take 811.5 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 75.3 kB

  • Original 84.3 kB
  • After minification 52.4 kB
  • After compression 9.0 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 31.9 kB, which is 38% 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 75.3 kB or 89% of the original size.

Image Optimization

-16%

Potential reduce by 131.8 kB

  • Original 811.5 kB
  • After minification 679.7 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, Bene F IX needs image optimization as it can save up to 131.8 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-2%

Potential reduce by 4.6 kB

  • Original 223.7 kB
  • After minification 223.7 kB
  • After compression 219.0 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.

CSS Optimization

-4%

Potential reduce by 5.8 kB

  • Original 137.0 kB
  • After minification 137.0 kB
  • After compression 131.2 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. Benefix.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 51 (78%)

Requests Now

65

After Optimization

14

  • Images
  • JavaScript
  • CSS

The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Bene F IX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 36 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

benefix.com

benefix.com

258 ms

www.benefix.com

www.benefix.com

502 ms

bootstrap.js

bootstrap.js

223 ms

hydration.css

hydration.css

46 ms

launch-EN1368dd8ee61d44a39fc66850d298a763.min.js

launch-EN1368dd8ee61d44a39fc66850d298a763.min.js

53 ms

8a0093ad54059b1010fae7235f45dfde.css

8a0093ad54059b1010fae7235f45dfde.css

339 ms

jquery.min.js

jquery.min.js

346 ms

menuu1.css

menuu1.css

287 ms

benefix-menu.css

benefix-menu.css

251 ms

menu.js

menu.js

209 ms

benefix-footer.css

benefix-footer.css

308 ms

benefix-isi.css

benefix-isi.css

488 ms

homepage.css

homepage.css

371 ms

fonts.css

fonts.css

526 ms

benefix-floating-isi.css

benefix-floating-isi.css

448 ms

aboutpage.css

aboutpage.css

568 ms

benefix-middle-container.css

benefix-middle-container.css

555 ms

breadcrumb.css

breadcrumb.css

557 ms

resources-patient-affairs-liaisons.css

resources-patient-affairs-liaisons.css

629 ms

jquery.uniform.js

jquery.uniform.js

821 ms

benefix-floating-isi.js

benefix-floating-isi.js

751 ms

what-is-benefix.css

what-is-benefix.css

760 ms

once-weekly-prophylaxis-01.css

once-weekly-prophylaxis-01.css

715 ms

unsubscribe.css

unsubscribe.css

744 ms

mpl4ebc.css

mpl4ebc.css

116 ms

benefix-procured-font.css

benefix-procured-font.css

696 ms

indication.css

indication.css

757 ms

resources-landing.css

resources-landing.css

877 ms

Benefix-travel-case.css

Benefix-travel-case.css

963 ms

advocacy-group.css

advocacy-group.css

921 ms

exit-link.js

exit-link.js

820 ms

exit-link.css

exit-link.css

1049 ms

sticky.js

sticky.js

1001 ms

custom_analytics.js

custom_analytics.js

887 ms

helix.esm.js

helix.esm.js

44 ms

helix.js

helix.js

47 ms

helix-extras.esm.js

helix-extras.esm.js

340 ms

helix-extras.js

helix-extras.js

45 ms

analytics_footer.js

analytics_footer.js

1132 ms

style-fixes.css

style-fixes.css

970 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

1193 ms

css_tGTNtRAsNJmcVz4r7F6YCijbrQGDbBmziHSrRd1Stqc.css

css_tGTNtRAsNJmcVz4r7F6YCijbrQGDbBmziHSrRd1Stqc.css

1192 ms

css_YmuMqUm--85MDg6GF8xFt60xnxOSYeKArfr5yk0-sVc.css

css_YmuMqUm--85MDg6GF8xFt60xnxOSYeKArfr5yk0-sVc.css

1133 ms

css_jENQOQqZCRFGZK__DTefxYiXR2RUf03k1ugj3_Vg7vk.css

css_jENQOQqZCRFGZK__DTefxYiXR2RUf03k1ugj3_Vg7vk.css

1192 ms

css_hUItx_P1oCWlFy-S87Lo4wc6laMJcOX7en4bBOS6_Dc.css

css_hUItx_P1oCWlFy-S87Lo4wc6laMJcOX7en4bBOS6_Dc.css

1288 ms

css_DrzlIex2u-bBfSoyQWyMsPPmAvLQKzOQLM9Wg06acbE.css

css_DrzlIex2u-bBfSoyQWyMsPPmAvLQKzOQLM9Wg06acbE.css

1027 ms

p.css

p.css

27 ms

css2

css2

38 ms

css_nVYbsGPs7pX6-2BqJEpRSZMilFpXiA9wvhm5BwcsZvI.css

css_nVYbsGPs7pX6-2BqJEpRSZMilFpXiA9wvhm5BwcsZvI.css

951 ms

indication-exitpopup.js

indication-exitpopup.js

1174 ms

survey-prod.js

survey-prod.js

1153 ms

custom.js

custom.js

1042 ms

helix.css

helix.css

315 ms

helix-extras.css

helix-extras.css

473 ms

phone-icon.png

phone-icon.png

358 ms

newlogo25.png

newlogo25.png

416 ms

logo.jpg

logo.jpg

325 ms

close-btnn.png

close-btnn.png

372 ms

f73b8646daeb4ac4f432a29c25f5363e.png

f73b8646daeb4ac4f432a29c25f5363e.png

508 ms

fbe34ac809b574c4dd12d6e539873242.png

fbe34ac809b574c4dd12d6e539873242.png

570 ms

Group-10142x-513516817983641-1518017.webp

Group-10142x-513516817983641-1518017.webp

569 ms

home-callout-icon-1.png

home-callout-icon-1.png

431 ms

home-callout-icon-3.png

home-callout-icon-3.png

599 ms

home-callout-icon-4.png

home-callout-icon-4.png

585 ms

benefix-footer-pfizer-logo.png

benefix-footer-pfizer-logo.png

488 ms

c9f5bbf03857da7f42e1ff37e2d494ff.png

c9f5bbf03857da7f42e1ff37e2d494ff.png

568 ms

d

d

35 ms

d

d

43 ms

Roboto-Regular.woff

Roboto-Regular.woff

430 ms

d

d

45 ms

d

d

49 ms

d

d

46 ms

08cb8f79715774f9a6285ee7db2919a3.woff

08cb8f79715774f9a6285ee7db2919a3.woff

605 ms

d

d

50 ms

d

d

46 ms

d

d

46 ms

d

d

47 ms

373c79a0bcb34d794c629a42aed22172.png

373c79a0bcb34d794c629a42aed22172.png

515 ms

11eabca2251325cfc5589c9c6fb57b46.ttf

11eabca2251325cfc5589c9c6fb57b46.ttf

52 ms

bootstrap.css

bootstrap.css

192 ms

Accessibility Review

benefix.com accessibility score

98

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

benefix.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

benefix.com SEO score

90

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Benefix.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 Benefix.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.

Social Sharing Optimization

benefix.com

Open Graph data is detected on the main page of Bene F IX. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: