shopdennys.com website review

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

actionbase.ai costs a phone 1.3 s of main-thread work and 222 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (actionbase.ai, Shopify and heatmap.com and others), adding 2.5 MB and 2.8 s of main-thread time.

About 930 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

20 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Shopify costs a phone 592 ms of main-thread work and 1.6 MB 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 125 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

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

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

heatmap.com costs a phone 382 ms of main-thread work and 100 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.

cloudfront.net costs a phone 288 ms of main-thread work and 232 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.

65 KiB could be saved by minifying JavaScript.

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

7 KiB JavaScript is shipped twice across bundles.

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.

4 KiB could be saved by minifying CSS.

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.

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

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

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

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

Real visitors wait 222 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

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

Your homepage downloads 10.3 MB in 668 requests on a phone: images 5.1 MB (125), scripts 2.5 MB (177) and other files 1.8 MB (331). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

Elements use prohibited ARIA attributes (1 element).

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

1 element has a tabindex above 0, which scrambles the keyboard order.

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

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

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

Your title is 78 characters, so Google will cut it off around 60: “Shop at Denny's | Children's Clothing Store | NY, NJ & FL – Denny's X Lester's”.

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

The homepage links to 614 pages on shopdennys.com and 22 external pages.

https://shopdennys.com/collections/shop-all-baby, https://shopdennys.com/collections/baby-girl-tops, https://shopdennys.com/collections/baby-girl-bottoms and https://shopdennys.com/collections/baby-girl-sets use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://shopdennys.com/collections/in-store-online-gift-cards/products/in-store-online-gift-card, whose canonical is https://shopdennys.com/products/in-store-online-gift-card. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://shopdennys.com/collections/new-arrivals, https://shopdennys.com/pages/store-locator, https://shopdennys.com/collections/in-store-online-gift-cards/products/in-store-online-gift-card, https://shopdennys.com/collections/shop-all-baby, https://shopdennys.com/collections/shop-baby-girl and https://shopdennys.com/collections/shop-baby-boy and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://shopdennys.com/collections/shop-infant-boy took over 3 s to send its HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

Large scripts ship without source maps.

1 image is served at too low a resolution for sharp phone screens.

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

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

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 Tag Manager, Klaviyo 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 20 cookies, 16 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.