starlightceiling.com website review

About 411 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

6 third-party services load with your homepage (Shopify, tidio.co and breadpayments.com and others), adding 10.3 MB and 224 ms of main-thread time.

Shopify costs a phone 114 ms of main-thread work and 9.6 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.

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

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

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

tidio.co costs a phone 72 ms of main-thread work and 515 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.

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

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

39 KiB could be saved by minifying JavaScript.

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

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.

4 KiB could be saved by minifying CSS.

3 KiB JavaScript is shipped twice across bundles.

Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Pre-Built Fiber Optic Starlight Ceiling Panels”.

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

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

The first text or image appears after 2.0 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 96 ms to 95 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.7 MB in 187 requests on a phone: media 9.3 MB (4), scripts 1,017 KiB (61) and other files 688 KiB (87). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

Your title is 66 characters, so Google will cut it off around 60: “Starlight Ceiling — Star Ceiling Lights, Fiber Optic Panels & Kits”.

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

The homepage links to 53 pages on starlightceiling.com and 5 external pages.

https://www.starlightceiling.com/en-us/pages/contact and https://www.starlightceiling.com/pages/contact all use the title “Contact Starlight Ceiling — Tell Us About the Room”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.starlightceiling.com/pages/installation-guide and https://www.starlightceiling.com/en-us/pages/free-design have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.starlightceiling.com/en-us/pages/contact and https://www.starlightceiling.com/pages/contact use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.starlightceiling.com/pages/installation-guide, whose canonical is https://www.starlightceiling.com/en-us/pages/installation-guide. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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.

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

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