Abilify.shop Test Results

Abilify.shop Mobile Performance: 5/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid an excessive DOM size
6,142 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Reduce unused JavaScript
Potential savings of 787 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Minimize main-thread work
26.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Avoid large layout shifts
7 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Largest Contentful Paint element
17,700 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce JavaScript execution time
16.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Avoid multiple page redirects
Potential savings of 2,500 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Defer offscreen images
Potential savings of 89 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Reduce unused CSS
Potential savings of 37 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Eliminate render-blocking resources
Potential savings of 0 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 19 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Properly size images
Potential savings of 746 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Serve images in next-gen formats
Potential savings of 1,384 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Avoid enormous network payloads
Total size was 4,131 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Serve static assets with an efficient cache policy
62 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Max Potential First Input Delay
1,420 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Time to Interactive
23.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
First Meaningful Paint
7.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

Abilify.shop Mobile SEO: 77/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Abilify.shop Mobile Best Practices: 59/100
Quick overview:
Trust and Safety
Does not use HTTPS
2 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
General
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Uses deprecated APIs
2 warnings found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
User Experience
Document doesn't use legible font sizes
59.85% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes.
Abilify.shop Mobile Accessibility: 63/100
Quick overview:
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.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
ARIA input fields do not have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Definition list items are not wrapped in `<dl>` elements
Definition list items (`<dt>` and `<dd>`) must be wrapped in a parent `<dl>` element to ensure that screen readers can properly announce them. Learn how to structure definition lists correctly.
`<dl>`'s do not contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Similar tests
www.abilify.com
www.abilify.net
www.abilify.org
www.abilify.info
www.abilify.biz
www.abilify.us
www.abilify.mobi
www.bilify.shop
www.abilify.shop
www.qbilify.shop
www.aqbilify.shop
www.qabilify.shop
www.wbilify.shop
www.awbilify.shop
www.wabilify.shop
www.sbilify.shop
www.asbilify.shop
www.sabilify.shop
www.zbilify.shop
www.azbilify.shop
www.zabilify.shop
www.ailify.shop
www.avilify.shop
www.abvilify.shop
www.avbilify.shop
www.agilify.shop
www.abgilify.shop
www.agbilify.shop
www.ahilify.shop
www.abhilify.shop
www.ahbilify.shop
www.anilify.shop
www.abnilify.shop
www.anbilify.shop
www.ablify.shop
www.abulify.shop
www.abiulify.shop
www.abuilify.shop
www.abjlify.shop
www.abijlify.shop
www.abjilify.shop
www.abklify.shop
www.abiklify.shop
www.abkilify.shop
www.abolify.shop
www.abiolify.shop
www.aboilify.shop
www.abiify.shop
www.abipify.shop
www.abilpify.shop
www.abiplify.shop
www.abioify.shop
www.abiloify.shop
www.abikify.shop
www.abilkify.shop
www.abilfy.shop
www.abilufy.shop
www.abiliufy.shop
www.abiluify.shop
www.abiljfy.shop
www.abilijfy.shop
www.abiljify.shop
www.abilkfy.shop
www.abilikfy.shop
www.abilofy.shop
www.abiliofy.shop
www.abiliy.shop
www.abilicy.shop
www.abilifcy.shop
www.abilicfy.shop
www.abilidy.shop
www.abilifdy.shop
www.abilidfy.shop
www.abiliry.shop
www.abilifry.shop
www.abilirfy.shop
www.ability.shop
www.abilifty.shop
www.abilitfy.shop
www.abiligy.shop
www.abilifgy.shop
www.abiligfy.shop
www.abilivy.shop
www.abilifvy.shop
www.abilivfy.shop
www.abilif.shop
www.abilift.shop
www.abilifyt.shop
www.abilifg.shop
www.abilifyg.shop
www.abilifh.shop
www.abilifyh.shop
www.abilifhy.shop
www.abilifu.shop
www.abilifyu.shop
www.abilifuy.shop
Last Tested: