Loupe LookoutSaltbrush & Sage

Saltbrush & Sage · Lookout Score 89

Speed 64

How fast pages load for real visitors (field data) and in the lab, and how quickly the server answers. Weight 15 of 105 in the Lookout Score.

Core Web Vitals for real visitors Warn

On phones, 75th percentile over 2026-10-22 to 2026-11-18: LCP 2.6 s (needs improvement), INP 168 ms (good), CLS 0.04 (good). Desktop: LCP 1.7 s, INP 71 ms, CLS 0.02.

Chrome UX Report, 21 Nov 2026, 06:11 MST · weight 3 · checked weekly

Why it matters, and what to do

This is what Google measures on real visitors' phones over the last 28 days, and it feeds ranking. It is the headline speed number because lab scores swing from run to run.

What to do: Images sized for the screen, fewer apps injecting scripts, a lighter theme section above the fold. Each poor metric has its own fix on the facet page.

Rule: LCP, INP and CLS all good: pass. One needs improvement: warn. Any poor: fail. Needs enough visitors for Google to publish field data.

Ask RDA to handle this

Lighthouse mobile performance Warn

Lab mobile performance 58 (average of 3 pages): home 61 mobile / 92 desktop; top collection 55 / 88; top product 58 / 90. Biggest opportunity: Improve image delivery (Estimated savings of 1.2 s).

PageSpeed Insights, 21 Nov 2026, 06:12 MST · weight 2 · checked weekly

Why it matters, and what to do

A lab run on a throttled phone connection. It swings run to run, so it is weighted below the field data, but it points at the specific resources slowing the page.

What to do: The three biggest opportunities from the run are listed on the facet page in plain words.

Rule: Average mobile score across the pages tested under 50: fail. Under 75: warn. Home, top collection and top product, mobile and desktop.

Ask RDA to handle this

Lighthouse accessibility Pass

Lighthouse accessibility 94 on the home (lowest of 3 pages).

PageSpeed Insights, 21 Nov 2026, 06:13 MST · weight 1 · checked weekly

Why it matters, and what to do

Contrast, labels and alt text: what makes the site usable with a screen reader or in bright sun, and part of what Google checks.

What to do: Fix the failed audits listed on the facet page; most are alt text and contrast.

Rule: Under 80: warn.

Server response time from two places Pass

Median 317 ms from New York over 288 pings today, 351 ms from New Jersey just now.

Lookout pings from New York and New Jersey, 21 Nov 2026, 23:40 MST · weight 1 · checked daily

Why it matters, and what to do

How long the server takes to start answering, before any page content loads. Measured from two vantage points so one slow route is not mistaken for a slow site.

What to do: On Shopify this is Shopify's edge; on WordPress it is hosting and caching. A slow first byte usually means a cache miss or an overloaded server.

Rule: Median time to first byte over 1.5 s: warn.

Figures

Lab speed (Lighthouse) 58

Mobile performance, average across the pages tested; lab figures swing run to run. Columns are the mobile run.

PageMobileDesktopLCPTBTCLSWeight
home61923.9 s310 ms0.032.6 MB, 96 req
top collection55884.3 s380 ms0.023.1 MB, 112 req
top product58904.0 s420 ms0.042.8 MB, 104 req

Biggest opportunities: Improve image delivery (Estimated savings of 1.2 s); Reduce unused JavaScript (0.9 s); Render-blocking requests (Estimated savings of 450 ms).

PageSpeed Insights (lab), Lighthouse 13.6.0, run 21 Nov 2026

Core Web Vitals (field)

Real Chrome visitors, 75th percentile, to . This is what Google measures.

MetricPhone p75RatingGoodDesktop p75Rating
LCP2.6 sneeds improvement68%1.7 sgood
INP168 msgood84%71 msgood
CLS0.04good81%0.02good

Chrome UX Report, origin https://saltbrushandsage.com, read 21 Nov 2026