stewleonardsgifts.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Stripe and others), adding 1.6 MB and 1.3 s of main-thread time.

1 image could be 129 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

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

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

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

Facebook costs a phone 340 ms of main-thread work and 315 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.

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

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

17 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.

36 KiB could be saved by minifying JavaScript.

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 wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

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

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

Your homepage downloads 4.8 MB in 401 requests on a phone: scripts 4.0 MB (287), images 337 KiB (20) and HTML 230 KiB (6). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Goldbelly_3000x600_HP_Banner.jpg at 1,500 px wide, shown at 390 px. Resized copies would save about 33 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

No XML sitemap at https://stewleonards.goldbelly.com/sitemap.xml, so Google discovers your pages only by following links.

Open Graph is missing og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 7 pages on stewleonardsgifts.com and 0 external pages.

A phone browser shows 404 words, but the HTML your server sends has only 15. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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://stewleonards.goldbelly.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://stewleonards.goldbelly.com/categories/all-products, https://stewleonards.goldbelly.com/categories/gift-boxes, https://stewleonards.goldbelly.com/categories/stews-merch, https://stewleonards.goldbelly.com/categories/gift-card and https://stewleonards.goldbelly.com/categories/group-corporate-gifting and 2 others all use the title “Stew Leonard's Delivered Nationwide - Goldbelly”. Search engines can't tell which page to show for a search, so each competes with the others.

https://stewleonards.goldbelly.com/categories/all-products, https://stewleonards.goldbelly.com/categories/gift-boxes, https://stewleonards.goldbelly.com/categories/stews-merch, https://stewleonards.goldbelly.com/categories/gift-card, https://stewleonards.goldbelly.com/categories/group-corporate-gifting and https://stewleonards.goldbelly.com/categories/sympathy and 1 other use the same meta description. A description written for each page earns more clicks.

https://stewleonards.goldbelly.com/categories/all-products, https://stewleonards.goldbelly.com/categories/gift-boxes, https://stewleonards.goldbelly.com/categories/stews-merch, https://stewleonards.goldbelly.com/categories/gift-card, https://stewleonards.goldbelly.com/categories/group-corporate-gifting and https://stewleonards.goldbelly.com/categories/sympathy and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://stewleonards.goldbelly.com/categories/all-products, https://stewleonards.goldbelly.com/categories/gift-boxes, https://stewleonards.goldbelly.com/categories/stews-merch, https://stewleonards.goldbelly.com/categories/gift-card, https://stewleonards.goldbelly.com/categories/group-corporate-gifting and https://stewleonards.goldbelly.com/categories/sympathy and 1 other have 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.

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

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=5500049&Ver=2&mid=d705735a-0370-4263-a2dd-9f73aefc9439&bo=1&sid=ce82d5e0dde911f19483115eecd0a4b8&vid=ce82faa0dde911f1a44303e495455997&vids=1&msclkid=N&pi=918639831&lg=.

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

Large scripts ship without source maps.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

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

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

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