Ave.ai Site Title
Ave.ai
Ave.ai Test Results
Ave.ai Mobile Performance: 27/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused JavaScript
Potential savings of 2,170 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.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 28 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
Eliminate render-blocking resources
Potential savings of 150 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.
Largest Contentful Paint element
23,630 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused CSS
Potential savings of 53 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.
Minimize main-thread work
7.8 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
Reduce JavaScript execution time
5.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 reduce Javascript execution time.
Avoid multiple page redirects
Potential savings of 1,090 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Avoid an excessive DOM size
1,796 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.
Avoid enormous network payloads
Total size was 4,072 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Ensure text remains visible during webfont load
Leverage the `font-display` CSS feature to ensure text is user-visible while webfonts are loading. Learn more about `font-display`.
Properly size images
Potential savings of 143 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Serve static assets with an efficient cache policy
29 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Serve images in next-gen formats
Potential savings of 91 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.
Defer offscreen images
Potential savings of 12 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.
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
Time to Interactive
24.2 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.
Max Potential First Input Delay
900 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.
Ave.ai Mobile SEO: 83/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
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.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Ave.ai Mobile Best Practices: 72/100
Quick overview:
General
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.
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
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Trust and Safety
Does not use HTTPS
1 insecure request 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.
Ave.ai Mobile Accessibility: 74/100
Quick overview:
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.
Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
`button`, `link`, and `menuitem` elements do not have accessible names.
When an element 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 how to make command elements more accessible.
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.
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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Best practices
These items highlight common accessibility best practices.
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.
`[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.
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 sites
Similar tests
www.ave.com
www.ave.net
www.ave.org
www.ave.info
www.ave.biz
www.ave.us
www.ave.mobi
www.ve.ai
www.ave.ai
www.qve.ai
www.aqve.ai
www.qave.ai
www.wve.ai
www.awve.ai
www.wave.ai
www.sve.ai
www.asve.ai
www.save.ai
www.zve.ai
www.azve.ai
www.zave.ai
www.ae.ai
www.ace.ai
www.avce.ai
www.acve.ai
www.afe.ai
www.avfe.ai
www.afve.ai
www.age.ai
www.avge.ai
www.agve.ai
www.abe.ai
www.avbe.ai
www.abve.ai
www.av.ai
www.avw.ai
www.avew.ai
www.avwe.ai
www.avs.ai
www.aves.ai
www.avse.ai
www.avd.ai
www.aved.ai
www.avde.ai
www.avr.ai
www.aver.ai
www.avre.ai
www.ave.net
www.ave.org
www.ave.info
www.ave.biz
www.ave.us
www.ave.mobi
www.ve.ai
www.ave.ai
www.qve.ai
www.aqve.ai
www.qave.ai
www.wve.ai
www.awve.ai
www.wave.ai
www.sve.ai
www.asve.ai
www.save.ai
www.zve.ai
www.azve.ai
www.zave.ai
www.ae.ai
www.ace.ai
www.avce.ai
www.acve.ai
www.afe.ai
www.avfe.ai
www.afve.ai
www.age.ai
www.avge.ai
www.agve.ai
www.abe.ai
www.avbe.ai
www.abve.ai
www.av.ai
www.avw.ai
www.avew.ai
www.avwe.ai
www.avs.ai
www.aves.ai
www.avse.ai
www.avd.ai
www.aved.ai
www.avde.ai
www.avr.ai
www.aver.ai
www.avre.ai