Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Detailed Report

Audit breakdown by category with detailed findings.

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 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.

Request	Cache TTL	Transfer Size
hammer3.com/assets/forest-walk-lAdL5yUV.webp	691200.0 s	233.3 KiB
hammer3.com/assets/vendor-zGAdSkjg.js	691200.0 s	99.6 KiB
hammer3.com/assets/bg2-1rb3pZSb.webp	691200.0 s	95.4 KiB
hammer3.com/assets/ai-600x400-f9o4FL7U.webp	691200.0 s	47.4 KiB
hammer3.com/assets/pbg6-768x512-jFvMl62X.webp	691200.0 s	40.6 KiB
hammer3.com/assets/router-ih45X-RH.js	691200.0 s	39.7 KiB
hammer3.com/assets/pbg2-768x512-x9vY-9dL.webp	691200.0 s	31.8 KiB
hammer3.com/assets/clown-gun-zoom-aoyKm8yX.webp	691200.0 s	17.5 KiB
hammer3.com/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js	172794.0 s	4.4 KiB
hammer3.com/assets/router-uCWn486s.css	691200.0 s	9.8 KiB
hammer3.com/assets/main-hyCcgF6E.js	691200.0 s	782 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:1.000125] map[node:map[boundingRect:map[bottom:8456 height:1244 left:0 right:412 top:7212 width:412] lhId:page-0-DIV nodeLabel:Our Address Hammer3 15746, Groß Köris Email: Use Contact Form Tel: +49 176 34… path:1,HTML,1,BODY,0,DIV,2,DIV,0,DIV selector:body > div#root > div#footer > div.h-full snippet:<div class="h-full bg-cover bg-center object-cover animate-bgBlur mix-blend-overlay bg…" loading="lazy"> type:node] score:1 subItems:map[items:[map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/montserrat/v31/JTUSjIg1_i6t8kCHKm459WlhyyTh89Y.woff2]] map[cause:Web font extra:map[type:url value:https://fonts.gstatic.com/s/hind/v18/5aU69_a8oxmIdGl4BDGwgDI.woff2]]] type:subitems]] map[node:map[boundingRect:map[bottom:54 height:44 left:236 right:340 top:10 width:104] lhId:page-6-DIV nodeLabel:Show mysteries path:1,HTML,1,BODY,0,DIV,0,DIV,2,DIV,1,DIV selector:div#root > div.flex > div#big-nav-buttons > div.items-end snippet:<div class="items-end space-x-4"> type:node] score:0.000125 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:3979 height:253 left:16 right:396 top:3726 width:380] lhId:page-11-IMG nodeLabel:div.grid > div.shadow > div.grid > img.lg:hover:scale-110 path:1,HTML,1,BODY,0,DIV,1,DIV,3,DIV,0,DIV,1,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,IMG selector:div.grid > div.shadow > div.grid > img.lg:hover:scale-110 snippet:<img class="lg:hover:scale-110 lg:hover:shadow-xl lg:shadow-md lg:shadow-black lg:hove…" decoding="async" src="https://hammer3.com/assets/pbg2-768x512-x9vY-9dL.webp" srcset=" https://hammer3.com/assets/pbg2-5TTB8qJ9.webp 900w, …" loading="eager"> type:node]]] type:subitems]]]

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Our Address Hammer3 15746, Groß Köris Email: Use Contact Form Tel: +49 176 34… `body > div#root > div#footer > div.h-full`	hammer3.com/assets/forest-walk-lAdL5yUV.webp	232.6 KiB	76.6 KiB

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

value: no origins were preconnected

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.

URL	Transfer Size	Duration
hammer3.com/assets/router-uCWn486s.css	9.8 KiB	176 ms
fonts.googleapis.com/css2?family=Montserrat:wght@400;500;600;700&display=swap	757 B	761 ms
cdn.jsdelivr.net/gh/lipis/flag-icons@7.0.0/css/flag-icons.min.css	2.4 KiB	761 ms
fonts.googleapis.com/css2?family=Hind:wght@300;400;500;600;700&display=swap	1.0 KiB	151 ms

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

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
Our Address Hammer3 15746, Groß Köris Email: Use Contact Form Tel: +49 176 34… `body > div#root > div#footer > div.h-full`	1.000
Show mysteries `div#root > div.flex > div#big-nav-buttons > div.items-end`	0.000

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 310 ms 42.0 KiB

URL	Transfer Size	Est Savings
hammer3.com/assets/vendor-zGAdSkjg.js	99.0 KiB	42.0 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 6.4 KiB

URL	Transfer Size	Est Savings
unpkg.com/flowbite@1.3.3/dist/flowbite.js	17.5 KiB	6.4 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
div.grid > div.shadow > div.grid > img.lg:hover:scale-110 `div.grid > div.shadow > div.grid > img.lg:hover:scale-110`	hammer3.com/assets/pbg2-768x512-x9vY-9dL.webp
div.grid > div.shadow > div.grid > img.lg:hover:scale-110 `div.grid > div.shadow > div.grid > img.lg:hover:scale-110`	hammer3.com/assets/pbg6-768x512-jFvMl62X.webp
div.grid > div.shadow > div.grid > img.lg:hover:scale-110 `div.grid > div.shadow > div.grid > img.lg:hover:scale-110`	hammer3.com/assets/ai-600x400-f9o4FL7U.webp

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

●Max Potential First Input Delay 130 ms

●Document request latency

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Reduce unused CSS

●Avoids enormous network payloads Total size was 696 KiB

●JavaScript execution time 0.6 s

●Minimizes main-thread work 2.0 s

●Avoid long main-thread tasks 7 long tasks found

●Avoid non-composited animations 8 animated elements found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 20 ms

●Server Backend Latencies 20 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 30 ms

○INP breakdown

○LCP request discovery

○User Timing marks and measures

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.

ARIA

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#root > div.flex > div.block > div.hamburger-react `div#root > div.flex > div.block > div.hamburger-react`

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.

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
180 / person `div.order-last > ul.flex > li.flex > span`
Whatever happened to Jane Templeton? The young maid disappeared without a trace… `div.grid > div.order-last > div.inline-flex > p.py-2`
Detective Inspector Duncan Hall has gathered all the suspects to dinner… and no… `div.grid > div.order-last > div.inline-flex > p.py-2`
Your hosts will guide you through a thrilling crime where each character will p… `div.grid > div.order-last > div.inline-flex > p.py-2`
180 / person `div.order-last > ul.flex > li.flex > span`
Lorem Ipsum è considerato il testo segnaposto standard sin dal sedicesimo secol… `div.grid > div.order-last > div.inline-flex > p.py-2`
Lorem Ipsum è considerato il testo segnaposto standard sin dal sedicesimo secol… `div.grid > div.order-last > div.inline-flex > p.py-2`
Lorem Ipsum è considerato il testo segnaposto standard sin dal sedicesimo secol… `div.grid > div.order-last > div.inline-flex > p.py-2`
180 / person `div.order-last > ul.flex > li.flex > span`
'Death in the Berlin Barn' transports players to a desolate, run-down barn on t… `div.grid > div.order-last > div.inline-flex > p.py-2`
Lord Alexander Dunham, a once-wealthy landowner, hosts an unconventional dinner… `div.grid > div.order-last > div.inline-flex > p.py-2`
Lady Emily Dunham, yearning for freedom, pursues a forbidden romance. Her troub… `div.grid > div.order-last > div.inline-flex > p.py-2`
When Lord Dunham is discovered murdered in the derelict barn, suspicion falls o… `div.grid > div.order-last > div.inline-flex > p.py-2`

These are opportunities to improve the legibility of your content.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.grid > div.shadow > div.grid > img.lg:hover:scale-110 `div.grid > div.shadow > div.grid > img.lg:hover:scale-110`
div.grid > div.shadow > div.grid > img.lg:hover:scale-110 `div.grid > div.shadow > div.grid > img.lg:hover:scale-110`
div.grid > div.shadow > div.grid > img.lg:hover:scale-110 `div.grid > div.shadow > div.grid > img.lg:hover:scale-110`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
span.inline-flex > ul.social > li > a `span.inline-flex > ul.social > li > a`
span.inline-flex > ul.social > li > a `span.inline-flex > ul.social > li > a`
span.inline-flex > ul.social > li > a `span.inline-flex > ul.social > li > a`
span.inline-flex > ul.social > li > a `span.inline-flex > ul.social > li > a`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
home about mystery gallery faq `body > div#root > div.flex > ul.top-[64px]`
6-8 \| Easy \| 180 / person `div#mysteryItem > div.grid > div.order-last > ul.flex`
6-8 \| Hard \| 180 / person `div#mysteryItem > div.grid > div.order-last > ul.flex`
4-10 \| Taxing \| 180 / person `div#mysteryItem > div.grid > div.order-last > ul.flex`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
home `div.flex > ul.top-[64px] > a.text-white > li.z-50`
about `div.flex > ul.top-[64px] > a > li.z-50`
mystery `div.flex > ul.top-[64px] > a > li.z-50`
gallery `div.flex > ul.top-[64px] > a > li.z-50`
faq `div.flex > ul.top-[64px] > a > li.z-50`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○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

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○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.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○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 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

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.

Content Best Practices

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.grid > div.shadow > div.grid > img.lg:hover:scale-110 `div.grid > div.shadow > div.grid > img.lg:hover:scale-110`
div.grid > div.shadow > div.grid > img.lg:hover:scale-110 `div.grid > div.shadow > div.grid > img.lg:hover:scale-110`
div.grid > div.shadow > div.grid > img.lg:hover:scale-110 `div.grid > div.shadow > div.grid > img.lg:hover:scale-110`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○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

●robots.txt is valid

●Document has a valid `hreflang`

○Document has a valid `rel=canonical`