ellus.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: 214 ms

  214 ms

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

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

  +11%

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

• Page weight: 4.7 MB

  4.7 MB

  Your homepage downloads 4.7 MB on a phone, 3.9 MB of it images (83%). Under 2 MB keeps phones on slow connections fast.

• 4 images over 500 KB

  4 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.

  Elements (4)

• An image on the first screen is lazy-loaded

  00f5d7a0-3b4b-497f-bd0f-ec56ebfdffb4.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)

• 4 images far larger than shown

  283 KiB

  4 images are downloaded at several times the size a phone draws them, for example nova-colecao-26-primavera-verao-MOB_06.jpg at 1,236 px wide, shown at 390 px. Resized copies would save about 283 KiB.

  Elements (4)

• 1 image below the first screen load straight away

  1 image further down the page (557 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  Elements (1)

• About 1.3 g of CO₂ per visit

  1.32 g

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

• 1 button without a name

  1 button has no accessible name, so screen readers announce just “button”.

  Elements (1)

• 7 tap targets too small

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

• ARIA dialog and alertdialog nodes should have an accessible name (1 element)

  ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• Elements must only use permitted ARIA attributes (1 element)

  Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  Elements (1)

• 6 images without alt text

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

  View source

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

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

  Elements (3)

• 7 form fields without a label

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

  View source

• 3 links without text

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

  Elements (3)

• No H1 headline

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

• No canonical URL

  No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

• No social preview image

  No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is incomplete here.

• 313 internal links, 10 external

  The homepage links to 313 pages on ellus.com and 10 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

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

• 1 page without a title

  /listadedesejos has no <title>, so Google invents the link text in results.

  Elements (1)

• 4 pages without a meta description

  /top-acessorios-sale, /listadedesejos, /new-in and /masculino have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (4)

• 15 pages without an H1

  /top-acessorios-sale, /listadedesejos, /new-in, /masculino/bermudas, /masculino/calcas and /masculino/camisas and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

• 4 pages slow to respond

  /masculino/calcas, /masculino/camisas, /masculino/jaquetas-e-casacos and /masculino/moletons took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• 8 small tap targets

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

• 5 JavaScript errors while loading

  5 errors were logged to the browser console while the page loaded, for example “The source list for the Content Security Policy directive 'default-src' contains an invalid source: '.stackadapt.com'. …”.

• No Referrer-Policy

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

• No security.txt

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

• No CAA record

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

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

• No social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

• Only about 234 words

  The homepage has only about 234 words of visible text; thin pages give Google and first-time buyers little to go on.

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

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

• 1 tracker load before any consent

  1

  Before a visitor clicks anything, the page loads Microsoft Clarity (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.

• 5 cookies set on arrival

  5

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

• 15 other companies contacted

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