Rubau.com Site Title

Rubau | Construccions RUBAU

Rubau.com Test Results

Rubau.com Mobile Performance: 56/100
Quick overview:
Network dependency tree
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Render blocking requests
Est savings of 4,740 ms
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Improve image delivery
Est savings of 971 KiB
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Use efficient cache lifetimes
Est savings of 2,851 KiB
A long cache lifetime can speed up repeat visits to your page. Learn more.
Forced reflow
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Font display
Est savings of 170 ms
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Document request latency
Est savings of 3,400 ms
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Time to Interactive
17.5 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.
Serve images in next-gen formats
Est savings of 1,193 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 CSS
Est savings of 15 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.
Enable text compression
Est savings of 112 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more about text compression.
Avoid multiple page redirects
Est savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Defer offscreen images
Est savings of 408 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.
Reduce unused JavaScript
Est savings of 418 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
Est savings of 4,480 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.
Minify JavaScript
Est savings of 93 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Properly size images
Est savings of 259 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Largest Contentful Paint element
17,280 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce initial server response time
Root document took 2,160 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.
Efficiently encode images
Est savings of 118 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
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
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
72 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid enormous network payloads
Total size was 3,278 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
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`.

Rubau.com Mobile SEO: 83/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.

Rubau.com Mobile Best Practices: 69/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 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.
Does not use HTTPS
63 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.
User Experience
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.
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Rubau.com Mobile Accessibility: 74/100
Quick overview:
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.
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.
Input buttons do not have discernible text.
Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.
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.
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.
`[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.
Similar sites
Similar tests
www.rubau.com
www.rubau.net
www.rubau.org
www.rubau.info
www.rubau.biz
www.rubau.us
www.rubau.mobi
www.ubau.com
www.rubau.com
www.eubau.com
www.reubau.com
www.erubau.com
www.dubau.com
www.rdubau.com
www.drubau.com
www.fubau.com
www.rfubau.com
www.frubau.com
www.tubau.com
www.rtubau.com
www.trubau.com
www.rbau.com
www.rybau.com
www.ruybau.com
www.ryubau.com
www.rhbau.com
www.ruhbau.com
www.rhubau.com
www.rjbau.com
www.rujbau.com
www.rjubau.com
www.ribau.com
www.ruibau.com
www.riubau.com
www.ruau.com
www.ruvau.com
www.rubvau.com
www.ruvbau.com
www.rugau.com
www.rubgau.com
www.rugbau.com
www.ruhau.com
www.rubhau.com
www.runau.com
www.rubnau.com
www.runbau.com
www.rubu.com
www.rubqu.com
www.rubaqu.com
www.rubqau.com
www.rubwu.com
www.rubawu.com
www.rubwau.com
www.rubsu.com
www.rubasu.com
www.rubsau.com
www.rubzu.com
www.rubazu.com
www.rubzau.com
www.ruba.com
www.rubay.com
www.rubauy.com
www.rubayu.com
www.rubah.com
www.rubauh.com
www.rubahu.com
www.rubaj.com
www.rubauj.com
www.rubaju.com
www.rubai.com
www.rubaui.com
www.rubaiu.com
www.rubau.con
Last Tested: