lightcorp.com website review

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

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

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

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

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

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

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

Facebook costs a phone 252 ms of main-thread work and 221 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 page has 1,818 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

1 image could be 52 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

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

19 KiB could be saved by minifying JavaScript.

Desktop scores 85 but mobile only 49. A gap that wide usually means heavy scripts and images that hit phones hardest.

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.

2 KiB could be saved by minifying CSS.

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.

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

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

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

Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We're on CET! Specifying our products has never been easier…”.

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

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

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

Real visitors wait 3.7 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-10, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 3.0 MB in 164 requests on a phone: scripts 1.7 MB (74), other files 351 KiB (10) and stylesheets 298 KiB (63). Under 2 MB keeps phones on slow connections fast.

1 image (53 KiB) is 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.84 g of CO₂e: 101.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 link inside paragraphs relies on colour alone to stand out.

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

There are 10 <h1> headlines (“We're on CET!”, “Product Lines” and “Capabilities”). One clear main headline is easier for people and search engines.

3 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 81 pages on lightcorp.com and 9 external pages.

There is no /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.

/products, /categories/under-mount-power and /categories/portable-power-and-power-strips have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'replace')”.

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.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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 300 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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