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.

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

nodeLabel: Barrett Studio Architects

path: 1,HTML,1,BODY,0,DIV,0,HEADER,0,DIV,0,DIV,0,DIV,0,SPAN,0,A,0,IMG

selector: div.inner-container > span.logo > a > img

snippet: <img src="https://barrettstudio.com/wp-content/uploads/2024/12/BarrettStudioLogo.png" srcset="https://barrettstudio.com/wp-content/uploads/2024/12/BarrettStudioLogo.png…" sizes="(max-width: 340px) 100vw, 340px" height="100" width="300" alt="Barrett Studio Architects">

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

value: No additional origins are good candidates for preconnecting

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
barrettstudio.com/wp-content/themes/enfold/js/avia-compat.js?ver=6.0.8	1.2 KiB
/wp-content/themes/enfold/js/aviapopup/magnific-popup.min...	1.7 KiB
/wp-content/themes/enfold/css/avia-snippet-lightbox.css?v...	1.6 KiB
/wp-content/themes/enfold/css/avia-snippet-fold-unfold.cs...	1.1 KiB
barrettstudio.com/wp-content/themes/enfold/css/shortcodes.css?ver=6.0.8	7.6 KiB
barrettstudio.com/wp-content/uploads/dynamic_avia/enfold.css?ver=69fb80e1216ca	21.2 KiB
barrettstudio.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1	31.1 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	843 B
barrettstudio.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1	5.2 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	882 B
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	1.2 KiB
barrettstudio.com/wp-content/themes/enfold/js/avia-js.js?ver=6.0.8	1.2 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	1.6 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	1.7 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	1.9 KiB
/wp-content/plugins/youtube-embed-plus/styles/ytprefs.min...	2.0 KiB
/wp-content/uploads/dynamic_avia/avia_posts_css/post-12.c...	744 B
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	1.4 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	1.1 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	2.5 KiB
barrettstudio.com/wp-content/themes/enfold/css/avia-snippet-widget.css?ver=6.0.8	5.2 KiB	360 ms
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	1.6 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	1021 B
/wp-content/themes/enfold/css/avia-snippet-site-preloader...	926 B
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	962 B
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	1.3 KiB
barrettstudio.com/wp-content/themes/enfold/css/custom.css?ver=6.0.8	573 B
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	3.7 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	1.3 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	3.3 KiB
/wp-content/plugins/youtube-embed-plus/scripts/ytprefs.mi...	5.0 KiB
barrettstudio.com/wp-content/themes/enfold/css/layout.css?ver=6.0.8	16.5 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	1.7 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	4.4 KiB	360 ms
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	1.9 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	3.0 KiB
barrettstudio.com/wp-content/themes/enfold/css/grid.css?ver=6.0.8	2.7 KiB
barrettstudio.com/wp-content/themes/enfold/css/base.css?ver=6.0.8	5.6 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	1.3 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	644 B

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
ssl.google-analytics.com/ga.js	7200.0 s	17.4 KiB
assets.dwell.com/badges/s-160x160.png	0.0 ms	2.7 KiB

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.

URL	Est Savings
fonts.gstatic.com/s/lato/v25/S6u9w4BMUTPHh7USSwiPGQ3q5d0.woff2	15 ms
fonts.gstatic.com/s/lato/v25/S6uyw4BMUTPHjx4wXiWtFCc.woff2	10 ms
/s/playfairdisplay/v40/nuFiD-vYSZviVYUb_rj3ij__anPXDTzYgE...	10 ms
fonts.gstatic.com/s/lato/v25/S6u9w4BMUTPHh6UVSwiPGQ3q5d0.woff2	10 ms

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
div.avia-image-container-inner > div.avia-image-overlay-wrap > a.avia_image > img.wp-image-8891 `div.avia-image-container-inner > div.avia-image-overlay-wrap > a.avia_image > img.wp-image-8891`	barrettstudio.com/wp-content/uploads/2022/11/StudioHome2022.jpg	292.5 KiB	248.5 KiB
div.avia-fullscreen-slider > div.avia-slideshow > ul.avia-slideshow-inner > li.avia-slideshow-slide `div.avia-fullscreen-slider > div.avia-slideshow > ul.avia-slideshow-inner > li.avia-slideshow-slide`	/wp-content/uploads/2016/06/1-Boulder-Modern-Architecture...	455.6 KiB	162.6 KiB
Barrett Studio Architects `div.inner-container > span.logo > a > img`	barrettstudio.com/wp-content/uploads/2024/12/BarrettStudioLogo.png	27.9 KiB	22.3 KiB
div.avia-image-container-inner > div.avia-image-overlay-wrap > a.avia_image > img.wp-image-5473 `div.avia-image-container-inner > div.avia-image-overlay-wrap > a.avia_image > img.wp-image-5473`	barrettstudio.com/wp-content/uploads/2016/06/Home1-1.jpg	63.0 KiB	19.0 KiB
Instagram `div.textwidget > p > a > img.alignleft`	barrettstudio.com/wp-content/uploads/2024/12/instagram-logo.png	7.7 KiB	7.2 KiB
Houzz Design Award `div.textwidget > p > a > img.alignleft`	st.hzcdn.com/static/badge_46_7@2x.png	6.5 KiB	5.1 KiB

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

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: 60 ms 31.3 KiB

URL	Transfer Size	Est Savings
barrettstudio.com/wp-content/uploads/dynamic_avia/enfold.css?ver=69fb80e1216ca	20.9 KiB	17.2 KiB
barrettstudio.com/wp-content/themes/enfold/css/layout.css?ver=6.0.8	16.2 KiB	14.1 KiB

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 5.5 KiB

URL	Transfer Size	Est Savings
barrettstudio.com/wp-content/themes/enfold/css/layout.css?ver=6.0.8	16.5 KiB	3.2 KiB
barrettstudio.com/wp-content/themes/enfold/css/shortcodes.css?ver=6.0.8	7.6 KiB	2.2 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 18.4 KiB

URL	Transfer Size	Est Savings
barrettstudio.com/wp-content/themes/enfold/js/avia.js?ver=6.0.8	16.2 KiB	6.5 KiB
barrettstudio.com/wp-content/themes/enfold/js/shortcodes.js?ver=6.0.8	11.5 KiB	4.4 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	9.7 KiB	4.1 KiB
/wp-content/themes/enfold/config-templatebuilder/avia-sho...	6.7 KiB	3.3 KiB

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

●Max Potential First Input Delay 80 ms

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Reduce unused JavaScript

●Avoids enormous network payloads Total size was 2,593 KiB

●JavaScript execution time 0.4 s

●Minimizes main-thread work 1.9 s

●Avoid long main-thread tasks 5 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 210 ms

●Server Backend Latencies 530 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 240 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

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
Living Architecture `section.av_textblock_section > div.avia_textblock > p > a`
“Whether it’s a poetic seed, an impulse to connect, a DNA, or finding the soul … `div.flex_column > section.av_textblock_section > div.avia_textblock > h5`

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
div.flex_column > section.av_textblock_section > div.avia_textblock > h5 `div.flex_column > section.av_textblock_section > div.avia_textblock > h5`

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
form#mc-embedded-subscribe-form > div#mc_embed_signup_scroll > div > input `form#mc-embedded-subscribe-form > div#mc_embed_signup_scroll > div > input`

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.

○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

●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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●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

●`[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

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

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

○`[accesskey]` values are unique

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

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○Buttons have an accessible name

○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

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

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

Best Practices

Trust and Safety

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URL	Request Resolution
st.hzcdn.com/static/badge_46_7@2x.png	Automatically upgraded to HTTPS
st.hzcdn.com/static/badge_43_7@2x.png	Automatically upgraded to HTTPS
st.hzcdn.com/static/badge_40_7@2x.png	Automatically upgraded to HTTPS
st.hzcdn.com/static/badge_21_7@2x.png	Automatically upgraded to HTTPS
st.hzcdn.com/static/badge_15_7@2x.png	Automatically upgraded to HTTPS
st.hzcdn.com/static/badge_12_7@2x.png	Automatically upgraded to HTTPS
st.hzcdn.com/static/badge_7_7@2x.png	Automatically upgraded to HTTPS

General

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
Mixed content

●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

●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

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`