Website review, no card needed

eosenergystorage.com logo

eosenergystorage.com website review

Visit site (opens in a new tab)Reviewed 6 November 202633 issues · 77 checks

This review found 33 issues worth fixing on eosenergystorage.com, 9 of them high impact, across 77 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.1 s1.4 sMay 16Oct 312.8 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20262.0 s
Jun 20, 20262.3 s
Jun 27, 20262.5 s
Jul 4, 20262.7 s
Jul 11, 20262.7 s
Jul 18, 20262.7 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20262.9 s
Sep 5, 20262.8 s
Sep 12, 20262.9 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.8 s
Oct 31, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
93 ms76 msMay 16Oct 3186 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202679 ms
May 23, 202679 ms
May 30, 202678 ms
Jun 6, 202679 ms
Jun 13, 202684 ms
Jun 20, 202681 ms
Jun 27, 202681 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202681 ms
Jul 25, 202684 ms
Aug 1, 202685 ms
Aug 8, 202687 ms
Aug 15, 202688 ms
Aug 22, 202688 ms
Aug 29, 202691 ms
Sep 5, 202687 ms
Sep 12, 202688 ms
Sep 19, 202690 ms
Sep 26, 202687 ms
Oct 3, 202686 ms
Oct 10, 202686 ms
Oct 17, 202685 ms
Oct 24, 202685 ms
Oct 31, 202686 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of eosenergystorage.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eosenergystorage.com at 0.4 s0.4 s
  2. eosenergystorage.com at 0.8 s0.8 s
  3. eosenergystorage.com at 1.1 s1.1 s
  4. eosenergystorage.com at 1.5 s1.5 s
  5. eosenergystorage.com at 1.9 s1.9 s
  6. eosenergystorage.com at 2.3 s2.3 s
  7. eosenergystorage.com at 2.6 s2.6 s
  8. eosenergystorage.com at 3.0 s3.0 s

Speed

4 to fix71
  • Improve image delivery

    2.0 s · 1.2 MB

    6 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

  • Render-blocking requests

    1.2 s

    6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

  • Mobile performance score: 71

    71/100

    Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    300 ms · 102 KiB

    7 files are served with short cache lifetimes, so returning visitors download them again (102 KiB).

  • Reduce unused JavaScript

    280 ms · 116 KiB

    About 116 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 280 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and tradingview-widget.com and others), adding 382 KiB and 327 ms of main-thread time.

  • Reduce unused CSS

    280 ms · 43 KiB

    About 43 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 280 ms faster on a phone.

  • 3 long tasks on the main thread

    3 long tasks block the main thread while loading, the longest for 100 ms. During a long task the page ignores taps.

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

2 checks passed
  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 413 ms of it running JavaScript. That is comfortably low.

  • Server response: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix67
  • Fails Core Web Vitals for real visitors

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

  • Real-user TTFB: 2.2 s

    2.2 s

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

  • Largest Contentful Paint: 5.9 s

    5.9 s

    Your largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Real-user LCP: 3.1 s

    3.1 s

    Real visitors wait 3.1 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-31, 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.7 s

    2.7 s

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

  • Time to Interactive: 5.9 s

    5.9 s

    The page becomes fully interactive after 5.9 s. Good is under 3.8 s.

  • Speed Index: 4.0 s

    4.0 s

    Visually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 s.

  • Cumulative Layout Shift: 0.127

    0.127

    The layout shifts by 0.127 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

  • 9 images without width and height

    9 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +8%

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

3 checks passed
  • Real-user INP: 87 ms

    87 ms

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

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Total Blocking Time: 56 ms

    56 ms

    Scripts block the page for only 56 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix68
  • Page weight: 2.7 MB in 59 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 59 requests on a phone: images 2.0 MB (12), scripts 481 KiB (33) and fonts 166 KiB (3). 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.

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

  • About 0.8 g of CO₂ per visit

    0.77 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 8792
  • Invalid ARIA attributes

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

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

  • 4 tap targets too small

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

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

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 6 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9288
  • 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.

  • No social preview image

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

  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 81 internal links, 13 external

    The homepage links to 81 pages on eosenergystorage.com and 13 external pages.

6 checks passed
  • Meta description: 124 characters

    Your meta description is 124 characters: “Eos is accelerating the shift to clean energy with positively ingenious solutions that transform how the world stores p…”.

  • One H1 headline

    Your main headline reads: “Home”.

  • Canonical URL set

    The canonical URL is https://www.eose.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.eose.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://www.eose.com/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.

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (580 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 15 pages without a meta description

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

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9287
  • 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/09a21798-7b2f-4496-9000-19845e333d8f' violates the following Content …”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “Learn more”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Contact Us”, “Learn more” and “Submit a request”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 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.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at eosenergystorage.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
Fastly

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on eosenergystorage.com, including 15 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25