themarkhotel.com website review

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

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

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

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

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

Your mobile performance score is 60 (desktop: 59). Pages that score under 90 lose visitors before the first paint.

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

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

A phone's processor spends 2.1 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

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

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.

Real visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.

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

Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (2.5 s).

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

Real visitors wait 3.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 235 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 2.9 MB in 87 requests on a phone: scripts 1.6 MB (30), images 1.1 MB (25) and fonts 90 KiB (5). Under 2 MB keeps phones on slow connections fast.

6 images (1.1 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.

5 images are downloaded at several times the size a phone draws them, for example IMG_7714-SSedit-1024x635.png at 1,024 px wide, shown at 310 px. Resized copies would save about 284 KiB.

3 images further down the page (399 KiB) 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 0.82 g of CO₂e: 98.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Some list items are not inside a list.

Some lists contain elements other than list items, which screen readers announce wrongly.

2 elements have a tabindex above 0, which scrambles the keyboard order.

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

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

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

The homepage links to 40 pages on themarkhotel.com and 6 external pages.

https://www.themarkhotel.com/information/press is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.themarkhotel.com/the-mark-experience and https://www.themarkhotel.com/the-mark-experience/the-mark-bikes-picnic-by-jean-georges all use the title “Luxury Hotel Exclusive Experiences | The Mark Hotel in NYC”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.themarkhotel.com/the-mark-experience and https://www.themarkhotel.com/the-mark-experience/the-mark-bikes-picnic-by-jean-georges use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.themarkhotel.com/the-mark-experience/the-mark-bikes-picnic-by-jean-georges, whose canonical is https://www.themarkhotel.com/the-mark-experience. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.themarkhotel.com/gallery, https://www.themarkhotel.com/inside-the-mark and https://www.themarkhotel.com/information/press took over 3 s to send their HTML from our server.

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

3 images failed to load on a phone, for example https://www.themarkhotel.com/.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 410 ()”.

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.

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

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