3545indianqueen.com website review

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

About 444 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Google Maps and Google/Doubleclick Ads and others), adding 17.2 MB and 375 ms of main-thread time.

cribflyer-proxy.com costs a phone 0 ms of main-thread work and 15.7 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.

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

Google Tag Manager costs a phone 223 ms of main-thread work and 347 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.

Google Maps costs a phone 148 ms of main-thread work and 507 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.

Amazon Web Services costs a phone 0 ms of main-thread work and 667 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.

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

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

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

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 text “3545 Indian Queen Lane East Falls, Philadelphia, PA 19129”.

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 19.0 MB in 192 requests on a phone: images 15.8 MB (109), scripts 2.5 MB (44) and other files 686 KiB (16). Under 2 MB keeps phones on slow connections fast.

38 images are downloaded at several times the size a phone draws them, for example photo-2000.webp at 1,620 px wide, shown at 362 px. Resized copies would save about 7.1 MB.

7 images weigh 4.7 MB together. On a phone connection a single image that size takes seconds.

40 images further down the page (13.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

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

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

Headings skip levels (h1 → h4, h2 → h5 and h4 → h6), which makes the page harder to scan with a screen reader.

The homepage links to only 2 pages on your own site, so visitors and crawlers find few routes into the rest of it.

8 links have no real href, so search engines can't follow them.

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.

robots.txt blocks GPTBot and CCBot, 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.

https://3545indianqueen.com/tour declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://3545indianqueen.com/tour all use the title “East Falls single family home for sale”. Search engines can't tell which page to show for a search, so each competes with the others.

https://3545indianqueen.com/privacy has no meta description, so Google writes the search snippet from whatever text it finds.

https://3545indianqueen.com/privacy has no <h1> headline, so visitors and search engines get no clear main topic.

https://3545indianqueen.com/tour has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 2 pages linked from your homepage and read each the way a search engine does.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Social proof on the homepage: 12 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage shows no opening hours. If customers visit or call, show when.

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 2,802 words of visible text.

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