Tools & Wizards About Us
velcade-hcp.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

velcade-hcp.com

Explore Takeda Oncology U.S. Approved Medicines | Takeda Oncology

Page Load Speed

694 ms in total

First Response

27 ms

Resources Loaded

562 ms

Page Rendered

105 ms

velcade-hcp.com screenshot

About Website

Click here to check amazing Velcade Hcp content. Otherwise, check out these important facts you probably never knew about velcade-hcp.com

Discover Takeda Oncology's innovative cancer medicines approved in the United States of America that aim to improve patient outcomes.

Visit velcade-hcp.com

Key Findings

We analyzed Velcade-hcp.com page load time and found that the first response time was 27 ms and then it took 667 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

velcade-hcp.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value7.3 s

28/100

10%

TBT (Total Blocking Time)

Value1,510 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

velcade-hcp.com

27 ms

62 ms

gtm.js

90 ms

container_8RFPFIX1.js

42 ms

datadog-rum-v4.js

34 ms

Our browser made a total of 104 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Velcade-hcp.com, 85% (88 requests) were made to Takedaoncology.com and 4% (4 requests) were made to Aim-tag.hcn.health. The less responsive or slowest element that took the longest time to load (422 ms) relates to the external source Takeda.matomo.cloud.

Page Optimization Overview & Recommendations

Page size can be reduced by 108.6 kB (49%)

Content Size

222.1 kB

After Optimization

113.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Velcade-hcp.com main page is 222.1 kB. 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. HTML takes 138.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 108.3 kB

  • Original 138.4 kB
  • After minification 138.3 kB
  • After compression 30.1 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 108.3 kB or 78% of the original size.

Image Optimization

-17%

Potential reduce by 18 B

  • Original 103 B
  • After minification 85 B

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, Velcade Hcp needs image optimization as it can save up to 18 B or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 282 B

  • Original 83.7 kB
  • After minification 83.7 kB
  • After compression 83.4 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.

Requests Breakdown

Number of requests can be reduced by 88 (92%)

Requests Now

96

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

velcade-hcp.com

velcade-hcp.com

27 ms

62 ms

gtm.js

gtm.js

90 ms

container_8RFPFIX1.js

container_8RFPFIX1.js

42 ms

datadog-rum-v4.js

datadog-rum-v4.js

34 ms

c519d5e30826dfa8.css

c519d5e30826dfa8.css

20 ms

c6727958a5da520b.css

c6727958a5da520b.css

41 ms

f714de409d1b43fb.css

f714de409d1b43fb.css

65 ms

99f1298953809fb9.css

99f1298953809fb9.css

66 ms

8a81431e0111eb38.css

8a81431e0111eb38.css

64 ms

ed452b8d3cb9b5f5.css

ed452b8d3cb9b5f5.css

65 ms

e36dc02c97d66a94.css

e36dc02c97d66a94.css

63 ms

334b3874b222d47d.css

334b3874b222d47d.css

67 ms

6ff744ee6873a788.css

6ff744ee6873a788.css

66 ms

35f0bf5638c2f65f.css

35f0bf5638c2f65f.css

66 ms

b6e45cbc516c846f.css

b6e45cbc516c846f.css

67 ms

252350acbdc21608.css

252350acbdc21608.css

68 ms

65ed5f4e45e172d1.css

65ed5f4e45e172d1.css

69 ms

9f82b9d0d0c21666.css

9f82b9d0d0c21666.css

67 ms

f544ebc22208d8fd.css

f544ebc22208d8fd.css

68 ms

697dd36401a33942.css

697dd36401a33942.css

70 ms

eb69599eec34d7d6.css

eb69599eec34d7d6.css

75 ms

b7f105bd9500c480.css

b7f105bd9500c480.css

73 ms

cb5012c0c2e9150c.css

cb5012c0c2e9150c.css

86 ms

3fc36e44cf2f943f.css

3fc36e44cf2f943f.css

81 ms

08eb4b1e92fe81cb.css

08eb4b1e92fe81cb.css

82 ms

15ef2fffadd72147.css

15ef2fffadd72147.css

106 ms

d5a466a385fa8ca2.css

d5a466a385fa8ca2.css

83 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

122 ms

client.js

client.js

62 ms

OtAutoBlock.js

OtAutoBlock.js

67 ms

otSDKStub.js

otSDKStub.js

85 ms

8913.8618515d6a868dda.js

8913.8618515d6a868dda.js

171 ms

1735.6e13465857a46e49.js

1735.6e13465857a46e49.js

105 ms

982.49d90b2e7c60d920.js

982.49d90b2e7c60d920.js

163 ms

29107295.54c46f60208f68c8.js

29107295.54c46f60208f68c8.js

163 ms

3707.581b5e92eb05e247.js

3707.581b5e92eb05e247.js

169 ms

8378.275f2173944fc013.js

8378.275f2173944fc013.js

168 ms

1467.47739fc584c2757a.js

1467.47739fc584c2757a.js

168 ms

4676.f60b29e1327e8187.js

4676.f60b29e1327e8187.js

167 ms

9669.c8815bc7bc3ead79.js

9669.c8815bc7bc3ead79.js

174 ms

8212.48487cb9786df9db.js

8212.48487cb9786df9db.js

174 ms

9327.f98e8218a85cc756.js

9327.f98e8218a85cc756.js

175 ms

8079.27f1c84ee15713c1.js

8079.27f1c84ee15713c1.js

170 ms

738.f9148f949790a9ae.js

738.f9148f949790a9ae.js

159 ms

675.a1a1af359fe4d930.js

675.a1a1af359fe4d930.js

142 ms

matomo.php

matomo.php

422 ms

286.3545219d6ff7852f.js

286.3545219d6ff7852f.js

119 ms

2066.c95332614bc5ec40.js

2066.c95332614bc5ec40.js

121 ms

3829.7b1cdd8ec4cb42d9.js

3829.7b1cdd8ec4cb42d9.js

119 ms

7588.a4ac813d2e46add1.js

7588.a4ac813d2e46add1.js

119 ms

4818.bb240cb895090fe6.js

4818.bb240cb895090fe6.js

119 ms

7114.858c94c81f7ba61e.js

7114.858c94c81f7ba61e.js

119 ms

9413.99fc3b9a6a9bfe5b.js

9413.99fc3b9a6a9bfe5b.js

124 ms

9838.34be64ecf5398e95.js

9838.34be64ecf5398e95.js

119 ms

8660.4a197c146bc5993e.js

8660.4a197c146bc5993e.js

119 ms

288.1751a2b1b675e888.js

288.1751a2b1b675e888.js

118 ms

3644.41c81531f05f80c9.js

3644.41c81531f05f80c9.js

119 ms

14.09d630d4b932f291.js

14.09d630d4b932f291.js

119 ms

2600.bb529bdb71abf7ad.js

2600.bb529bdb71abf7ad.js

117 ms

761.9af74b87b990a136.js

761.9af74b87b990a136.js

117 ms

configs.php

configs.php

379 ms

5259.1f3e11a7a6918dd9.js

5259.1f3e11a7a6918dd9.js

116 ms

5321.40e9134082939eec.js

5321.40e9134082939eec.js

115 ms

9634.a0250f8010de76bc.js

9634.a0250f8010de76bc.js

109 ms

3085.1e018d7cfcba1d94.js

3085.1e018d7cfcba1d94.js

106 ms

2255.ffe8f76c47cdaad9.js

2255.ffe8f76c47cdaad9.js

107 ms

6899.34c2ed02acee6beb.js

6899.34c2ed02acee6beb.js

115 ms

2279.8819adc9ad64788a.js

2279.8819adc9ad64788a.js

80 ms

transition

transition

46 ms

iframe.html

iframe.html

103 ms

1c21da89-fd19-457f-a6d0-69a1c4fead2d.json

1c21da89-fd19-457f-a6d0-69a1c4fead2d.json

46 ms

6166.84d789d4bb423317.js

6166.84d789d4bb423317.js

37 ms

8211.73055784ab0ae98d.js

8211.73055784ab0ae98d.js

37 ms

1118.b7a94127c8bbafda.js

1118.b7a94127c8bbafda.js

33 ms

2737.9f56e1c1b410b11c.js

2737.9f56e1c1b410b11c.js

57 ms

812.bc3fd270f49cb973.js

812.bc3fd270f49cb973.js

53 ms

1078.da84bc00ff6589a4.js

1078.da84bc00ff6589a4.js

52 ms

7557.1da5eb9c852f6287.js

7557.1da5eb9c852f6287.js

127 ms

283.12886359ee935697.js

283.12886359ee935697.js

51 ms

5298.52a7022d1727d611.js

5298.52a7022d1727d611.js

49 ms

3029.f552db69430d366e.js

3029.f552db69430d366e.js

60 ms

5866.0eac23fb033fc3f1.js

5866.0eac23fb033fc3f1.js

52 ms

5724.5488b2011e94cf31.js

5724.5488b2011e94cf31.js

59 ms

7133.6baf6024d2fdc8bc.js

7133.6baf6024d2fdc8bc.js

55 ms

6362.eff60ce13337ecb7.js

6362.eff60ce13337ecb7.js

62 ms

9457.ace3bca4eac3ffb2.js

9457.ace3bca4eac3ffb2.js

61 ms

webpack-008ddd2f41b3e2e6.js

webpack-008ddd2f41b3e2e6.js

114 ms

framework-ce84985cd166733a.js

framework-ce84985cd166733a.js

115 ms

main-d09ace4de2a9c53e.js

main-d09ace4de2a9c53e.js

115 ms

_app-cd716749cbc36f2c.js

_app-cd716749cbc36f2c.js

115 ms

%5B%5B...slug%5D%5D-d1ed8493a45c63c4.js

%5B%5B...slug%5D%5D-d1ed8493a45c63c4.js

112 ms

_buildManifest.js

_buildManifest.js

123 ms

_ssgManifest.js

_ssgManifest.js

123 ms

GothamSSm-Book_Web.woff

GothamSSm-Book_Web.woff

125 ms

GothamSSm-Medium_Web.woff

GothamSSm-Medium_Web.woff

123 ms

GothamSSm-Light_Web.woff

GothamSSm-Light_Web.woff

123 ms

GothamSSm-XLight_Web.woff

GothamSSm-XLight_Web.woff

139 ms

GothamSSm-Bold_Web.woff

GothamSSm-Bold_Web.woff

123 ms

GothamSSm-Black_Web.woff

GothamSSm-Black_Web.woff

124 ms

transition.js

transition.js

6 ms

location

location

85 ms

_itu.png

_itu.png

48 ms

22 ms

Accessibility Review

velcade-hcp.com accessibility score

87

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Form elements do not have associated labels

Best Practices

velcade-hcp.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

velcade-hcp.com SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    N/A

  • Encoding

    UTF-8

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

velcade-hcp.com

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