Ros138.com Test Results

Ros138.com Mobile Performance: 99/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
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
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
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.

Ros138.com Mobile SEO: 91/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

Ros138.com Mobile Best Practices: 66/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.
Trust and Safety
Does not use HTTPS
11 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.
Does not redirect HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
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
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 contains a `doctype` that triggers `limited-quirks-mode`
Ros138.com Mobile Accessibility: 72/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.
Select elements do not have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
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.
`<td>` elements in a large `<table>` do not have table headers.
Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.
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.
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.
Similar tests
www.ros138.com
www.ros138.net
www.ros138.org
www.ros138.info
www.ros138.biz
www.ros138.us
www.ros138.mobi
www.os138.com
www.ros138.com
www.eos138.com
www.reos138.com
www.eros138.com
www.dos138.com
www.rdos138.com
www.dros138.com
www.fos138.com
www.rfos138.com
www.fros138.com
www.tos138.com
www.rtos138.com
www.tros138.com
www.rs138.com
www.ris138.com
www.rois138.com
www.rios138.com
www.rks138.com
www.roks138.com
www.rkos138.com
www.rls138.com
www.rols138.com
www.rlos138.com
www.rps138.com
www.rops138.com
www.rpos138.com
www.ro138.com
www.row138.com
www.rosw138.com
www.rows138.com
www.roe138.com
www.rose138.com
www.roes138.com
www.rod138.com
www.rosd138.com
www.rods138.com
www.roz138.com
www.rosz138.com
www.rozs138.com
www.rox138.com
www.rosx138.com
www.roxs138.com
www.roa138.com
www.rosa138.com
www.roas138.com
www.ros38.com
www.ros18.com
www.ros13.com
www.ros138.con
Last Tested: