lytx.com website review

6 images could be 923 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

8 third-party services load with your homepage (Google Tag Manager, Wistia and Optanon and others), adding 1.2 MB and 1.4 s of main-thread time.

Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.

Google Tag Manager costs a phone 802 ms of main-thread work and 567 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 108 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

About 516 KiB of JavaScript is downloaded but never used on this page.

A phone's processor spends 3.2 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

11 long tasks block the main thread while loading, the longest for 302 ms. During a long task the page ignores taps.

Wistia costs a phone 255 ms of main-thread work and 316 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

15 files are served with short cache lifetimes, so returning visitors download them again (173 KiB).

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

The page becomes fully interactive after 19.6 s. Good is under 3.8 s.

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

Visually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 690 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 815 ms for your server to start answering (75th percentile). Good is under 800 ms.

The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

15 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 131 ms to 121 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1225-900-0247_hero-background-09.png weighs 694 KiB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example 1225-900-0247_hero-background-09.png at 2,200 px wide, shown at 388 px. Resized copies would save about 500 KiB.

Your homepage downloads 3.4 MB in 130 requests on a phone: scripts 1.4 MB (37), images 1.3 MB (29) and fonts 551 KiB (6). Under 2 MB keeps phones on slow connections fast.

3 images (785 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

By the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

6 images have no alt text, which hurts accessibility and image search.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Headings skip levels (h1 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (3 elements).

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 100 pages on lytx.com and 15 external pages.

There is no https://www.lytx.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

We fetched 15 pages linked from your homepage (of 59 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5511677&Ver=2&mid=22c05512-7c18-4681-87be-218f9fba8e8d&bo=1&sid=5bca1670d88e11f1b29de367d024bbab&vid=5bca40a0d88e11f193ade9b528fe80d3&vids=1&msclkid=N&pi=918639831&lg=.

3 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

5 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://www.clarity.ms/tag/z852uovvda?ref=gtm' violates the following Content Security Policy direc…”.

Chrome logged issues while loading the page (“Content security policy”).

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 820 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Microsoft Ads and 1 more (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 28 cookies (measured from a US location before any click).

Loading the homepage contacts 35 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.