Skip to content
https://www.hillhousehome.com/pages/contact-us

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.

25

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:43.863 source:map[column:29117 line:0 type:source-location url:https://www.hillhousehome.com/cdn/shopifycloud/perf-kit/shopify-perf-kit-3.11.0.min.js urlProvider:network]] map[reflowTime:53.096 source:map[type:text value:[unattributed]]] map[reflowTime:2.237 source:map[column:7440 line:0 type:source-location url:https://www.hillhousehome.com/cdn/shop/t/566/assets/bundled-carousel.directive.js?v=136122985305739386131792431518&f=bundled-carousel.directive.js urlProvider:network]] map[reflowTime:0.69 source:map[column:16452 line:0 type:source-location url:https://www.hillhousehome.com/cdn/shop/t/566/assets/bundled-carousel.directive.js?v=136122985305739386131792431518&f=bundled-carousel.directive.js urlProvider:network]] map[reflowTime:25.446 source:map[column:4255 line:186 type:source-location url:https://www.hillhousehome.com/cdn/shop/t/566/assets/bundled-app.js?v=34250425883287296351792431515&f=bundled-app.js urlProvider:network]] map[reflowTime:0.583 source:map[column:14371 line:186 type:source-location url:https://www.hillhousehome.com/cdn/shop/t/566/assets/bundled-app.js?v=34250425883287296351792431515&f=bundled-app.js urlProvider:network]] map[reflowTime:0.57 source:map[column:19919 line:186 type:source-location url:https://www.hillhousehome.com/cdn/shop/t/566/assets/bundled-app.js?v=34250425883287296351792431515&f=bundled-app.js urlProvider:network]] map[reflowTime:0.781 source:map[column:854 line:3 type:source-location url:https://www.hillhousehome.com/cdn/shop/t/566/assets/bundled-gift-form.directive.js?v=90698548312885913271792431509&f=bundled-gift-form.directive.js urlProvider:network]]]

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.

URLResource SizeEst Savings
ENJOY 15% OFF YOUR FIRST ORDER Email CONTINUE div.needsclick > div.needsclick > div.needsclick > form.needsclick
/company/gDHDse/images/e047c3f0-aaa2-47a7-bb3f-747a2b715f...320.1 KiB85.8 KiB

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:189.811 label:Time to first byte subpart:timeToFirstByte] map[duration:8838.773 label:Resource load delay subpart:resourceLoadDelay] map[duration:219.419 label:Resource load duration subpart:resourceLoadDuration] map[duration:63.537 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-FORM
nodeLabel: ENJOY 15% OFF YOUR FIRST ORDER Email CONTINUE
path: 1,HTML,1,BODY,32,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,FORM
selector: div.needsclick > div.needsclick > div.needsclick > form.needsclick
snippet: <form aria-live="polite" data-testid="klaviyo-form-TibCWk" novalidate="" class="needsclick klaviyo-form klaviyo-form-version-cid_1 go3279073480 kl-private…" style="display: flex; flex-direction: row; box-sizing: border-box; width: 390px;">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-FORM
nodeLabel: ENJOY 15% OFF YOUR FIRST ORDER Email CONTINUE
path: 1,HTML,1,BODY,32,DIV,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,FORM
selector: div.needsclick > div.needsclick > div.needsclick > form.needsclick
snippet: <form aria-live="polite" data-testid="klaviyo-form-TibCWk" novalidate="" class="needsclick klaviyo-form klaviyo-form-version-cid_1 go3279073480 kl-private…" style="display: flex; flex-direction: row; box-sizing: border-box; width: 390px;">

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.

More than 4 preconnect connections were found. These should be used sparingly and only to the most important origins.
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.

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

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

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

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 900 ms 79.9 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
/cdn/shop/t/566/assets/bundled-carousel.directive.js?v=13...6.7 s1.9 s0.0 ms
Unattributable4.3 s1.1 s0.0 ms
www.hillhousehome.com/pages/contact-us3.5 s1.7 s52 ms
www.hillhousehome.com/cdn/wpm/b49d3b31aw169a7c20pfc9cb2c9m68241e55m.js2.7 s2.0 s32 ms
event-observer-collector.js1.4 s1.2 s0.0 ms
cdn.intelligems.io/esm/ebb9c452aba6/bundle.js611 ms483 ms2.7 ms
cdn.rebuyengine.com/onsite/js/global-4acfb30b81b0a18d696e.js492 ms402 ms83 ms
dashboard.heatmap.com/preprocessor.min.js?sid=3390443 ms365 ms23 ms
/cdn/s/trekkie.storefront.6efba1340ec6769622eb0d10b5cb070...431 ms417 ms10 ms
cdn.shopify.com/shopifycloud/shop-js/modules/v2/chunk.register_BK1wmFlx.esm.js388 ms385 ms0.3 ms
/cdn/shop/t/566/assets/bundled-app.js?v=34250425883287296...384 ms213 ms0.0 ms
www.googletagmanager.com/gtag/js?id=AW-697040076384 ms333 ms49 ms
www.hillhousehome.com/cdn/shopifycloud/perf-kit/shopify-perf-kit-3.11.0.min.js359 ms172 ms8.5 ms
/cdn/shop/t/566/assets/bundled-xhr-hijack.js?v=8912505736...350 ms308 ms0.1 ms
connect.facebook.net/en_US/fbevents.js344 ms282 ms46 ms
/signals/config/1645716422412209?v=2.9.427&r=stable&domai...285 ms240 ms45 ms
dashboard.heatmap.com/heatmap-light.min.js?sid=3390&_v=1792663148706271 ms233 ms8.2 ms
static.klaviyo.com/onsite/js/vendors~.bf6126b032be2.js?cb=2268 ms247 ms3.7 ms
/onsite/js/vendors~reviews~in_app_forms~signup_forms~atla...264 ms230 ms2.8 ms
cdn.jsdelivr.net/npm/@appmate/wishlist@4.29.2/wishlist-app.js173 ms138 ms0.1 ms
static.klaviyo.com/onsite/js/Render.39c98c70373f7.js?cb=2162 ms136 ms26 ms
/web-pixels@49d3b31aw169a7c20pfc9cb2c9m68241e55/app/web-p...103 ms99 ms1.5 ms
static.klaviyo.com/onsite/js/sharedUtils.8924fbc03f1d0.js?cb=298 ms62 ms4.8 ms
cdn.rebuyengine.com/onsite/js/rebuy.js?shop=hill-house-home.myshopify.com65 ms57 ms6.2 ms
cdn-static.okendo.io/reviews-widget-plus/js/okendo-reviews.js63 ms13 ms3.8 ms
/onsite/js/default~Render~ClientStore~~onsite-back-in-sto...62 ms60 ms1.2 ms
/cdn/shop/t/566/assets/es-module-shims.js?v=1479724620423...51 ms43 ms4.8 ms

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
Script Evaluation13.6 s
Other8.9 s
Style & Layout1.7 s
Rendering519 ms
Script Parsing & Compilation516 ms
Garbage Collection416 ms
Parse HTML & CSS196 ms

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

●Layout shift culprits
●Document request latency
●Optimize DOM size
●Font display
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 123 user timings
●Avoid long main-thread tasks 20 long tasks found
●Image elements have explicit `width` and `height`
●Network Requests
●Network Round Trip Times 180 ms
●Server Backend Latencies 310 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 140 ms
○INP breakdown
○Avoid non-composited animations
○Avoid large layout shifts
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.

○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.
●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
●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 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
○`[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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
92

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
Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin
Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 404 ()
Failed to load resource: the server responded with a status of 429 ()
ReferenceError: OneTrust is not defined at https://www.hillhousehome.com/pages/contact-us:4589:11 at Array.forEach (<anonymous>) at https://www.hillhousehome.com/pages/contact-us:4577:30

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Blocked by cross-origin policy
●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
●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
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
100

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.

○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`
○Image elements have `[alt]` attributes

Send Feedback