Na-markete.ru Site Title

На Маркете.ру — автоматически сканирует и находит лучшие цены

Na-markete.ru Meta Description

Система автоматического сканирования и поиска лучших цен на Яндекс Маркете, Алиэкспресс, Авито, Озон, Горбушке, Беру, Плеере, Савеловском и Официальных сайтах

Na-markete.ru Test Results

Na-markete.ru Mobile Performance: 59/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Properly size images
Est savings of 446 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Eliminate render-blocking resources
Est savings of 1,690 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.
Reduce unused CSS
Est savings of 27 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.
Largest Contentful Paint element
13,330 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Serve images in next-gen formats
Est savings of 576 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.
Efficiently encode images
Est savings of 358 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Avoid multiple page redirects
Est savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Minify JavaScript
Est savings of 9 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Reduce unused JavaScript
Est savings of 445 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.
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
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.
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().
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
49 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid serving legacy JavaScript to modern browsers
Est savings of 13 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support legacy browsers. Learn why most sites can deploy ES6+ code without transpiling
Defer offscreen images
Est savings of 332 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.
Render blocking requests
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Use efficient cache lifetimes
Est savings of 940 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Improve image delivery
Est savings of 724 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Forced reflow
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about forced reflow and its mitigations.
Font display
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Document request latency
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Time to Interactive
13.5 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.

Na-markete.ru Mobile SEO: 83/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
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.

Na-markete.ru Mobile Best Practices: 83/100
Quick overview:
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.
Na-markete.ru Mobile Accessibility: 65/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.
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.
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 input fields do not have accessible names
When an input field 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 more about input field labels.
ARIA toggle fields do not have accessible names
When a toggle field 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 more about toggle fields.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
`[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.
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.
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 tests
www.na-markete.com
www.na-markete.net
www.na-markete.org
www.na-markete.info
www.na-markete.biz
www.na-markete.us
www.na-markete.mobi
www.a-markete.ru
www.na-markete.ru
www.ba-markete.ru
www.nba-markete.ru
www.bna-markete.ru
www.ha-markete.ru
www.nha-markete.ru
www.hna-markete.ru
www.ja-markete.ru
www.nja-markete.ru
www.jna-markete.ru
www.ma-markete.ru
www.nma-markete.ru
www.mna-markete.ru
www.n-markete.ru
www.nq-markete.ru
www.naq-markete.ru
www.nqa-markete.ru
www.nw-markete.ru
www.naw-markete.ru
www.nwa-markete.ru
www.ns-markete.ru
www.nas-markete.ru
www.nsa-markete.ru
www.nz-markete.ru
www.naz-markete.ru
www.nza-markete.ru
www.namarkete.ru
www.na-arkete.ru
www.na-narkete.ru
www.na-mnarkete.ru
www.na-nmarkete.ru
www.na-jarkete.ru
www.na-mjarkete.ru
www.na-jmarkete.ru
www.na-karkete.ru
www.na-mkarkete.ru
www.na-kmarkete.ru
www.na-mrkete.ru
www.na-mqrkete.ru
www.na-maqrkete.ru
www.na-mqarkete.ru
www.na-mwrkete.ru
www.na-mawrkete.ru
www.na-mwarkete.ru
www.na-msrkete.ru
www.na-masrkete.ru
www.na-msarkete.ru
www.na-mzrkete.ru
www.na-mazrkete.ru
www.na-mzarkete.ru
www.na-makete.ru
www.na-maekete.ru
www.na-marekete.ru
www.na-maerkete.ru
www.na-madkete.ru
www.na-mardkete.ru
www.na-madrkete.ru
www.na-mafkete.ru
www.na-marfkete.ru
www.na-mafrkete.ru
www.na-matkete.ru
www.na-martkete.ru
www.na-matrkete.ru
www.na-marete.ru
www.na-marjete.ru
www.na-markjete.ru
www.na-marjkete.ru
www.na-mariete.ru
www.na-markiete.ru
www.na-marikete.ru
www.na-marmete.ru
www.na-markmete.ru
www.na-marmkete.ru
www.na-marlete.ru
www.na-marklete.ru
www.na-marlkete.ru
www.na-maroete.ru
www.na-markoete.ru
www.na-marokete.ru
www.na-markte.ru
www.na-markwte.ru
www.na-markewte.ru
www.na-markwete.ru
www.na-markste.ru
www.na-markeste.ru
www.na-marksete.ru
www.na-markdte.ru
www.na-markedte.ru
www.na-markdete.ru
www.na-markrte.ru
www.na-markerte.ru
www.na-markrete.ru
www.na-markee.ru
www.na-markere.ru
www.na-marketre.ru
www.na-markefe.ru
www.na-marketfe.ru
www.na-markefte.ru
www.na-markege.ru
www.na-marketge.ru
www.na-markegte.ru
www.na-markeye.ru
www.na-marketye.ru
www.na-markeyte.ru
www.na-market.ru
www.na-marketw.ru
www.na-marketew.ru
www.na-marketwe.ru
www.na-markets.ru
www.na-marketes.ru
www.na-marketse.ru
www.na-marketd.ru
www.na-marketed.ru
www.na-marketde.ru
www.na-marketr.ru
www.na-marketer.ru
Last Tested: