Comenza.com Site Title

Comenza | Barandillas de Vidrio y Acero Inoxidable

Comenza.com Meta Description

Comenza: la compañía global especializada en el desarrollo de sistemas de barandillas de cristal y barandillas modulares de acero inoxidable ¡Proyectos únicos!

Comenza.com Test Results

Comenza.com Mobile Performance: 29/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Largest Contentful Paint element
11,510 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,460 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
Minify JavaScript
Potential savings of 38 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
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.
Reduce initial server response time
Root document took 830 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.
Reduce JavaScript execution time
4.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.
Minify CSS
Potential savings of 21 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Reduce unused JavaScript
Potential savings of 616 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.
Reduce unused CSS
Potential savings of 227 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.
Properly size images
Potential savings of 144 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Largest Contentful Paint image was lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.
Minimize main-thread work
8.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 minimize main-thread work
Eliminate render-blocking resources
Potential savings of 3,840 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 393 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.
Avoid an excessive DOM size
1,163 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.
Efficiently encode images
Potential savings of 99 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
Avoid serving legacy JavaScript to modern browsers
Potential savings of 14 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
Serve static assets with an efficient cache policy
14 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,064 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`.
Defer offscreen images
Potential savings of 27 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.
Time to Interactive
17.4 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
570 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
6.0 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

Comenza.com Mobile SEO: 77/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
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
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.

Comenza.com Mobile Best Practices: 79/100
Quick overview:
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.
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.
Comenza.com Mobile Accessibility: 61/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-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
`[aria-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn how `aria-hidden` affects focusable elements.
Elements use prohibited ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
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.
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.
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.
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.
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.comenza.com
www.comenza.net
www.comenza.org
www.comenza.info
www.comenza.biz
www.comenza.us
www.comenza.mobi
www.omenza.com
www.comenza.com
www.xomenza.com
www.cxomenza.com
www.xcomenza.com
www.domenza.com
www.cdomenza.com
www.dcomenza.com
www.fomenza.com
www.cfomenza.com
www.fcomenza.com
www.vomenza.com
www.cvomenza.com
www.vcomenza.com
www.cmenza.com
www.cimenza.com
www.coimenza.com
www.ciomenza.com
www.ckmenza.com
www.cokmenza.com
www.ckomenza.com
www.clmenza.com
www.colmenza.com
www.clomenza.com
www.cpmenza.com
www.copmenza.com
www.cpomenza.com
www.coenza.com
www.conenza.com
www.comnenza.com
www.conmenza.com
www.cojenza.com
www.comjenza.com
www.cojmenza.com
www.cokenza.com
www.comkenza.com
www.comnza.com
www.comwnza.com
www.comewnza.com
www.comwenza.com
www.comsnza.com
www.comesnza.com
www.comsenza.com
www.comdnza.com
www.comednza.com
www.comdenza.com
www.comrnza.com
www.comernza.com
www.comrenza.com
www.comeza.com
www.comebza.com
www.comenbza.com
www.comebnza.com
www.comehza.com
www.comenhza.com
www.comehnza.com
www.comejza.com
www.comenjza.com
www.comejnza.com
www.comemza.com
www.comenmza.com
www.comemnza.com
www.comena.com
www.comenxa.com
www.comenzxa.com
www.comenxza.com
www.comensa.com
www.comenzsa.com
www.comensza.com
www.comenaa.com
www.comenzaa.com
www.comenaza.com
www.comenz.com
www.comenzq.com
www.comenzaq.com
www.comenzqa.com
www.comenzw.com
www.comenzaw.com
www.comenzwa.com
www.comenzs.com
www.comenzas.com
www.comenzz.com
www.comenzaz.com
www.comenzza.com
www.comenza.con
Last Tested: