35thavesewandvac.com website review

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

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

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

Your mobile performance score is 49. 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 Google CDN and others), adding 2.1 MB and 901 ms of main-thread time.

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

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

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

Google CDN costs a phone 113 ms of main-thread work and 453 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.

Attentive costs a phone 71 ms of main-thread work and 457 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.

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

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

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

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

Your largest element takes 56.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “35th Ave Gift Card Purchase a 35th Ave Gift Card: Amount: $…”.

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

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

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

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

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

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

Your homepage downloads 19.8 MB in 149 requests on a phone: images 16.7 MB (35), scripts 2.2 MB (56) and fonts 597 KiB (15). Under 2 MB keeps phones on slow connections fast.

10 images weigh 11.8 MB together. On a phone connection a single image that size takes seconds.

11 images are downloaded at several times the size a phone draws them, for example ss_11321_4898290_8_20260630161538.png at 1,920 px wide, shown at 390 px. Resized copies would save about 7.3 MB.

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

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

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

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

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.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

The homepage links to 143 pages on 35thavesewandvac.com and 16 external pages.

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://www.35thavesewandvac.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.

robots.txt blocks GPTBot and ClaudeBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

Your homepage links to https://www.35thavesewandvac.com/website-accessibility.htm, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.35thavesewandvac.com/shop/Fabric/Fabric-Theme/Activities.htm, https://www.35thavesewandvac.com/shop/fabric, https://www.35thavesewandvac.com/shop/Fabric/Fabric-Collections.htm, https://www.35thavesewandvac.com/shop/Fabric/FABRIC-THEME.htm, https://www.35thavesewandvac.com/shop/Fabric/FABRIC-MANUFACTURER.htm and https://www.35thavesewandvac.com/shop/Fabric/Precuts.htm have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.35thavesewandvac.com/shop/Fabric/FABRIC-THEME.htm, whose canonical is https://www.35thavesewandvac.com/shop/Fabric/Fabric-Theme.htm. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.35thavesewandvac.com/newsletter.htm, https://www.35thavesewandvac.com/shop/Fabric/Fabric-Theme/Activities.htm, https://www.35thavesewandvac.com/classes---phoenix-location.htm, https://www.35thavesewandvac.com/class-chandler-location.htm, https://www.35thavesewandvac.com/class---el-mirage-location.htm and https://www.35thavesewandvac.com/shop/fabric and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.35thavesewandvac.com/products.htm took over 3 s to send its HTML from our server.

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

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

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.

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

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