1riversidepark.com website review

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

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

The page goes through 1 redirect before it starts loading, costing about 1.2 s. Link and advertise the final URL directly.

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

8 third-party services load with your homepage (Google Tag Manager, posthog.com and JSDelivr CDN and others), adding 1.1 MB and 448 ms of main-thread time.

About 322 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need.

14 KiB JavaScript is shipped twice across bundles.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB could be saved by minifying JavaScript.

Your largest element takes 34.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Photo for One Riverside Park - 50 Riverside Boulevard Condo…”.

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

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

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

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

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 9.0 MB in 110 requests on a phone: images 7.4 MB (14), scripts 1.2 MB (48) and fonts 240 KiB (3). Under 2 MB keeps phones on slow connections fast.

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

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

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

Your title is 113 characters, so Google will cut it off around 60: “One Riverside Park - 50 Riverside Boulevard Condominium in Upper West Side, Manhattan | N…”.

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

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

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

No XML sitemap at https://www.1riversidepark.com/sitemap.xml, so Google discovers your pages only by following links.

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

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

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.1riversidepark.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.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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.

The homepage carries about 1,247 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 6 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 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.