Azeah.com Site Title

Arizona Exotic Animal Hospital | Veterinary care for exotic pets in Phoenix, Mesa, Tempe, Chandler, Gilbert AZ

Azeah.com Test Results

Azeah.com Mobile Performance: 48/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Enable text compression
Potential savings of 43 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Defer offscreen images
Potential savings of 736 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 JavaScript
Potential savings of 426 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.
Eliminate render-blocking resources
Potential savings of 2,050 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.
Minimize main-thread work
6.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
Reduce initial server response time
Root document took 680 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Reduce the impact of third-party code
Third-party code blocked the main thread for 890 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
Largest Contentful Paint element
5,840 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid an excessive DOM size
944 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 JavaScript execution time
3.7 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.
Serve images in next-gen formats
Potential savings of 670 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.
Minify JavaScript
Potential savings of 13 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
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`.
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
Properly size images
Potential savings of 569 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more about adopting passive event listeners.
Serve static assets with an efficient cache policy
47 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Reduce unused CSS
Potential savings of 24 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.
Time to Interactive
12.9 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
4.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Max Potential First Input Delay
250 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.

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

Azeah.com Mobile Best Practices: 72/100
Quick overview:
Trust and Safety
Does not use HTTPS
47 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.
Does not redirect HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
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.
Azeah.com Mobile Accessibility: 68/100
Quick overview:
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.
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.
Select elements do not have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
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.
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.
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.
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.
Similar sites
Similar tests
www.azeah.com
www.azeah.net
www.azeah.org
www.azeah.info
www.azeah.biz
www.azeah.us
www.azeah.mobi
www.zeah.com
www.azeah.com
www.qzeah.com
www.aqzeah.com
www.qazeah.com
www.wzeah.com
www.awzeah.com
www.wazeah.com
www.szeah.com
www.aszeah.com
www.sazeah.com
www.zzeah.com
www.azzeah.com
www.zazeah.com
www.aeah.com
www.axeah.com
www.azxeah.com
www.axzeah.com
www.aseah.com
www.azseah.com
www.aaeah.com
www.azaeah.com
www.aazeah.com
www.azah.com
www.azwah.com
www.azewah.com
www.azweah.com
www.azsah.com
www.azesah.com
www.azdah.com
www.azedah.com
www.azdeah.com
www.azrah.com
www.azerah.com
www.azreah.com
www.azeh.com
www.azeqh.com
www.azeaqh.com
www.azeqah.com
www.azewh.com
www.azeawh.com
www.azesh.com
www.azeash.com
www.azezh.com
www.azeazh.com
www.azezah.com
www.azea.com
www.azeab.com
www.azeahb.com
www.azeabh.com
www.azeag.com
www.azeahg.com
www.azeagh.com
www.azeay.com
www.azeahy.com
www.azeayh.com
www.azeau.com
www.azeahu.com
www.azeauh.com
www.azeaj.com
www.azeahj.com
www.azeajh.com
www.azean.com
www.azeahn.com
www.azeanh.com
www.azeah.con
Last Tested: