newyorker.com website review

Not measured in this review.

• Tap response (INP) held steady for real visitors

  +2%

  Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 176 ms to 176 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Largest content (LCP) held steady for real visitors

  +9%

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

• Page weight: 8.1 MB

  8.1 MB

  Your homepage downloads 8.1 MB on a phone, 1.5 MB of it images (19%). Under 2 MB keeps phones on slow connections fast.

• 1 image over 500 KB

  Final_GIF_NewYorker_ani.gif weighs 1.2 MB. On a phone connection a single image that size takes seconds.

  Elements (1)

• 2 images in older formats

  2 images (1.3 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.

  Elements (2)

• About 2.3 g of CO₂ per visit

  2.28 g

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

• Interactive controls must not be nested (6 elements)

  Interactive controls must not be nested: 6 elements on the page fail this check, rated serious by axe-core.

  Elements (3)

• 3 text elements with low contrast

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

  Elements (3)

• All page content should be contained by landmarks (2 elements)

  All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  Elements (2)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

  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.

  Elements (1)

• Page should contain a level-one heading (1 element)

  Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 4 links without text

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

  Elements (3)

• Headings skip levels

  Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

  View source

• Title is short (14 characters)

  Your title is only 14 characters: “The New Yorker”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

• 126 internal links, 18 external

  The homepage links to 126 pages on newyorker.com and 18 external pages.

• robots.txt blocks 4 AI answer engine crawlers

  4 of 6

  Your robots.txt shuts out Claude search (Claude-SearchBot), Claude (Claude-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

• Organization data is thin (3 of 6 facts)

  Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  View source

• No llms.txt

  There is no https://www.newyorker.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.

• Opted out of AI training for 4 crawlers

  robots.txt blocks ClaudeBot, Google-Extended, Applebot-Extended 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.

• 15 internal pages checked

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

• 2 broken images

  2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=4015762&tm=gtm002&Ver=2&mid=4bbb78eb-6939-4c60-920c-dc2a0fc10c62&bo=1&sid=635647a0c5e011f19ff82b985301df12&vid=6356a630c5e011f1a95495d99e2f4d1d&vids=1&msclkid=N&pi=918.

• 4 small tap targets

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

• 6 JavaScript errors while loading

  6 errors were logged to the browser console while the page loaded, for example “Error setting performance measure: SyntaxError: Failed to execute 'measure' on 'Performance': The mark 'gb-script-end' …”.

• Thin social proof

  Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

• No analytics detected

  No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

• No direct contact details

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

• No form on the homepage

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

• No risk reducer

  No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

• About 2,277 words of copy

  The homepage carries about 2,277 words of visible text.

• 11 trackers load before any consent

  11

  Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Criteo, Google Ads and Google Tag Manager and 6 mores (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.

• 51 cookies set on arrival

  51

  Opening the homepage sets 51 cookies (measured from a US location before any click).

• No consent tool detected

  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.

• 86 other companies contacted

  Loading the homepage contacts 86 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.