1b.app Site Title
Українські CRM системи для бізнесу на базі OneBox OS
1b.app Meta Description
Рішення з готовим набором функцій на базі OneBox OS ✅ Українська CRM ✅ Інтеграція з популярними сервісами ✅ Безкоштовний тариф ✅ 100% безпека
1b.app Test Results
1b.app Mobile Performance: 48/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
5.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
Reduce the impact of third-party code
Third-party code blocked the main thread for 710 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 multiple page redirects
Potential savings of 1,080 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Avoid an excessive DOM size
1,503 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.
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.
Reduce unused JavaScript
Potential savings of 201 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.
Eliminate render-blocking resources
Potential savings of 300 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.
Largest Contentful Paint element
6,280 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid serving legacy JavaScript to modern browsers
Potential savings of 7 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
49 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 2,875 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Efficiently encode images
Potential savings of 721 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Reduce unused CSS
Potential savings of 84 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.
Minify JavaScript
Potential savings of 3 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify 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
Serve images in next-gen formats
Potential savings of 2,213 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.
Avoid enormous network payloads
Total size was 4,210 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
10.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
320 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.
1b.app 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
1b.app Mobile Best Practices: 79/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.
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
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.
1b.app Mobile Accessibility: 86/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.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
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.1b.com
www.1b.net
www.1b.org
www.1b.info
www.1b.biz
www.1b.us
www.1b.mobi
www.b.app
www.1b.app
www.1.app
www.1v.app
www.1bv.app
www.1vb.app
www.1g.app
www.1bg.app
www.1gb.app
www.1h.app
www.1bh.app
www.1hb.app
www.1n.app
www.1bn.app
www.1nb.app
www.1b.net
www.1b.org
www.1b.info
www.1b.biz
www.1b.us
www.1b.mobi
www.b.app
www.1b.app
www.1.app
www.1v.app
www.1bv.app
www.1vb.app
www.1g.app
www.1bg.app
www.1gb.app
www.1h.app
www.1bh.app
www.1hb.app
www.1n.app
www.1bn.app
www.1nb.app