Hxny.com Test Results
Hxny.com Mobile Performance: 35/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Efficiently encode images
Potential savings of 2,651 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Enable text compression
Potential savings of 878 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Reduce unused CSS
Potential savings of 33 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
6.2 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
Defer offscreen images
Potential savings of 3,403 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 244 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 large layout shifts
5 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
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
11,210 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce JavaScript execution time
2.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.
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.
Avoid an excessive DOM size
1,153 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.
Minify CSS
Potential savings of 8 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Properly size images
Potential savings of 4,460 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 6,694 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.
Serve static assets with an efficient cache policy
94 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid enormous network payloads
Total size was 10,193 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Use video formats for animated content
Potential savings of 56 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more about efficient video formats
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
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.
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
Time to Interactive
37.7 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
220 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.
First Meaningful Paint
3.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Hxny.com 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.
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
Hxny.com Mobile Best Practices: 62/100
Quick overview:
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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.
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Hxny.com Mobile Accessibility: 64/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.
Values assigned to `role=""` are not valid ARIA roles.
ARIA `role`s enable assistive technologies to know the role of each element on the web page. If the `role` values are misspelled, not existing ARIA `role` values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.
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.
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.
Contrast
These are opportunities to improve the legibility of your content.
Links rely on color to be distinguishable.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
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.
Image elements have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the `alt` attribute.
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.
Best practices
These items highlight common accessibility best practices.
The document uses `<meta http-equiv="refresh">`
Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.
`[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.
Similar sites
Similar tests
www.hxny.com
www.hxny.net
www.hxny.org
www.hxny.info
www.hxny.biz
www.hxny.us
www.hxny.mobi
www.xny.com
www.hxny.com
www.bxny.com
www.hbxny.com
www.bhxny.com
www.gxny.com
www.hgxny.com
www.ghxny.com
www.yxny.com
www.hyxny.com
www.yhxny.com
www.uxny.com
www.huxny.com
www.uhxny.com
www.jxny.com
www.hjxny.com
www.jhxny.com
www.nxny.com
www.hnxny.com
www.nhxny.com
www.hny.com
www.hzny.com
www.hxzny.com
www.hzxny.com
www.hsny.com
www.hxsny.com
www.hsxny.com
www.hdny.com
www.hxdny.com
www.hdxny.com
www.hcny.com
www.hxcny.com
www.hcxny.com
www.hxy.com
www.hxby.com
www.hxnby.com
www.hxbny.com
www.hxhy.com
www.hxnhy.com
www.hxhny.com
www.hxjy.com
www.hxnjy.com
www.hxjny.com
www.hxmy.com
www.hxnmy.com
www.hxmny.com
www.hxn.com
www.hxnt.com
www.hxnyt.com
www.hxnty.com
www.hxng.com
www.hxnyg.com
www.hxngy.com
www.hxnh.com
www.hxnyh.com
www.hxnu.com
www.hxnyu.com
www.hxnuy.com
www.hxny.con
www.hxny.net
www.hxny.org
www.hxny.info
www.hxny.biz
www.hxny.us
www.hxny.mobi
www.xny.com
www.hxny.com
www.bxny.com
www.hbxny.com
www.bhxny.com
www.gxny.com
www.hgxny.com
www.ghxny.com
www.yxny.com
www.hyxny.com
www.yhxny.com
www.uxny.com
www.huxny.com
www.uhxny.com
www.jxny.com
www.hjxny.com
www.jhxny.com
www.nxny.com
www.hnxny.com
www.nhxny.com
www.hny.com
www.hzny.com
www.hxzny.com
www.hzxny.com
www.hsny.com
www.hxsny.com
www.hsxny.com
www.hdny.com
www.hxdny.com
www.hdxny.com
www.hcny.com
www.hxcny.com
www.hcxny.com
www.hxy.com
www.hxby.com
www.hxnby.com
www.hxbny.com
www.hxhy.com
www.hxnhy.com
www.hxhny.com
www.hxjy.com
www.hxnjy.com
www.hxjny.com
www.hxmy.com
www.hxnmy.com
www.hxmny.com
www.hxn.com
www.hxnt.com
www.hxnyt.com
www.hxnty.com
www.hxng.com
www.hxnyg.com
www.hxngy.com
www.hxnh.com
www.hxnyh.com
www.hxnu.com
www.hxnyu.com
www.hxnuy.com
www.hxny.con