Armex.su Site Title
АРМЭКС - управление недвижимостью, эксплуатация зданий и консалтинг по эксплуатации недвижимости
Armex.su Test Results
Armex.su Mobile Performance: 60/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused JavaScript
Potential savings of 56 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.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Minimize main-thread work
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 minimize main-thread work
Largest Contentful Paint element
11,150 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
Potential savings of 578 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 the impact of third-party code
Third-party code blocked the main thread for 350 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.
Reduce JavaScript execution time
1.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.
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.
Eliminate render-blocking resources
Potential savings of 1,740 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.
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`.
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.
Minify JavaScript
Potential savings of 3 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 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 static assets with an efficient cache policy
5 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 7,170 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Minify CSS
Potential savings of 3 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Efficiently encode images
Potential savings of 16 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
First Meaningful Paint
4.7 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
5.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
190 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.
Armex.su Mobile SEO: 82/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.
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Armex.su Mobile Best Practices: 48/100
Quick overview:
User Experience
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more about legible font sizes. Text is illegible because there's no viewport meta tag optimized for mobile screens.
General
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
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Trust and Safety
Does not use HTTPS
2 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.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document must contain a doctype
Armex.su Mobile Accessibility: 80/100
Quick overview:
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.
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.
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.
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.
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.armex.com
www.armex.net
www.armex.org
www.armex.info
www.armex.biz
www.armex.us
www.armex.mobi
www.rmex.su
www.armex.su
www.qrmex.su
www.aqrmex.su
www.qarmex.su
www.wrmex.su
www.awrmex.su
www.warmex.su
www.srmex.su
www.asrmex.su
www.sarmex.su
www.zrmex.su
www.azrmex.su
www.zarmex.su
www.amex.su
www.aemex.su
www.aremex.su
www.aermex.su
www.admex.su
www.ardmex.su
www.adrmex.su
www.afmex.su
www.arfmex.su
www.afrmex.su
www.atmex.su
www.artmex.su
www.atrmex.su
www.arex.su
www.arnex.su
www.armnex.su
www.arnmex.su
www.arjex.su
www.armjex.su
www.arjmex.su
www.arkex.su
www.armkex.su
www.arkmex.su
www.armx.su
www.armwx.su
www.armewx.su
www.armwex.su
www.armsx.su
www.armesx.su
www.armdx.su
www.armedx.su
www.armdex.su
www.armrx.su
www.armerx.su
www.armrex.su
www.arme.su
www.armez.su
www.armexz.su
www.armezx.su
www.armes.su
www.armexs.su
www.armed.su
www.armexd.su
www.armec.su
www.armexc.su
www.armecx.su
www.armex.net
www.armex.org
www.armex.info
www.armex.biz
www.armex.us
www.armex.mobi
www.rmex.su
www.armex.su
www.qrmex.su
www.aqrmex.su
www.qarmex.su
www.wrmex.su
www.awrmex.su
www.warmex.su
www.srmex.su
www.asrmex.su
www.sarmex.su
www.zrmex.su
www.azrmex.su
www.zarmex.su
www.amex.su
www.aemex.su
www.aremex.su
www.aermex.su
www.admex.su
www.ardmex.su
www.adrmex.su
www.afmex.su
www.arfmex.su
www.afrmex.su
www.atmex.su
www.artmex.su
www.atrmex.su
www.arex.su
www.arnex.su
www.armnex.su
www.arnmex.su
www.arjex.su
www.armjex.su
www.arjmex.su
www.arkex.su
www.armkex.su
www.arkmex.su
www.armx.su
www.armwx.su
www.armewx.su
www.armwex.su
www.armsx.su
www.armesx.su
www.armdx.su
www.armedx.su
www.armdex.su
www.armrx.su
www.armerx.su
www.armrex.su
www.arme.su
www.armez.su
www.armexz.su
www.armezx.su
www.armes.su
www.armexs.su
www.armed.su
www.armexd.su
www.armec.su
www.armexc.su
www.armecx.su