ebinnewyork.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: 235 ms

  235 ms

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

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

  +39%

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

• Largest content (LCP) got 23% slower for real visitors

  +23%

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

• Real-user FCP: 2.1 s

  2.1 s

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

• Page weight: 3.1 MB

  3.1 MB

  Your homepage downloads 3.1 MB on a phone, 427 KiB of it images (13%). Under 2 MB keeps phones on slow connections fast.

• An image on the first screen is lazy-loaded

  Edge_Control_Spray_MB.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  Elements (2)

• 1 image in older formats

  1 image (73 KiB) is 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 (1)

• About 0.9 g of CO₂ per visit

  0.88 g

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

• 10 tap targets too small

  10 tap targets are too small or too close together to hit reliably with a finger.

  Elements (3)

• 5 text elements with low contrast

  5 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 (14 elements)

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

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

• 2 form fields without a label

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

  View source

• 1 link without text

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

  Elements (1)

• Alternative text of images should not be repeated as text (6 elements)

  Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.

  Elements (3)

• Headings should not be empty (1 element)

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

  Elements (1)

• Headings skip levels

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

  View sourceElements (1)

• No H1 headline

  There is no <h1>, so neither visitors nor Google get a clear main headline.

• Title is short (13 characters)

  Your title is only 13 characters: “EBIN NEW YORK”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• Meta description is long (198 characters)

  Your meta description is 198 characters; Google truncates after about 160, so the end of your pitch is cut.

  View source

• No XML sitemap

  No XML sitemap at https://www.ebinnewyork.com/sitemap.xml, so Google discovers your pages only by following links.

• 242 internal links, 7 external

  The homepage links to 242 pages on ebinnewyork.com and 7 external pages.

• 1 linked page is broken

  Your homepage links to /collections/setting-lotions, which answers with an error. Visitors hit a dead end and search engines drop it.

  Elements (1)

• 7 pages without a meta description

  /collections/shop-all, /collections/wonder-curl-bond, /collections/melt, /collections/heat-protectant, /collections/styling-tools and /collections/wig-cares and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (7)

• 1 page without an H1

  /collections/wonder-weave-bond has 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 97 found) and read each the way a search engine does.

• 6 JavaScript errors while loading

  6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

• 3 broken links to your own pages

  3 links from your homepage to your own site are broken, for example https://www.ebinnewyork.com/collections/melt (503).

• 1 broken external link

  1 link to other sites is dead, for example https://ebinny.aftership.com/ (404).

• Short HSTS lifetime

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

• 1 link through redirect chains

  1 link go through two or more redirects, for example https://instagram.com/ebin_newyork.

• 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

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

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

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

• Thin social proof

  Social proof on the homepage: 83 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

• No opening hours

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

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

  The homepage carries about 776 words of visible text.

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be ebinnewyork.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.

• 7 trackers load before any consent

  7

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

• 28 cookies set on arrival

  28

  Opening the homepage sets 28 cookies, 2 of them by other companies (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.

• 55 other companies contacted

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