As72.ru Site Title

АВТОСАН72

As72.ru Meta Description

АВТОСАН72 - Интернет-магазин запчастей для автобусов

As72.ru Test Results

As72.ru Mobile Performance: 50/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 40 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Reduce unused JavaScript
Potential savings of 867 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.
Enable text compression
Potential savings of 1,546 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Largest Contentful Paint element
16,510 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 713 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.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 27 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
Serve images in next-gen formats
Potential savings of 232 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 CSS
Potential savings of 41 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Eliminate render-blocking resources
Potential savings of 11,350 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.
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.
Defer offscreen images
Potential savings of 95 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
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`.
Serve static assets with an efficient cache policy
46 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 2,709 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Time to Interactive
16.8 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.

As72.ru Mobile SEO: 92/100
Quick overview:
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

As72.ru Mobile Best Practices: 55/100
Quick overview:
Trust and Safety
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.
Does not use HTTPS
54 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
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.
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.
As72.ru Mobile Accessibility: 67/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.
`[aria-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn how `aria-hidden` affects focusable elements.
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.
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.
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.
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.
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.
Similar sites
Similar tests
www.as72.com
www.as72.net
www.as72.org
www.as72.info
www.as72.biz
www.as72.us
www.as72.mobi
www.s72.ru
www.as72.ru
www.qs72.ru
www.aqs72.ru
www.qas72.ru
www.ws72.ru
www.aws72.ru
www.was72.ru
www.ss72.ru
www.ass72.ru
www.sas72.ru
www.zs72.ru
www.azs72.ru
www.zas72.ru
www.a72.ru
www.aw72.ru
www.asw72.ru
www.ae72.ru
www.ase72.ru
www.aes72.ru
www.ad72.ru
www.asd72.ru
www.ads72.ru
www.az72.ru
www.asz72.ru
www.ax72.ru
www.asx72.ru
www.axs72.ru
www.aa72.ru
www.asa72.ru
www.aas72.ru
www.as2.ru
www.as7.ru
Last Tested: