hellomagazine.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user INP: 217 ms

  217 ms

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

• Tap response (INP) got 22% slower for real visitors

  +22%

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

• Real-user TTFB: 812 ms

  812 ms

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

• About 0.5 g of CO₂ per visit

  0.52 g

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

• 18 links without text

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

• 284 internal links, 13 external

  The homepage links to 284 pages on hellomagazine.com and 13 external pages.

• robots.txt blocks 3 AI answer engine crawlers

  3 of 6

  Your robots.txt shuts out ChatGPT search (OAI-SearchBot), 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.

• No llms.txt

  There is no /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 2 crawlers

  robots.txt blocks 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.

• 1 linked page hidden from search

  /newsletter is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  Elements (1)

• 2 pages share a title

  /us and / all use the title “HELLO! US Edition - Latest news and Photos”. Search engines can't tell which page to show for a search, so each competes with the others.

  Elements (2)

• 1 link to non-canonical URLs

  Your homepage links to 1 page by a URL that isn't its canonical one, for example /, whose canonical is /us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  Elements (1)

• 1 page without an H1

  /subscribe has no <h1> headline, so visitors and search engines get no clear main topic.

• 1 page with very little text

  /subscribe 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.

• 15 internal pages checked

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

• 7 small tap targets

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

• 2 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://accounts.google.com/gsi/style' from origin 'https://www.hellomagazine.com' has bee…”.

• 1 broken external link

  1 link to other sites is dead, for example https://www.snapchat.com/discover/Hello/4038796137 (404).

• 2 redirects before the homepage

  Opening https://hellomagazine.com goes through 2 redirects before the homepage loads.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• No CAA record

  hellomagazine.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

• DNSSEC is off

  hellomagazine.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• No call to action on the first screen

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

• Local business without LocalBusiness data

  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.

  View source

• No phone number on the homepage

  A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

• 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 opening hours

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

• No form on the homepage

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

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• 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,041 words of copy

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

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be hellomagazine.com is still delivered. Reports are on, so moving to quarantine is the next step.

• Email authentication score: 70/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 4 trackers load before any consent

  4

  Before a visitor clicks anything, the page loads Amazon Ads, Comscore, Google Ads 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.

• 11 cookies set on arrival

  11

  Opening the homepage sets 11 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.

• 19 other companies contacted

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