lci1.com website review

About 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

22 files are served with short cache lifetimes, so returning visitors download them again (1.2 MB).

Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, formstack.com and Google CDN and others), adding 2.9 MB and 2.3 s of main-thread time.

3 images could be 331 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

formstack.com costs a phone 561 ms of main-thread work and 1,011 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.

Google Tag Manager costs a phone 582 ms of main-thread work and 521 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.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

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

Google CDN costs a phone 350 ms of main-thread work and 736 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.

Facebook costs a phone 270 ms of main-thread work and 282 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.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

About 56 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 49 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.

Your largest element takes 27.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Whenever, wherever, we make your experience better.”.

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

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

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

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

Real visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 12.9 MB in 223 requests on a phone: media 6.0 MB (1), scripts 3.3 MB (60) and other files 2.2 MB (106). Under 2 MB keeps phones on slow connections fast.

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

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

Documents must have <title> element to aid in navigation: 1 element on the page fails this check, rated serious by axe-core.

Your page has no <title>, so Google has to invent the blue link in search results.

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 275 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://corporate.lippert.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.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 81 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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

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

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