Website review, no card needed

eecoonline.com logo

eecoonline.com website review

Visit site (opens in a new tab)Reviewed 2 November 202638 issues · 65 checks

This review found 38 issues worth fixing on eecoonline.com, 12 of them high impact, across 65 checks. The most urgent: fails Core Web Vitals for real visitors. 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
4.1 s2.8 sMay 16Oct 313.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.8 s
May 23, 20263.8 s
May 30, 20263.9 s
Jun 6, 20264.0 s
Jun 13, 20264.0 s
Jun 20, 20264.0 s
Jun 27, 20264.0 s
Jul 4, 20263.9 s
Jul 11, 20263.8 s
Jul 18, 20263.9 s
Jul 25, 20263.9 s
Aug 1, 20263.9 s
Aug 8, 20263.9 s
Aug 15, 20263.8 s
Aug 22, 20263.8 s
Aug 29, 20263.8 s
Sep 5, 20263.8 s
Sep 12, 20263.8 s
Sep 19, 20263.8 s
Sep 26, 20263.6 s
Oct 3, 20263.5 s
Oct 10, 20263.2 s
Oct 17, 20263.0 s
Oct 24, 20263.0 s
Oct 31, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
97 ms77 msMay 16Oct 3180 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202688 ms
May 23, 202693 ms
May 30, 202694 ms
Jun 6, 202695 ms
Jun 13, 202691 ms
Jun 20, 202688 ms
Jun 27, 202689 ms
Jul 4, 202688 ms
Jul 11, 202690 ms
Jul 18, 202690 ms
Jul 25, 202690 ms
Aug 1, 202694 ms
Aug 8, 202691 ms
Aug 15, 202688 ms
Aug 22, 202693 ms
Aug 29, 202688 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202682 ms
Sep 26, 202679 ms
Oct 3, 202683 ms
Oct 10, 202682 ms
Oct 17, 202685 ms
Oct 24, 202683 ms
Oct 31, 202680 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 eecoonline.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

100
3 checks passed
  • Mobile performance score: 100

    100/100

    Your mobile performance score is 100. That is in Google's “good” band (90 and up).

  • Main-thread work: 0.0 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

4 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 LCP: 3.0 s

    3.0 s

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

10 checks passed
  • Real-user INP: 80 ms

    80 ms

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

  • Real-user CLS: 0.09

    0.09

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

  • Tap response (INP) got 10% faster for real visitors

    -10%

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

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

    -23%

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

  • Cumulative Layout Shift: 0

    0

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

  • First Contentful Paint: 0.8 s

    0.8 s

    The first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 0.8 s

    0.8 s

    Your largest element renders in 0.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “You don't have permissions to access this page. Please come…”.

  • Speed Index: 0.8 s

    0.8 s

    Visually, the page fills in at 0.8 s (Speed Index), inside the 3.4 s “good” threshold.

  • Total Blocking Time: 0 ms

    0 ms

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

  • Time to Interactive: 0.8 s

    0.8 s

    The page is fully interactive after 0.8 s.

Images and page weight

1 to fix90
  • 1 image far larger than shown

    29 KiB

    1 image is downloaded at several times the size a phone draws it, for example 63585a0d2d57e111680750-podcast-breakout-2x.png at 1,050 px wide, shown at 304 px. Resized copies would save about 29 KiB.

  • 1 image in older formats

    1 image (118 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.

  • 1 image below the first screen load straight away

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

  • About 0.00 g of CO₂ per visit

    0.00 g

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

1 checks passed
  • Page weight: 2 KiB in 1 request

    2 KiB

    Your homepage downloads 2 KiB in 1 request on a phone: HTML 2 KiB (1). That is a lean page.

Accessibility

9 to fixGoogle 10090
  • 8 text elements with low contrast

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

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

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

  • Heading levels should only increase by one (2 elements)

    Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 5 links without text

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

  • 1 form field without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

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

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

12 to fixGoogle 4530
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

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

  • No H1 headline

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

  • Blocked from indexing

    Google's crawler is blocked from indexing this page.

  • Error status code

    The page answers with an error status, so search engines may drop it.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 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 XML sitemap

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

  • No robots.txt

    There is no robots.txt at eecoonline.com/robots.txt, the first file search crawlers ask for.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

AI search readiness

2 to fix42
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 955 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://eecoonline.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.

Best practices

5 to fixGoogle 9653
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 7 small tap targets

    7 of 25 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 “The Content-Security-Policy directive name 'Content-Security-Policy:' contains one or more invalid characters. Only ASC…”.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • No character set

    No character set is declared, so some characters can render as gibberish.

Content and conversion

4 to fix40
  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 955 words of visible text.

1 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start Searching” and “Register >”.

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.

  • 13 cookies set on arrival

    13

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 eecoonline.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on eecoonline.com, including 4 speed issues, 12 SEO issues and 4 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