Mahr.com Test Results

Mahr.com Mobile Performance: 38/100
Quick overview:
Time to Interactive
13.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.
First Meaningful Paint
2.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid multiple page redirects
Potential savings of 1,590 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
9,040 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce JavaScript execution time
1.8 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 107 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.
Avoid large layout shifts
3 layout shifts 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
Properly size images
Potential savings of 73 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Defer offscreen images
Potential savings of 682 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.
Minimize main-thread work
3.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
Serve images in next-gen formats
Potential savings of 875 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.
Eliminate render-blocking resources
Potential savings of 0 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.
Serve static assets with an efficient cache policy
50 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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
Avoid enormous network payloads
Total size was 4,235 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
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
Avoid an excessive DOM size
821 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.
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`.

Mahr.com Mobile SEO: 77/100
Quick overview:
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.
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.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
689 errors found
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Mahr.com Mobile Best Practices: 79/100
Quick overview:
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
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.
Mahr.com Mobile Accessibility: 67/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.
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.
Image elements have `[alt]` attributes that are redundant text.
Informative elements should aim for short, descriptive alternative text. Alternative text that is exactly the same as the text adjacent to the link or image is potentially confusing for screen reader users, because the text will be read twice. Learn more about the `alt` attribute.
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.
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.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.
Similar sites
Similar tests
www.mahr.com
www.mahr.net
www.mahr.org
www.mahr.info
www.mahr.biz
www.mahr.us
www.mahr.mobi
www.ahr.com
www.mahr.com
www.nahr.com
www.mnahr.com
www.nmahr.com
www.jahr.com
www.mjahr.com
www.jmahr.com
www.kahr.com
www.mkahr.com
www.kmahr.com
www.mhr.com
www.mqhr.com
www.maqhr.com
www.mqahr.com
www.mwhr.com
www.mawhr.com
www.mwahr.com
www.mshr.com
www.mashr.com
www.msahr.com
www.mzhr.com
www.mazhr.com
www.mzahr.com
www.mar.com
www.mabr.com
www.mahbr.com
www.mabhr.com
www.magr.com
www.mahgr.com
www.maghr.com
www.mayr.com
www.mahyr.com
www.mayhr.com
www.maur.com
www.mahur.com
www.mauhr.com
www.majr.com
www.mahjr.com
www.majhr.com
www.manr.com
www.mahnr.com
www.manhr.com
www.mah.com
www.mahe.com
www.mahre.com
www.maher.com
www.mahd.com
www.mahrd.com
www.mahdr.com
www.mahf.com
www.mahrf.com
www.mahfr.com
www.maht.com
www.mahrt.com
www.mahtr.com
www.mahr.con
Last Tested: