citylightssftrade.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Klaviyo and Google Tag Manager and others), adding 2.8 MB and 1.5 s of main-thread time.

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

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

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

Shopify costs a phone 610 ms of main-thread work and 1.4 MB 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 (144 KiB).

Klaviyo costs a phone 227 ms of main-thread work and 654 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 184 ms of main-thread work and 362 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 155 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

14 KiB could be saved by minifying CSS.

9 KiB could be saved by minifying JavaScript.

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.

Your largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “4.85/5 Based On 1779 Happy Customers Luxury Lighting With E…”.

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

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

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

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

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

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

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

Your homepage downloads 8.5 MB in 747 requests on a phone: images 3.9 MB (199), scripts 2.2 MB (201) and other files 1.6 MB (274). Under 2 MB keeps phones on slow connections fast.

9 images are downloaded at several times the size a phone draws them, for example HP_Pendants_Herman_Miller.jpg at 1,080 px wide, shown at 173 px. Resized copies would save about 668 KiB.

10 images further down the page (717 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images (91 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 2.42 g of CO₂e: 289.9 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”.

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

Some list items are not inside a list.

1 tap target is too small or too close together to hit reliably with a finger.

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 441 pages on citylightssftrade.com and 4 external pages.

https://citylightssf.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://citylightssf.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://citylightssf.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

https://citylightssf.com/pages/accessibility, https://citylightssf.com/collections/all, https://citylightssf.com/customer_authentication/redirect, https://citylightssf.com/collections/sale, https://citylightssf.com/pages/trade and https://citylightssf.com/pages/our-showroom and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://citylightssf.com/pages/accessibility, https://citylightssf.com/collections/all, https://citylightssf.com/collections/sale, https://citylightssf.com/pages/trade, https://citylightssf.com/pages/our-showroom and https://citylightssf.com/collections/plug-in-pendant-lights and 8 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

2 images failed to load on a phone, for example https://i.liadm.com/s/85221?&aid=e2330fdc-5712-461c-aa49-6cae0996390a&ref=P2ND46P56&_=0.07407965164190822.

6 errors were logged to the browser console while the page loaded, for example “carousel is not defined”.

Large scripts ship without source maps.

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

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo and Microsoft Clarity (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 28 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 51 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.