Tools & Wizards About Us
abilify.com screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

abilify.com

ABILIFY® (aripiprazole) | Official Site

Page Load Speed

1.2 sec in total

First Response

80 ms

Resources Loaded

779 ms

Page Rendered

367 ms

abilify.com screenshot

About Website

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.com

Key Findings

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

Performance Metrics

abilify.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value670 ms

44/100

30%

CLS (Cumulative Layout Shift)

Value0.203

61/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

abilify.com

80 ms

www.abilify.com

93 ms

ajax-progress.module.css

20 ms

align.module.css

38 ms

autocomplete-loading.module.css

54 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 89% of them (78 requests) were addressed to the original Abilify.com, 3% (3 requests) were made to Assets.adobedtm.com and 2% (2 requests) were made to Dpm.demdex.net. The less responsive or slowest element that took the longest time to load (226 ms) belongs to the original domain Abilify.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 229.9 kB (22%)

Content Size

1.1 MB

After Optimization

830.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Abilify.com main page is 1.1 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. 60% of websites need less resources to load. Images take 535.0 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 65.8 kB

  • Original 89.8 kB
  • After minification 88.7 kB
  • After compression 24.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 65.8 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 535.0 kB
  • After minification 535.0 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.

JavaScript Optimization

-42%

Potential reduce by 161.4 kB

  • Original 387.4 kB
  • After minification 387.4 kB
  • After compression 226.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 161.4 kB or 42% of the original size.

CSS Optimization

-6%

Potential reduce by 2.8 kB

  • Original 48.1 kB
  • After minification 46.0 kB
  • After compression 45.3 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 66 (85%)

Requests Now

78

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 78 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 11 to 1 for JavaScripts and from 57 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

abilify.com

abilify.com

80 ms

www.abilify.com

www.abilify.com

93 ms

ajax-progress.module.css

ajax-progress.module.css

20 ms

align.module.css

align.module.css

38 ms

autocomplete-loading.module.css

autocomplete-loading.module.css

54 ms

fieldgroup.module.css

fieldgroup.module.css

42 ms

container-inline.module.css

container-inline.module.css

39 ms

clearfix.module.css

clearfix.module.css

42 ms

details.module.css

details.module.css

40 ms

hidden.module.css

hidden.module.css

57 ms

item-list.module.css

item-list.module.css

61 ms

js.module.css

js.module.css

60 ms

nowrap.module.css

nowrap.module.css

62 ms

position-container.module.css

position-container.module.css

57 ms

progress.module.css

progress.module.css

72 ms

reset-appearance.module.css

reset-appearance.module.css

78 ms

resize.module.css

resize.module.css

74 ms

sticky-header.module.css

sticky-header.module.css

87 ms

system-status-counter.css

system-status-counter.css

83 ms

system-status-report-counters.css

system-status-report-counters.css

85 ms

system-status-report-general-info.css

system-status-report-general-info.css

101 ms

tabledrag.module.css

tabledrag.module.css

90 ms

tablesort.module.css

tablesort.module.css

91 ms

tree-child.module.css

tree-child.module.css

100 ms

views.module.css

views.module.css

110 ms

filter.caption.css

filter.caption.css

111 ms

filter.caption.css

filter.caption.css

108 ms

normalize.css

normalize.css

112 ms

normalize-fixes.css

normalize-fixes.css

117 ms

action-links.css

action-links.css

116 ms

breadcrumb.css

breadcrumb.css

122 ms

button.css

button.css

146 ms

collapse-processed.css

collapse-processed.css

130 ms

container-inline.css

container-inline.css

127 ms

details.css

details.css

138 ms

exposed-filters.css

exposed-filters.css

134 ms

field.css

field.css

140 ms

form.css

form.css

140 ms

icons.css

icons.css

150 ms

inline-form.css

inline-form.css

127 ms

item-list.css

item-list.css

129 ms

link.css

link.css

129 ms

links.css

links.css

133 ms

menu.css

menu.css

128 ms

more-link.css

more-link.css

127 ms

pager.css

pager.css

146 ms

tabledrag.css

tabledrag.css

129 ms

tableselect.css

tableselect.css

124 ms

tablesort.css

tablesort.css

128 ms

tabs.css

tabs.css

129 ms

textarea.css

textarea.css

128 ms

ui-dialog.css

ui-dialog.css

125 ms

messages.css

messages.css

143 ms

bootstrap.css

bootstrap.css

127 ms

print.css

print.css

123 ms

main.css

main.css

143 ms

infografic.css

infografic.css

137 ms

jquery.mCustomScrollbar.css

jquery.mCustomScrollbar.css

143 ms

sliding-popup.css

sliding-popup.css

131 ms

rocket-loader.min.js

rocket-loader.min.js

119 ms

logo.svg

logo.svg

225 ms

iPhone_Digital%20Wallet_Image_for_Web.jpg

iPhone_Digital%20Wallet_Image_for_Web.jpg

226 ms

savings_card_0.png

savings_card_0.png

225 ms

youtube.png

youtube.png

226 ms

otsuka-logo_0_1.png

otsuka-logo_0_1.png

220 ms

header-bg.png

header-bg.png

93 ms

sprite.png

sprite.png

92 ms

ITCFranklinGothicStd-Book.otf

ITCFranklinGothicStd-Book.otf

17 ms

ITCFranklinGothicStd-Demi.otf

ITCFranklinGothicStd-Demi.otf

55 ms

ITCFranklinGothicStd-BkCd.otf

ITCFranklinGothicStd-BkCd.otf

20 ms

helvetica_neu_bold-webfont.ttf

helvetica_neu_bold-webfont.ttf

54 ms

ITCFranklinGothicStd-DmCpIt.otf

ITCFranklinGothicStd-DmCpIt.otf

54 ms

ITCFranklinGothicStd-Med.otf

ITCFranklinGothicStd-Med.otf

54 ms

helveticaneue_medium-webfont.ttf

helveticaneue_medium-webfont.ttf

54 ms

launch-eafb88252158.min.js

launch-eafb88252158.min.js

37 ms

gtm.js

gtm.js

79 ms

adobe_launch_dtm_init.js

adobe_launch_dtm_init.js

31 ms

jquery.min.js

jquery.min.js

35 ms

id

id

47 ms

AppMeasurement.min.js

AppMeasurement.min.js

16 ms

AppMeasurement_Module_ActivityMap.min.js

AppMeasurement_Module_ActivityMap.min.js

44 ms

jquery-ui-1.12.1.js

jquery-ui-1.12.1.js

73 ms

dest5.html

dest5.html

65 ms

analytics.js

analytics.js

47 ms

tag.js

tag.js

26 ms

ibs:dpid=411&dpuuid=ZjkVYQAAAHeIeQMv

ibs:dpid=411&dpuuid=ZjkVYQAAAHeIeQMv

28 ms

bootstrap.js

bootstrap.js

29 ms

linkid.js

linkid.js

7 ms

Accessibility Review

abilify.com accessibility score

94

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

Best Practices

abilify.com best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

abilify.com SEO score

93

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

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 Abilify.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 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.

Social Sharing Optimization

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: