Skip to content
https://fernandolaserna.com/prueba6/index.html

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.

78

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:116.293 source:map[column:44 line:6 type:source-location url:https://fernandolaserna.com/prueba6/js/hero-canvas.js urlProvider:network]] map[reflowTime:0.28 source:map[column:45 line:7 type:source-location url:https://fernandolaserna.com/prueba6/js/hero-canvas.js urlProvider:network]]]

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:358.43 label:Time to first byte subpart:timeToFirstByte] map[duration:2192.776 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-A
nodeLabel: ORETANOS LAB
path: 1,HTML,1,BODY,1,NAV,0,A
selector: body > nav#navbar > a.nav-logo
snippet: <a href="#inicio" class="nav-logo" aria-label="Oretanos Lab Inicio">

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
fernandolaserna.com/prueba6/css/components/faq.css405 B
fernandolaserna.com/prueba6/css/components/cookie-consent.css1.2 KiB
fernandolaserna.com/prueba6/css/responsive.css494 B
fernandolaserna.com/prueba6/css/components/modal.css777 B
fernandolaserna.com/prueba6/css/components/proyectos.css635 B
fernandolaserna.com/prueba6/css/components/cta.css445 B150 ms
fernandolaserna.com/prueba6/css/components/proceso.css441 B
fernandolaserna.com/prueba6/css/components/farmacias.css1.0 KiB
fernandolaserna.com/prueba6/css/components/reveal.css238 B
fernandolaserna.com/prueba6/css/components/legal.css710 B
fernandolaserna.com/prueba6/css/components/footer.css514 B
fernandolaserna.com/prueba6/css/layout.css332 B
fernandolaserna.com/prueba6/css/components/pain-points.css483 B
fernandolaserna.com/prueba6/css/components/hero.css1022 B
fernandolaserna.com/prueba6/css/components/services.css510 B
fernandolaserna.com/prueba6/css/components/navbar.css844 B
fernandolaserna.com/prueba6/css/base.css291 B
fernandolaserna.com/prueba6/css/main.css215 B
fernandolaserna.com/prueba6/css/variables.css486 B
/css2?family=Inter:wght@300;400;500;600;700;800;900&famil...1.5 KiB782 ms
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css19.1 KiB929 ms

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
fernandolaserna.com/prueba6/js/cookie-consent.js604800.0 s2.1 KiB
fernandolaserna.com/prueba6/css/components/cookie-consent.css604800.0 s1.2 KiB
fernandolaserna.com/prueba6/css/components/farmacias.css604800.0 s1.0 KiB
fernandolaserna.com/prueba6/css/components/hero.css604800.0 s1022 B
fernandolaserna.com/prueba6/css/components/navbar.css604800.0 s844 B
fernandolaserna.com/prueba6/css/components/modal.css604800.0 s777 B
fernandolaserna.com/prueba6/css/components/legal.css604800.0 s710 B
fernandolaserna.com/prueba6/js/hero-canvas.js604800.0 s694 B
fernandolaserna.com/prueba6/css/components/proyectos.css604800.0 s635 B
fernandolaserna.com/prueba6/css/components/footer.css604800.0 s514 B
fernandolaserna.com/prueba6/css/components/services.css604800.0 s510 B
fernandolaserna.com/prueba6/css/responsive.css604800.0 s494 B
fernandolaserna.com/prueba6/js/main.js604800.0 s494 B
fernandolaserna.com/prueba6/css/variables.css604800.0 s486 B
fernandolaserna.com/prueba6/css/components/pain-points.css604800.0 s483 B
fernandolaserna.com/prueba6/css/components/cta.css604800.0 s445 B
fernandolaserna.com/prueba6/css/components/proceso.css604800.0 s441 B
fernandolaserna.com/prueba6/css/components/faq.css604800.0 s405 B
fernandolaserna.com/prueba6/js/form.js604800.0 s373 B
fernandolaserna.com/prueba6/css/layout.css604800.0 s332 B
fernandolaserna.com/prueba6/js/navbar.js604800.0 s315 B
fernandolaserna.com/prueba6/js/smooth-scroll.js604800.0 s301 B
fernandolaserna.com/prueba6/css/base.css604800.0 s291 B
fernandolaserna.com/prueba6/js/modal.js604800.0 s283 B
fernandolaserna.com/prueba6/js/reveal.js604800.0 s270 B
fernandolaserna.com/prueba6/css/components/reveal.css604800.0 s238 B
fernandolaserna.com/prueba6/js/faq.js604800.0 s234 B
fernandolaserna.com/prueba6/css/main.css604800.0 s215 B

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLEst Savings
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/webfonts/fa-solid-900.woff215 ms

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

Diagnostics

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 18.0 KiB
URLTransfer SizeEst Savings
cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css18.4 KiB18.0 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Other1.3 s
Style & Layout708 ms
Script Evaluation605 ms
Rendering141 ms
Parse HTML & CSS56 ms
Script Parsing & Compilation2.1 ms

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

●Time to Interactive 3.8 s
●Layout shift culprits
●Document request latency
●Optimize DOM size
●Improve image delivery
●Modern HTTP
●Optimize viewport for mobile
●Max Potential First Input Delay 20 ms
●Minify CSS
●Minify JavaScript
●Reduce unused JavaScript
●Avoids enormous network payloads Total size was 267 KiB
●JavaScript execution time 0.6 s
●Avoid long main-thread tasks 3 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 370 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 80 ms
○INP breakdown
○LCP request discovery
○User Timing marks and measures
○Avoid non-composited animations
○Avoid large layout shifts
90

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Auditoría gratuita nav#navbar > ul#navLinks > li > a.nav-cta
Solicitar auditoría gratuita section#inicio > div.hero-content > div.hero-buttons > a.btn
Laboratorio de software · Madrid · desde 2012 Páginas web que convierten. Softw… footer > div.footer-grid > div.footer-col > p.footer-contact-info
Problemas habituales div.footer-col > ul > li > a
Servicios div.footer-col > ul > li > a
Proyectos div.footer-col > ul > li > a
Proceso div.footer-col > ul > li > a
División Farmacias div.footer-col > ul > li > a
hola@oretanoslab.com div.footer-col > ul > li > a
Solicitar auditoría div.footer-col > ul > li > a
FAQ div.footer-col > ul > li > a
Aviso Legal div.footer-col > ul > li > a
Política de Privacidad div.footer-col > ul > li > a
Política de Cookies div.footer-col > ul > li > a
MADRID · BARCELONA · CIUDAD DE MÉXICO Confirmamos tu consulta en menos de 48 ho… footer > div.footer-grid > div.footer-col > p.footer-contact-info
© 2026 Oretanos Lab S.L. body > footer > div.footer-bottom > span
Aviso Legal body > footer > div.footer-bottom > a
Política de Privacidad body > footer > div.footer-bottom > a
Política de Cookies body > footer > div.footer-bottom > a
Gestionar cookies body > footer > div.footer-bottom > button
Aceptar todas aside#cookieBanner > div.cookie-banner__inner > div.cookie-banner__actions > button.btn

These are opportunities to improve the legibility of your content.

Navigation

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Descubrimiento div.container > div.process-timeline > div.process-step > h4
E-commerce farmacéutico div.container > div.farma-services-grid > div.farma-service-card > h4
ORETANOSLAB footer > div.footer-grid > div.footer-col > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.cookie-category > div.cookie-category__header > label.cookie-toggle > input#cookieAnalytics div.cookie-category > div.cookie-category__header > label.cookie-toggle > input#cookieAnalytics
div.cookie-category > div.cookie-category__header > label.cookie-toggle > input#cookieMarketing div.cookie-category > div.cookie-category__header > label.cookie-toggle > input#cookieMarketing

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.

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
ORETANOS LAB body > nav#navbar > a.nav-logo
○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●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
●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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
96

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
fernandolaserna.com/favicon.ico
Failed to load resource: the server responded with a status of 404 ()
●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 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 clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
92

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Send Feedback