eose.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 TTFB: 2.1 s

  2.1 s

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

• Real-user LCP: 2.8 s

  2.8 s

  Real visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

  +74%

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

• Real-user FCP: 2.5 s

  2.5 s

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

• Tap response (INP) held steady for real visitors

  +4%

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

• Page weight: 2.6 MB

  2.6 MB

  Your homepage downloads 2.6 MB on a phone, 2.0 MB of it images (76%). Under 2 MB keeps phones on slow connections fast.

• 1 image far larger than shown

  248 KiB

  1 image is downloaded at several times the size a phone draws it, for example eos_whitepaper_AI_banner.jpg.webp at 1,920 px wide, shown at 282 px. Resized copies would save about 248 KiB.

  Elements (1)

• 2 images below the first screen load straight away

  2 images further down the page (347 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (2)

• About 0.7 g of CO₂ per visit

  0.74 g

  By the Sustainable Web Design model, a visit to your homepage emits about 0.74 g of CO₂e: 88.5 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)

• 9 text elements with low contrast

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

  Elements (3)

• 4 tap targets too small

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

  Elements (3)

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

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

  Elements (3)

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

• Headings skip levels

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

  View sourceElements (1)

• Title is short (29 characters)

  Your title is only 29 characters: “Home - Eos Energy Enterprises”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• No social preview image

  No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  View source

• 81 internal links, 13 external

  The homepage links to 81 pages on eose.com and 13 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.

• 15 pages without a meta description

  /technology, /technology/manufacturing, /technology/rd, /technology/patents, /solutions and /solutions/eos-indensity and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (8)

• 15 internal pages checked

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

• 13 small tap targets

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

• 3 JavaScript errors while loading

  3 errors were logged to the browser console while the page loaded, for example “Creating a worker from 'blob:https://www.eose.com/432f752d-31a6-41d8-a41f-e3a90089b17f' violates the following Content …”.

• Short HSTS lifetime

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

• No security.txt

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

• Domain expires in 19 days

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

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

  eose.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 social proof

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

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

  The homepage carries about 598 words of visible text.

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

• 2 trackers load before any consent

  2

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

• 3 cookies set on arrival

  3

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

• 14 other companies contacted

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