altmanluggage.com website review

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

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

8 third-party services load with your homepage (Hotjar, Accessibe Accessibility Overlay and Shopify and others), adding 1.2 MB and 1.0 s of main-thread time.

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

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

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

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

Hotjar costs a phone 323 ms of main-thread work and 65 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.

Accessibe Accessibility Overlay costs a phone 291 ms of main-thread work and 256 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.

Shopify costs a phone 178 ms of main-thread work and 494 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.

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

9 images could be 168 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 28 KiB of CSS is downloaded but never applied on this page.

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

4 KiB could be saved by minifying CSS.

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

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

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

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

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

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

1 image 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 93 ms to 99 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.9 MB in 443 requests on a phone: images 2.5 MB (156), scripts 1.1 MB (115) and other files 695 KiB (104). Under 2 MB keeps phones on slow connections fast.

Altman_Black_Friday_2026_Mobile_533x.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

2 dropdowns have no label.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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: 19 elements on the page fail this check, rated moderate by axe-core.

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

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Headings skip levels (h2 → h5, h3 → h5 and 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 70 characters, so Google will cut it off around 60: “Altman Luggage | Luggage, Pens, and Travel Accessories | New York City”.

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

The homepage links to 957 pages on altmanluggage.com and 4 external pages.

https://altmanluggage.com/policies/shipping-policy, https://altmanluggage.com/collections/aidan-the-brand, https://altmanluggage.com/collections/american-tourister, https://altmanluggage.com/collections/arlo-skye, https://altmanluggage.com/collections/armourlite and https://altmanluggage.com/collections/aurora and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://altmanluggage.com/collections/sale, https://altmanluggage.com/pages/help, https://altmanluggage.com/collections/aidan-the-brand, https://altmanluggage.com/collections/aleon, https://altmanluggage.com/collections/american-tourister and https://altmanluggage.com/collections/arlo-skye and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “jQuery is not defined”.

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.

The homepage carries about 988 words of visible text.

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