91ajs.com Test Results

91ajs.com Mobile Performance: 33/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minimize main-thread work
9.4 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
Largest Contentful Paint element
5,870 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused JavaScript
Potential savings of 2,106 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 multiple page redirects
Potential savings of 1,890 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Serve images in next-gen formats
Potential savings of 167 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.
Reduce JavaScript execution time
5.1 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.
Reduce initial server response time
Root document took 640 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 2,940 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.
Avoid an excessive DOM size
1,162 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.
Eliminate render-blocking resources
Potential savings of 70 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.
Serve static assets with an efficient cache policy
83 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Properly size images
Potential savings of 5 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Use video formats for animated content
Potential savings of 208 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 enormous network payloads
Total size was 4,883 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Defer offscreen images
Potential savings of 2 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.
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.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 106 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
Enable text compression
Potential savings of 1,485 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 133 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
29.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.
Max Potential First Input Delay
1,520 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.

91ajs.com Mobile SEO: 91/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.

91ajs.com Mobile Best Practices: 59/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.
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
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
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.
91ajs.com Mobile Accessibility: 73/100
Quick overview:
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.
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.
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
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.91ajs.com
www.91ajs.net
www.91ajs.org
www.91ajs.info
www.91ajs.biz
www.91ajs.us
www.91ajs.mobi
www.1ajs.com
www.91ajs.com
www.9ajs.com
www.91js.com
www.91qjs.com
www.91aqjs.com
www.91qajs.com
www.91wjs.com
www.91awjs.com
www.91wajs.com
www.91sjs.com
www.91asjs.com
www.91sajs.com
www.91zjs.com
www.91azjs.com
www.91zajs.com
www.91as.com
www.91ans.com
www.91ajns.com
www.91anjs.com
www.91ahs.com
www.91ajhs.com
www.91ahjs.com
www.91aus.com
www.91ajus.com
www.91aujs.com
www.91ais.com
www.91ajis.com
www.91aijs.com
www.91aks.com
www.91ajks.com
www.91akjs.com
www.91ams.com
www.91ajms.com
www.91amjs.com
www.91aj.com
www.91ajw.com
www.91ajsw.com
www.91ajws.com
www.91aje.com
www.91ajse.com
www.91ajes.com
www.91ajd.com
www.91ajsd.com
www.91ajds.com
www.91ajz.com
www.91ajsz.com
www.91ajzs.com
www.91ajx.com
www.91ajsx.com
www.91ajxs.com
www.91aja.com
www.91ajsa.com
www.91ajas.com
www.91ajs.con
Last Tested: