leidys.com website review

105 files are served with short cache lifetimes, so returning visitors download them again (6.4 MB).

9 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.2 s faster on a phone.

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

About 1.3 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.2 s faster on a phone.

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

Your mobile performance score is 54 (desktop: 60). Pages that score under 90 lose visitors before the first paint.

Google Tag Manager costs a phone 188 ms of main-thread work and 306 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.1 s on main-thread work while loading, 841 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

5 third-party services load with your homepage (Google Tag Manager, Hubspot and WordPress Site Stats and others), adding 472 KiB and 250 ms of main-thread time.

Polyfills for old browsers add 46 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

14 KiB could be saved by minifying CSS.

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.

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.

Real visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.

Real visitors wait 2.5 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your largest element takes 33.6 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 15.5 s (Speed Index). Good is under 3.4 s.

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

Real visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your homepage downloads 7.1 MB in 118 requests on a phone: images 3.6 MB (22), scripts 1.7 MB (79) and stylesheets 1.2 MB (6). Under 2 MB keeps phones on slow connections fast.

bg-anim_02.png weighs 1.6 MB. On a phone connection a single image that size takes seconds.

11 images (2.1 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.

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

1 image is downloaded at several times the size a phone draws it, for example logo-home-anim.png at 1,920 px wide, shown at 624 px. Resized copies would save about 5 KiB.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to 58 pages on leidys.com and 5 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.

There is no https://leidys.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.

https://leidys.com/natures-tradition, https://leidys.com/all-products, https://leidys.com/all-products/natures-tradition-product, https://leidys.com/all-products/bacon, https://leidys.com/all-products/ham and https://leidys.com/all-products/sausage and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://leidys.com/natures-tradition, https://leidys.com/all-products, https://leidys.com/all-products/natures-tradition-product, https://leidys.com/all-products/bacon, https://leidys.com/all-products/ham and https://leidys.com/all-products/sausage and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://leidys.com/retail-locations has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://leidys.com/natures-tradition, https://leidys.com/all-products, https://leidys.com/all-products/natures-tradition-product, https://leidys.com/all-products/bacon, https://leidys.com/all-products/ham and https://leidys.com/all-products/smoked-sausage and 5 others took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'addEventListener')”.

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

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.

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

The homepage has only about 178 words of visible text; thin pages give Google and first-time buyers little to go on.

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

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and HubSpot (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 6 cookies (measured from a US location before any click).

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