lizardcuecase.com website review

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

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

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

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

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

8 third-party services load with your homepage (Shopify, PayPal and Cloudflare CDN and others), adding 1.8 MB and 1.3 s of main-thread time.

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

PayPal costs a phone 339 ms of main-thread work and 392 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.

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

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

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.

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

19 KiB could be saved by minifying CSS.

11 KiB JavaScript is shipped twice across bundles.

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

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 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Load video:”.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 95 ms to 96 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 0.8 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.0 MB in 453 requests on a phone: scripts 1.6 MB (167), images 917 KiB (82) and other files 898 KiB (171). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

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

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

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

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

There are 2 <h1> headlines (“LIZARD CUE CASE” and “Lizard Rainbow Series Cue Case 3B4S”). One clear main headline is easier for people and search engines.

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

The homepage links to 149 pages on lizardcuecase.com and 27 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://lizardcuecase.com/pages/contact, https://lizardcuecase.com/pages/about, https://lizardcuecase.com/collections/all and https://lizardcuecase.com/collections/2-butts-x-2-shafts/2-Butts-x-2-Shafts have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://lizardcuecase.com/collections/2-butts-x-2-shafts/2-Butts-x-2-Shafts, whose canonical is https://lizardcuecase.com/collections/2-butts-x-2-shafts/2-butts-x-2-shafts. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://lizardcuecase.com/pages/contact, https://lizardcuecase.com/apps/track and https://lizardcuecase.com/blogs/news have no <h1> headline, so visitors and search engines get no clear main topic.

https://lizardcuecase.com/collections/3-butts-x-6-shafts/3-Butts-x-6-Shafts, https://lizardcuecase.com/collections/2-slots and https://lizardcuecase.com/collections/3-slots took over 3 s to send their HTML from our server.

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

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 503 ()”.

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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 1,136 words of visible text.

Before a visitor clicks anything, the page loads 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 14 cookies, 3 of them by other companies (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 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.