121w27.com website review

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

6 images could be 938 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

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

5 third-party services load with your homepage (Squarespace, Google Maps and sqspcdn.com and others), adding 3.0 MB and 523 ms of main-thread time.

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

Squarespace costs a phone 397 ms of main-thread work and 1,017 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 62 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.3 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.

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

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 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “121 West 27th Street”.

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

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

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

1 image 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 3.0 MB in 78 requests on a phone: scripts 1.4 MB (49), images 1.4 MB (9) and stylesheets 171 KiB (11). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (132 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

1 image has no alt text, which hurts accessibility and image search.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 20 characters: “121 West 27th Street”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/60c3783e9b65137aa7c…”.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 34 pages on 121w27.com and 1 external page.

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.121w27.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.

Your homepage links to https://www.121w27.com/10th-floor-6750-sf and https://www.121w27.com/suite-404-1884-sf, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.121w27.com/home 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://www.121w27.com/home all use the title “121 West 27th Street”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.121w27.com/photos, https://www.121w27.com/suite-1102-sf-2450, https://www.121w27.com/suite-1001-sf-2480-1, https://www.121w27.com/suite-8011842-sf, https://www.121w27.com/suite-802-1728-sf-1 and https://www.121w27.com/suite303-1223sf-1 and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.121w27.com/photos, https://www.121w27.com/suite-1102-sf-2450, https://www.121w27.com/suite-1001-sf-2480-1, https://www.121w27.com/suite-8011842-sf, https://www.121w27.com/suite-802-1728-sf-1 and https://www.121w27.com/suite303-1223sf-1 and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.121w27.com/photos, https://www.121w27.com/suite-1102-sf-2450, https://www.121w27.com/suite-802-1728-sf-1, https://www.121w27.com/contact, https://www.121w27.com/Availabilities and https://www.121w27.com/home have 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 11 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/63ec29707597522082c65d5f/20/5c5a…”.

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.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 199 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

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.

Opening the homepage sets 3 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.