Ruall.com Site Title

RuAll.com | Бизнес портал

Ruall.com Meta Description

RuAll.com - Бизнес портал

Ruall.com Test Results

Ruall.com Mobile Performance: 74/100
Quick overview:
Time to Interactive
9.6 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Largest Contentful Paint element
9,590 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Efficiently encode images
Potential savings of 219 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Eliminate render-blocking resources
Potential savings of 820 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.
Serve images in next-gen formats
Potential savings of 985 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.
Properly size images
Potential savings of 248 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Reduce initial server response time
Root document took 1,090 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
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
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Serve static assets with an efficient cache policy
60 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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`.
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

Ruall.com Mobile SEO: 100/100
Quick overview:

Ruall.com Mobile Best Practices: 59/100
Quick overview:
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.
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.
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
Trust and Safety
Does not use HTTPS
70 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`
Ruall.com Mobile Accessibility: 71/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.
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.
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.
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.
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 sites
Similar tests
www.ruall.com
www.ruall.net
www.ruall.org
www.ruall.info
www.ruall.biz
www.ruall.us
www.ruall.mobi
www.uall.com
www.ruall.com
www.euall.com
www.reuall.com
www.eruall.com
www.duall.com
www.rduall.com
www.druall.com
www.fuall.com
www.rfuall.com
www.fruall.com
www.tuall.com
www.rtuall.com
www.truall.com
www.rall.com
www.ryall.com
www.ruyall.com
www.ryuall.com
www.rhall.com
www.ruhall.com
www.rhuall.com
www.rjall.com
www.rujall.com
www.rjuall.com
www.riall.com
www.ruiall.com
www.riuall.com
www.rull.com
www.ruqll.com
www.ruaqll.com
www.ruqall.com
www.ruwll.com
www.ruawll.com
www.ruwall.com
www.rusll.com
www.ruasll.com
www.rusall.com
www.ruzll.com
www.ruazll.com
www.ruzall.com
www.rual.com
www.ruapl.com
www.rualpl.com
www.ruapll.com
www.ruaol.com
www.rualol.com
www.ruaoll.com
www.ruakl.com
www.rualkl.com
www.ruakll.com
www.rualp.com
www.ruallp.com
www.rualo.com
www.ruallo.com
www.rualk.com
www.ruallk.com
www.ruall.con
Last Tested: