lesign.co website review

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

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

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

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

3 third-party services load with your homepage (Shopify, conversionbear.com and shop.app), adding 1.1 MB and 239 ms of main-thread time.

Shopify costs a phone 224 ms of main-thread work and 1,024 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.

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

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

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

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

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

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 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “slider image 1621243260e1af0c20-0”.

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 3.4 MB in 373 requests on a phone: images 1.1 MB (21), other files 1.0 MB (193) and scripts 937 KiB (123). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.98 g of CO₂e: 117.3 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.

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Your title is 68 characters, so Google will cut it off around 60: “Personalized Pet Memorial Signs | Custom Wooden Pet Tribute – LeSign”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 31 pages on lesign.co and 4 external pages.

https://lesign.co/discount/DAY10 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://lesign.co/discount/DAY10 all use the title “Personalized Pet Memorial Signs | Custom Wooden Pet Tribute – LeSign”. Search engines can't tell which page to show for a search, so each competes with the others.

https://lesign.co/policies/privacy-policy, https://lesign.co/policies/shipping-policy, https://lesign.co/policies/refund-policy and https://lesign.co/policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

https://lesign.co/apps/track123 has no <h1> headline, so visitors and search engines get no clear main topic.

https://lesign.co/apps/track123 took over 3 s to send its HTML from our server.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'classList')”.

Social proof on the homepage: 1 customer or partner logo. 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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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