Website review, no card needed

energybox.com logo

energybox.com website review

Visit site (opens in a new tab)Reviewed 21 October 202631 issues · 75 checks

This review found 31 issues worth fixing on energybox.com, 9 of them high impact, across 75 checks. The most urgent: render-blocking requests. 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

Full-page screenshot of energybox.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. energybox.com at 0.7 s0.7 s
  2. energybox.com at 1.4 s1.4 s
  3. energybox.com at 2.2 s2.2 s
  4. energybox.com at 2.9 s2.9 s
  5. energybox.com at 3.6 s3.6 s
  6. energybox.com at 4.3 s4.3 s
  7. energybox.com at 5.0 s5.0 s
  8. energybox.com at 5.8 s5.8 s

Speed

10 to fix53
  • Render-blocking requests

    5.4 s

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

  • Reduce unused JavaScript

    3.9 s · 1,007 KiB

    About 1,007 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.

  • Improve image delivery

    850 ms · 1.1 MB

    11 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, wpenginepowered.com and Google Tag Manager and others), adding 2.8 MB and 1.1 s of main-thread time.

  • Mobile performance score: 53

    53/100

    Your mobile performance score is 53 (desktop: 67). Pages that score under 90 lose visitors before the first paint.

  • Reduce unused CSS

    770 ms · 184 KiB

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

  • wpenginepowered.com adds 397 ms

    397 ms

    wpenginepowered.com costs a phone 397 ms of main-thread work and 1.5 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Google CDN adds 407 ms

    407 ms

    Google CDN costs a phone 407 ms of main-thread work and 733 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Main-thread work: 3.5 s

    A phone's processor spends 3.5 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Google Tag Manager adds 200 ms

    200 ms

    Google Tag Manager costs a phone 200 ms of main-thread work and 298 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • 12 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

  • Use efficient cache lifetimes

    8 KiB

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

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

5 to fix64
  • First Contentful Paint: 10.8 s

    10.8 s

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

  • Largest Contentful Paint: 30.1 s

    30.1 s

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

  • Time to Interactive: 31.1 s

    31.1 s

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

  • Speed Index: 13.6 s

    13.6 s

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

  • 12 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Total Blocking Time: 165 ms

    165 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix53
  • Page weight: 7.4 MB in 176 requests

    7.4 MB

    Your homepage downloads 7.4 MB in 176 requests on a phone: images 4.8 MB (23), scripts 1.5 MB (75) and fonts 393 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 5 images below the first screen load straight away

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

  • 3 images far larger than shown

    123 KiB

    3 images are downloaded at several times the size a phone draws them, for example NoPath-Copy-6-1.png at 370 px wide, shown at 100 px. Resized copies would save about 123 KiB.

  • 2 images in older formats

    2 images (85 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.

  • About 2.1 g of CO₂ per visit

    2.09 g

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

Accessibility

4 to fixGoogle 9295
  • 3 text elements with low contrast

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

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

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 41 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

2 to fixGoogle 9283
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (16 characters)

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

  • 105 internal links, 5 external

    The homepage links to 105 pages on energybox.com and 5 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “AI-Driven Monitoring & Automation for Multi-Site Facilities”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.energybox.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.energybox.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 (968 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 14 pages without a meta description

    https://www.energybox.com/solution, https://www.energybox.com/automation, https://www.energybox.com/monitoring, https://www.energybox.com/platform, https://www.energybox.com/mobile-apps and https://www.energybox.com/customer and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.energybox.com/solution, https://www.energybox.com/automation, https://www.energybox.com/monitoring, https://www.energybox.com/platform, https://www.energybox.com/mobile-apps and https://www.energybox.com/customer and 9 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 28 found) and read each the way a search engine does.

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

  • 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

1 to fixGoogle 9693
  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Swiper is not defined”.

2 checks passed
  • Tap targets are thumb-sized

    8 of 8 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Only about 193 words

    The homepage has only about 193 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.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SCHEDULE A DEMO” and “BOOK A FREE ROI ASSESSMENT”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Schedule a Demo”, “Book a Free ROI Assessment” and “Learn More”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 25 testimonial or review blocks and 1 customer or partner logo.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 cookies, 1 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.

  • 12 other companies contacted

    Loading the homepage contacts 12 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 energybox.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 Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on energybox.com, including 15 speed issues, 2 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