anabei.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: 237 ms

  237 ms

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

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

  +25%

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

• Page weight: 4.0 MB

  4.0 MB

  Your homepage downloads 4.0 MB on a phone, 1.0 MB of it images (26%). Under 2 MB keeps phones on slow connections fast.

• 2 images in older formats

  2 images (269 KiB) 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 1.1 g of CO₂ per visit

  1.13 g

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

• Invalid ARIA attributes

  1 element use ARIA attributes their role does not allow, which confuses screen readers.

  Elements (1)

• Scrollable region must have keyboard access (2 elements)

  Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  Elements (2)

• 1 image without alt text

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

  Elements (2)

• 127 form fields without a label

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

  View source

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

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

  Elements (3)

• 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)

• 14 links without text

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

  Elements (3)

• 163 internal links, 25 external

  The homepage links to 163 pages on anabei.com and 25 external pages.

• No Organization structured data

  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.

  View source

• 13 pages without an H1

  /pages/financing, /pages/reviews, /collections/armchairs-ottomans, /collections/sofas-loveseats, /collections/sectionals and /collections/corner-sectionals and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 54 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=187149415&tm=gtm002&Ver=2&mid=178631ae-3be2-4ede-8e60-5f68255d5518&bo=1&sid=2c8532b0daa711f1b419675911e8f8a9&vid=2c856590daa711f18e6871c38d4d9725&vids=1&msclkid=N&pi=9.

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

• Short HSTS lifetime

  HSTS is set, but max-age is 91 days; one year is the recommended minimum.

• 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.

• Domain expires in 5 days

  anabei.com is registered until Nov 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.

• No CAA record

  anabei.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

  anabei.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 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.

• About 2,102 words of copy

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

• Urgency cues

  The page uses urgency cues (a countdown or limited-time wording).

• DMARC is monitor-only (p=none)

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

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

• Email authentication score: 60/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.

• 11 trackers load before any consent

  11

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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.

• 34 cookies set on arrival

  34

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

• 40 other companies contacted

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