Bru.store Test Results
Bru.store Mobile Performance: 36/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused CSS
Potential savings of 75 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.
Reduce JavaScript execution time
1.6 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.
Minimize main-thread work
4.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
3,780 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid large layout shifts
1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Eliminate render-blocking resources
Potential savings of 1,490 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.
Avoid an excessive DOM size
1,736 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.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 22 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
Properly size images
Potential savings of 139 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
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.
Serve images in next-gen formats
Potential savings of 19 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 unused JavaScript
Potential savings of 426 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.
Defer offscreen images
Potential savings of 4 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.
Max Potential First Input Delay
1,040 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.
Time to Interactive
4.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.
Bru.store 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
Bru.store Mobile Best Practices: 72/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.
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
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
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.
Bru.store Mobile Accessibility: 82/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 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.
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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
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.
Links rely on color to be distinguishable.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
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 tests
www.bru.com
www.bru.net
www.bru.org
www.bru.info
www.bru.biz
www.bru.us
www.bru.mobi
www.ru.store
www.bru.store
www.vru.store
www.bvru.store
www.vbru.store
www.gru.store
www.bgru.store
www.gbru.store
www.hru.store
www.bhru.store
www.hbru.store
www.nru.store
www.bnru.store
www.nbru.store
www.bu.store
www.beu.store
www.breu.store
www.beru.store
www.bdu.store
www.brdu.store
www.bdru.store
www.bfu.store
www.brfu.store
www.bfru.store
www.btu.store
www.brtu.store
www.btru.store
www.br.store
www.bry.store
www.bruy.store
www.bryu.store
www.brh.store
www.bruh.store
www.brhu.store
www.brj.store
www.bruj.store
www.brju.store
www.bri.store
www.brui.store
www.briu.store
www.bru.net
www.bru.org
www.bru.info
www.bru.biz
www.bru.us
www.bru.mobi
www.ru.store
www.bru.store
www.vru.store
www.bvru.store
www.vbru.store
www.gru.store
www.bgru.store
www.gbru.store
www.hru.store
www.bhru.store
www.hbru.store
www.nru.store
www.bnru.store
www.nbru.store
www.bu.store
www.beu.store
www.breu.store
www.beru.store
www.bdu.store
www.brdu.store
www.bdru.store
www.bfu.store
www.brfu.store
www.bfru.store
www.btu.store
www.brtu.store
www.btru.store
www.br.store
www.bry.store
www.bruy.store
www.bryu.store
www.brh.store
www.bruh.store
www.brhu.store
www.brj.store
www.bruj.store
www.brju.store
www.bri.store
www.brui.store
www.briu.store