landryandarcari.com website review

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

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

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

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

Shopify costs a phone 184 ms of main-thread work and 5.1 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 695 KiB of JavaScript is downloaded but never used on this page.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).

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

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

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

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

Klaviyo costs a phone 104 ms of main-thread work and 318 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.

2 KiB could be saved by minifying JavaScript.

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

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

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 24.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “New Arrival Rugs”.

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

The layout shifts by 0.653 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Real visitors wait 296 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-11-07, real Chrome visitors' tap response (inp) went from 169 ms to 305 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

5 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' largest content (lcp) went from 2.6 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.0 MB in 419 requests on a phone: images 8.6 MB (98), scripts 2.1 MB (119) and other files 959 KiB (141). Under 2 MB keeps phones on slow connections fast.

5 images weigh 9.7 MB together. On a phone connection a single image that size takes seconds.

8 images are downloaded at several times the size a phone draws them, for example homepage_banner_-_ombre_turkmen_-_mobile_-_WEBP.webp at 2,744 px wide, shown at 390 px. Resized copies would save about 7.7 MB.

16 images (10.3 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.

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Elements with visible text labels do not have matching accessible names. (2 elements).

Your title is 74 characters, so Google will cut it off around 60: “Oriental Rugs & Carpet in New England – Landry & Arcari Rugs and Carpeting”.

There are 2 <h1> headlines (“” and “”). One clear main headline is easier for people and search engines.

5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 500 pages on landryandarcari.com and 7 external pages.

https://www.landryandarcari.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.landryandarcari.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.landryandarcari.com/customer_authentication/redirect and https://www.landryandarcari.com/pages/all-rug-collections have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.landryandarcari.com/collections/all-rugs, https://www.landryandarcari.com/collections/all-carpet, https://www.landryandarcari.com/customer_authentication/redirect, https://www.landryandarcari.com/pages/all-rug-collections, https://www.landryandarcari.com/collections/abstract-rugs and https://www.landryandarcari.com/collections/agra-rugs and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.landryandarcari.com/pages/all-rug-collections took over 3 s to send its HTML from our server.

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

7 of 28 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 “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

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.

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

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.

The homepage carries about 755 words of visible text.

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

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