lg.com website review

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

audioeye.com costs a phone 2.3 s of main-thread work and 332 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

Google Tag Manager costs a phone 1.2 s of main-thread work and 1.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

The page has 8,098 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (audioeye.com, Google Tag Manager and Optimizely and others), adding 3.3 MB and 5.4 s of main-thread time.

About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

Optimizely costs a phone 932 ms of main-thread work and 340 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.

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

30 images could be 602 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

transcend.io costs a phone 340 ms of main-thread work and 160 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.

sprinklr.com costs a phone 245 ms of main-thread work and 580 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.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 300 ms.

Polyfills for old browsers add 60 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

81 KiB could be saved by minifying JavaScript.

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

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 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “LG Deal Days promotional graphic featuring the LG QNED evo …”.

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

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

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

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

The layout shifts by 0.254 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Real visitors wait 415 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

Your homepage downloads 8.3 MB in 543 requests on a phone: scripts 4.5 MB (150), images 2.7 MB (231) and fonts 571 KiB (5). Under 2 MB keeps phones on slow connections fast.

HS_LAUNDRY_PREMIUM_PAIR_150-200_900x600 is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

Certain ARIA roles must be contained by particular parents: 8 elements on the page fail this check, rated critical by axe-core.

6 buttons have no accessible name, so screen readers announce just “button”.

42 elements hidden from screen readers can still receive keyboard focus.

Some list items are not inside a list.

Interactive controls must not be nested: 6 elements on the page fail this check, rated serious by axe-core.

ARIA commands must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.

Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

All page content should be contained by landmarks: 39 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

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

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

The homepage links to 524 pages on lg.com and 17 external pages.

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.

https://www.lg.com/us/discount-programs has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.lg.com/us/mylg-ownership-program, whose canonical is https://www.lg.com/us/promotions/mylg-ownership-program. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.lg.com/us/appreciation-program and https://www.lg.com/us/lg-partner-store have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.lg.com/us/promotions/home-appliance-rebates, https://www.lg.com/us/promotions/soundbar-bundle-savings and https://www.lg.com/us/promotions/tv-sale-deals took over 3 s to send their HTML from our server.

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

5 images failed to load on a phone, for example https://soxnwz.lg.com/g/uids?pld=GTfS9lmWwcJCUbC8NFiJJ3Z3bADwSyJ6_9GNB-JlIltokhqiceXNQIKOfbBnm8NWhjNe0aCGnj_INTWZ53ByqK3cbQKm_Wq4RtHOatRtS1-zpkpAnNIXVw5ISlf90_k7f7W3uMje18sAAOeOZC0iKA6uDKT3CmAOBU0XqK7.

26 of 72 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.

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

2 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use …”.

Requests the geolocation permission on page load.

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

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

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

The homepage carries about 1,352 words of visible text.

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

Before a visitor clicks anything, the page loads Amazon Ads, Criteo, FullStory, Google Ads and Google Tag Manager and 11 mores (measured from a US location before any click). A consent tool (Transcend) is installed; check it blocks these until visitors agree where the law requires it.

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

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