kingsofneon.com website review

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

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

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

25 images could be 3.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

About 292 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.

8 third-party services load with your homepage (Google Tag Manager, Shopify and Clarity and others), adding 745 KiB and 624 ms of main-thread time.

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

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

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

4 KiB could be saved by minifying CSS.

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

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

26 KiB JavaScript is shipped twice across bundles.

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.

3 KiB could be saved by minifying JavaScript.

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Black Friday sale on now”.

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

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

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

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

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

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

Your homepage downloads 26.5 MB in 313 requests on a phone: media 16.6 MB (2), images 7.9 MB (117) and scripts 1.1 MB (74). Under 2 MB keeps phones on slow connections fast.

4 images weigh 7.9 MB together. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example 586f59757ddbaf3c78d841adad006179.gif at 390 px wide, shown at 100 px. Resized copies would save about 3.8 MB.

12 images (8.9 MB) 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 7.52 g of CO₂e: 902.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

9 tap targets are too small or too close together to hit reliably with a finger.

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

4 visible links have no text or label, so screen readers cannot say where they go.

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

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

Elements with visible text labels do not have matching accessible names. (3 elements).

There are 2 <h1> headlines (“Kings Of Neon® USA” and “STAND OUT”). One clear main headline is easier for people and search engines.

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

1 link has no real href, so search engines can't follow it.

The homepage links to 266 pages on kingsofneon.com and 16 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.kingsofneon.com/pages/create-your-own and https://www.kingsofneon.com/collections/shop-all have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.kingsofneon.com/collections/shop-all, https://www.kingsofneon.com/collections/face-lit-signs and https://www.kingsofneon.com/collections/back-lit-signs have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 4 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 32 cookies, 10 of them by other companies (measured from a US location before any click).

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