3.2 sec in total
424 ms
2.6 sec
177 ms
Visit jakavi.com now to see the best up-to-date JAKAVI content and also check out these interesting facts you probably never knew about jakavi.com
JAKAVI® (ruxolitinib) for the treatment of myelofibrosis and for the treatment of polycythaemia vera in patients resistant to or intolerant of hydroxyurea.
Visit jakavi.comWe analyzed Jakavi.com page load time and found that the first response time was 424 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
jakavi.com performance score
name
value
score
weighting
Value2.8 s
58/100
10%
Value6.5 s
9/100
25%
Value5.3 s
58/100
10%
Value490 ms
59/100
30%
Value0.109
87/100
15%
Value8.2 s
41/100
10%
424 ms
565 ms
478 ms
59 ms
107 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 79% of them (37 requests) were addressed to the original Jakavi.com, 9% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Player.ooyala.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Player.ooyala.com.
Page size can be reduced by 206.7 kB (35%)
588.3 kB
381.5 kB
In fact, the total size of Jakavi.com main page is 588.3 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. 40% of websites need less resources to load. Images take 333.3 kB which makes up the majority of the site volume.
Potential reduce by 70.9 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 17.1 kB, which is 19% 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 70.9 kB or 79% of the original size.
Potential reduce by 21.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. JAKAVI images are well optimized though.
Potential reduce by 34 B
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 114.7 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. Jakavi.com needs all CSS files to be minified and compressed as it can save up to 114.7 kB or 82% of the original size.
Number of requests can be reduced by 7 (18%)
38
31
The browser has sent 38 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JAKAVI. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
www.jakavi.com
424 ms
bootstrap.min.css
565 ms
font-awesome.min.css
478 ms
styles
59 ms
libs
107 ms
scripts
62 ms
ee8497d2d4fe4f5c86c8e5d949d7a90a
1386 ms
jakavi_logo_tagline_aligned.svg
320 ms
icon_spleen_reduction.svg
337 ms
icon_symptom_improvement.svg
347 ms
icon_survival_benefit.svg
393 ms
icon_moa.svg
651 ms
icon_dosing.svg
654 ms
icon_safety_profile.svg
652 ms
icon_primary_endpoint.svg
688 ms
icon_haematocrit_control.svg
751 ms
icon_comprehensive_haematologic_control.svg
887 ms
icon_safety.svg
914 ms
novartis_oncology_logo.svg
917 ms
css
23 ms
top-icons.png
403 ms
socials17x17.png
372 ms
mf_home_page_art.jpg
606 ms
separator-left.png
574 ms
separator-right.png
608 ms
GillSansStd.woff
853 ms
fontawesome-webfont.woff
1175 ms
GillSansStd-Light.woff
803 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
6 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
12 ms
Jzo62I39jc0gQRrbndN6nfesZW2xOQ-xsNqO47m55DA.ttf
13 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
12 ms
GillSansStd-Bold.woff
1051 ms
ga.js
43 ms
icon_spleen_reduction.svg
49 ms
icon_symptom_improvement.svg
42 ms
icon_survival_benefit.svg
49 ms
icon_moa.svg
79 ms
icon_dosing.svg
80 ms
icon_safety_profile.svg
83 ms
icon_primary_endpoint.svg
95 ms
icon_haematocrit_control.svg
96 ms
icon_comprehensive_haematologic_control.svg
97 ms
icon_safety.svg
99 ms
ooyala_storage.html
72 ms
__utm.gif
25 ms
nr-885.min.js
45 ms
jakavi.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.
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
Links do not have a discernible name
<object> elements do not have alternate text
jakavi.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
Missing source maps for large first-party JavaScript
jakavi.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 doesn't use legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jakavi.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 Jakavi.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.
jakavi.com
Open Graph description is not detected on the main page of JAKAVI. 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: