ledmyplace.com website review

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

8 third-party services load with your homepage (Google Tag Manager, figpii.com and loox.io and others), adding 1.9 MB and 1.8 s of main-thread time.

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

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

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

About 696 KiB of JavaScript is downloaded but never used on this page.

Google Tag Manager costs a phone 498 ms of main-thread work and 526 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.

figpii.com costs a phone 443 ms of main-thread work and 49 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.

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

loox.io costs a phone 205 ms of main-thread work and 456 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.

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

Google CDN costs a phone 204 ms of main-thread work and 320 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 47 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 files are served with short cache lifetimes, so returning visitors download them again (176 KiB).

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

Polyfills for old browsers add 35 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.

3 KiB could be saved by minifying JavaScript.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

For real visitors the layout shifts by 0.28 (75th percentile). Good is under 0.1.

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

Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

Your homepage downloads 5.0 MB in 463 requests on a phone: scripts 2.1 MB (109), images 1.6 MB (168) and other files 930 KiB (142). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example Glowing_Gift_Box_October_Lighting_Sale_1.webp at 1,512 px wide, shown at 360 px. Resized copies would save about 326 KiB.

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

2 images (366 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 1.42 g of CO₂e: 170.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 elements hidden from screen readers can still receive keyboard focus.

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

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

ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

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

The homepage links to 310 pages on ledmyplace.com and 19 external pages.

There is no https://www.ledmyplace.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.ledmyplace.com/pages/free-shipping-on-99, whose canonical is https://www.ledmyplace.com/pages/free-shipping-above-99. 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 122 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=211049439&Ver=2&mid=3dc24838-7e46-4200-b201-d6923c21bc6b&bo=1&sid=054e1b40d8ab11f1884c35987f17d52b&vid=054e3f60d8ab11f1a10c3f29cecd183d&vids=1&msclkid=N&pi=918639831&l.

5 errors were logged to the browser console while the page loaded, for example “Unexpected token '**'”.

10 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Requests the notification permission on page load.

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

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