4.9 sec in total
393 ms
2.8 sec
1.7 sec
Visit abilify.com now to see the best up-to-date ABILIFY content for United States and also check out these interesting facts you probably never knew about abilify.com
Save on brand-name ABILIFY. Get a Savings Card and pay as little as $5. Conditions apply.
Visit abilify.comWe analyzed Abilify.com page load time and found that the first response time was 393 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
abilify.com performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value9.5 s
0/100
25%
Value9.8 s
10/100
10%
Value7,320 ms
0/100
30%
Value0.249
50/100
15%
Value15.2 s
7/100
10%
393 ms
155 ms
152 ms
202 ms
209 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 83% of them (59 requests) were addressed to the original Abilify.com, 10% (7 requests) were made to Fast.fonts.com and 3% (2 requests) were made to S.btstatic.com. The less responsive or slowest element that took the longest time to load (754 ms) belongs to the original domain Abilify.com.
Page size can be reduced by 1.1 MB (57%)
1.9 MB
822.3 kB
In fact, the total size of Abilify.com main page is 1.9 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. Javascripts take 699.5 kB which makes up the majority of the site volume.
Potential reduce by 82.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 32.6 kB, which is 35% 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 82.0 kB or 87% of the original size.
Potential reduce by 49.6 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. ABILIFY images are well optimized though.
Potential reduce by 556.3 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 556.3 kB or 80% of the original size.
Potential reduce by 412.6 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. Abilify.com needs all CSS files to be minified and compressed as it can save up to 412.6 kB or 89% of the original size.
Number of requests can be reduced by 16 (25%)
64
48
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ABILIFY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
abilify.com
393 ms
reset.css
155 ms
normalize.min.css
152 ms
mediaelementplayer.min.css
202 ms
video-popup.css
209 ms
main_home.css
375 ms
main_common.css
282 ms
jqtransform.css
218 ms
a2f2c165-ea15-45c5-ac30-d7053444cef1.css
111 ms
jquery-1.7.2.min.js
277 ms
lib.js
587 ms
mediaelement-and-player.js
563 ms
script.js
717 ms
jquery.jqtransform.js
313 ms
enscroll-0.6.1.min.js
314 ms
jquery.jplayer.min.js
754 ms
tag.js
636 ms
menu_nav_patch.png
500 ms
menu_nav_patch_navyblue.png
500 ms
download-this-card-hover.png
496 ms
get-ans-hover.png
497 ms
view-tips-hover.png
497 ms
get-savings-normal.png
489 ms
download-discussion-hover.png
497 ms
brand-name-bg-hover.png
511 ms
home-page-callout-hover.png
508 ms
home-page-callout-right-hover.png
509 ms
sub-page-callout-hover.png
510 ms
header-bg.png
496 ms
abilify-logo.png
506 ms
_component_copaycard.png
510 ms
pdf-icon.png
510 ms
border-right-img.png
494 ms
heading-img.png
494 ms
home-bg.jpg
555 ms
savings_card_new.png
554 ms
brand_new_border.png
555 ms
CRM_program.png
581 ms
right-cotner-img.png
549 ms
saving-bg-content.png
550 ms
yello-bullet.gif
550 ms
brandcard_mob.png
558 ms
support_program_mob.png
559 ms
defaulpg-collout-bg.png
563 ms
border-rgt.png
560 ms
vdo_callout.png
597 ms
watch_vdo_btn.png
560 ms
saving-card-faqs-que.png
561 ms
get-ans.png
561 ms
close-btn.png
618 ms
btn-close.png
579 ms
popup_triangle.png
600 ms
btn-close.png
304 ms
arrow_condition.png
294 ms
img_footer_yellowband.gif
290 ms
logo_otsuka.png
290 ms
popup_triangle_right.png
283 ms
usingvideo-bg.png
277 ms
video_step1.png
276 ms
video_step2.png
276 ms
video_step3.png
267 ms
61509a4a-55a0-4207-a78b-902f7a2cc685.woff
104 ms
41c174b1-68c1-41b7-a19f-5ec80929b115.woff
105 ms
060031a3-ab11-4f91-9dd4-6b39458f5109.woff
104 ms
08fe22ab-0517-4203-bcc9-1ba2ca45f40c.woff
83 ms
de902d7e-9849-4880-b8fe-966b186b110c.woff
83 ms
b547d31d-69fc-40d6-8013-e9b6f0b38df0.woff
82 ms
tag
207 ms
8c37e664ade9dfb163b2325cee2a84ed042088a4.js
47 ms
activityi;src=4511196;type=abili0;cat=abili0;ord=2142523066140.7114
100 ms
s36714323328342
17 ms
abilify.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
abilify.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
abilify.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
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Abilify.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 Abilify.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.
abilify.com
Open Graph description is not detected on the main page of ABILIFY. 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: