Skip to content
https://cyan-lapwing-837262.hostingersite.com

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

90

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Performance issues directly impact user engagement and conversion rates.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/wp-content/uploads/2026/09/11-marcos-tovar.webp604800.0 s57.0 KiB
/wp-content/uploads/2026/09/08-manuel-pascual.webp604800.0 s49.0 KiB
/wp-content/uploads/2026/09/12-jose-gabriel-puche.webp604800.0 s48.6 KiB
/wp-content/uploads/2026/09/11-marcos-tovar-576x360.webp604800.0 s45.8 KiB
cyan-lapwing-837262.hostingersite.com/wp-content/uploads/2026/09/05-laura.webp604800.0 s44.4 KiB
/wp-content/uploads/2026/09/01-juan-carlos-bevia.webp604800.0 s40.6 KiB
/wp-content/uploads/2026/09/12-jose-gabriel-puche-576x360...604800.0 s38.8 KiB
/wp-content/uploads/2026/09/05-laura-576x360.webp604800.0 s37.1 KiB
/wp-content/uploads/2026/09/03-juan-f-munoz.webp604800.0 s35.3 KiB
/wp-content/uploads/2026/09/07-angel-guinales-del-valle.webp604800.0 s34.2 KiB
/wp-content/uploads/2026/09/08-manuel-pascual-576x360.webp604800.0 s34.0 KiB
/wp-content/uploads/2026/09/06-jacobo-garcis.webp604800.0 s32.1 KiB
/wp-content/uploads/2026/09/01-juan-carlos-bevia-576x360....604800.0 s30.1 KiB
/wp-content/uploads/2026/09/09-gonzalo-santalucia.webp604800.0 s28.2 KiB
/wp-content/uploads/2026/09/06-jacobo-garcis-576x360.webp604800.0 s27.3 KiB
/wp-content/uploads/2026/09/10-eddy-benalal.webp604800.0 s26.9 KiB
/wp-content/uploads/2026/09/03-juan-f-munoz-576x360.webp604800.0 s26.2 KiB
/wp-content/uploads/2026/09/07-angel-guinales-del-valle-5...604800.0 s25.7 KiB
/wp-content/uploads/2026/09/10-eddy-benalal-576x360.webp604800.0 s23.7 KiB
/wp-content/uploads/2026/09/09-gonzalo-santalucia-576x360...604800.0 s23.0 KiB
/wp-content/uploads/2026/09/04-juan-carlos-jimenez.webp604800.0 s20.2 KiB
cdn-reach.hostinger.com/js/embed.js3600.0 s2.5 KiB
/wp-content/uploads/2026/09/02-mariano-serrano-gonzalez.webp604800.0 s18.9 KiB
/wp-content/uploads/2026/09/04-juan-carlos-jimenez-576x36...604800.0 s16.5 KiB
/wp-content/uploads/2026/09/02-mariano-serrano-gonzalez-5...604800.0 s15.9 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
/wp-content/themes/tch/assets/media/hero-tch-custom-mobil...1.7 MiB
/wp-content/uploads/2026/09/11-marcos-tovar.webp57.0 KiB
/wp-content/uploads/2026/09/08-manuel-pascual.webp49.0 KiB
/wp-content/uploads/2026/09/12-jose-gabriel-puche.webp48.6 KiB
/wp-content/uploads/2026/09/11-marcos-tovar-576x360.webp45.8 KiB
cyan-lapwing-837262.hostingersite.com/wp-content/uploads/2026/09/05-laura.webp44.4 KiB
cyan-lapwing-837262.hostingersite.com/44.2 KiB
/wp-content/uploads/2026/09/01-juan-carlos-bevia.webp40.6 KiB
/wp-content/uploads/2026/09/12-jose-gabriel-puche-576x360...38.8 KiB
/wp-content/uploads/2026/09/05-laura-576x360.webp37.1 KiB

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Time to Interactive 3.4 s
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Forced reflow
●Improve image delivery
●LCP breakdown
●Modern HTTP
●Render blocking requests
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Reduce unused JavaScript
●JavaScript execution time 0.2 s
●Minimizes main-thread work 1.9 s
●Avoid long main-thread tasks 6 long tasks found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 10 ms
●Server Backend Latencies 90 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Initial server response time was short Root document took 10 ms
●Avoid large layout shifts 1 layout shift found
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
100

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
2 PLANTAS Modelo Montecarlo 300 m² 4 dormitorios 3 baños 1 aseo section#dos-formas > div.container > div.tch-grid > a.tch-card
2 PLANTAS Modelo Praga 290 m² 4 dormitorios 3 baños 1 aseo section#dos-formas > div.container > div.tch-grid > a.tch-card
2 PLANTAS Modelo Oslo 250 m² 4 dormitorios 3 baños 1 aseo section#dos-formas > div.container > div.tch-grid > a.tch-card
2 PLANTAS Modelo Roma 210 m² 4 dormitorios 3 baños section#dos-formas > div.container > div.tch-grid > a.tch-card
1 PLANTA Modelo Niza 200 m² 4 dormitorios 4 baños section#dos-formas > div.container > div.tch-grid > a.tch-card
2 PLANTAS Modelo Milán 180 m² 3 dormitorios 2 baños 1 aseo section#dos-formas > div.container > div.tch-grid > a.tch-card
1 PLANTA Modelo Cannes 160 m² 3 dormitorios 2 baños 1 aseo section#dos-formas > div.container > div.tch-grid > a.tch-card
2 PLANTAS Modelo Lisboa 150 m² 3 dormitorios 2 baños 1 aseo section#dos-formas > div.container > div.tch-grid > a.tch-card
1 PLANTA Modelo Barcelona 150 m² 3 dormitorios 2 baños 1 aseo section#dos-formas > div.container > div.tch-grid > a.tch-card
1 PLANTA Modelo Santorini 150 m² 3 dormitorios 2 baños section#dos-formas > div.container > div.tch-grid > a.tch-card
1 PLANTA Modelo Zermatt 150 m² 3 dormitorios 2 baños 1 aseo section#dos-formas > div.container > div.tch-grid > a.tch-card
1 PLANTA Modelo Formentera 150 m² 3 dormitorios 2 baños section#dos-formas > div.container > div.tch-grid > a.tch-card
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

●Uses HTTPS
●Avoids deprecated APIs
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No browser errors logged to the console
●No issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Use a strong HSTS policy
●Ensure proper origin isolation with COOP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
○Detected JavaScript libraries
69

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
head > meta

To appear in search results, crawlers need access to your app.

○Structured data is valid
●Document has a `<title>` element
●Document has a meta description
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
●Document has a valid `rel=canonical`

Send Feedback