dillards.com website review

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

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

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

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

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

8 third-party services load with your homepage (talkdeskapp.com, sdiapi.com and nmgassets.com and others), adding 2.7 MB and 1.3 s of main-thread time.

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

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

talkdeskapp.com costs a phone 375 ms of main-thread work and 1.9 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 81 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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.

Your largest element takes 14.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Shop Dillard's Exclusive Hadley Greene x Gianni Bini Collab…”.

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

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

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

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

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

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

Your homepage downloads 4.1 MB in 176 requests on a phone: scripts 2.7 MB (80), fonts 754 KiB (8) and images 216 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Links must have discernible text: 37 elements on the page fail this check, rated serious by axe-core.

8 tap targets are too small or too close together to hit reliably with a finger.

Form elements should have a visible label: 2 elements on the page fail this check, rated serious by axe-core.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 2 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.

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 51 pages on dillards.com and 11 external pages.

The HTML your server sends has 387 of the 869 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

/webapp/wcs/stores/servlet/OrderItemDisplay is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/webapp/wcs/stores/servlet/OrderItemDisplay has no meta description, so Google writes the search snippet from whatever text it finds.

/c/back-in-stock and /c/limited-availability took over 3 s to send their HTML from our server.

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

10 images failed to load on a phone, for example https://fsbozl.dillards.com/g/uids?pld=Fcff-UF9iDDVXaRU37SXjfu-VEJFRzjFIuMV53v0NS2Mc_EeuQ_KCQr0wB3vJFEGONEX8t-HASpavFZiyysqoqEsJRb6ZLfmTF7ZefPjTssa8Yhw-mwPZ6n9lHp-CPicF5_ubyodk3ZdwnSWvc3HaRUCVUcqpOuvs.

24 of 48 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 2 deprecated browser APIs that will stop working in future browsers (“`StorageType.persistent` is deprecated. Please use standardized `navigator.storage` instead.”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads Criteo, Google Tag Manager, Meta Pixel, Microsoft Ads and Pinterest Tag and 4 mores (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 43 cookies (measured from a US location before any click).

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