Website review, no card needed

elogia.net logo

elogia.net website review

Visit site (opens in a new tab)Reviewed 29 October 202628 issues · 73 checks

This review found 28 issues worth fixing on elogia.net, 14 of them high impact, across 73 checks. The most urgent: reduce unused JavaScript. 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
5.9 s1.8 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.1 s
May 16, 20265.0 s
May 23, 20264.8 s
May 30, 20264.6 s
Jun 6, 20264.5 s
Jun 13, 20264.8 s
Jun 20, 20264.9 s
Jun 27, 20264.9 s
Jul 4, 20265.4 s
Jul 11, 20265.1 s
Jul 18, 20264.9 s
Jul 25, 20264.7 s
Aug 1, 20264.6 s
Aug 8, 20264.7 s
Aug 15, 20264.9 s
Aug 22, 20265.0 s
Aug 29, 20265.1 s
Sep 5, 20265.1 s
Sep 12, 20264.3 s
Sep 19, 20263.8 s
Sep 26, 20263.4 s
Oct 3, 20262.9 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
175 ms103 msMay 9Oct 3147 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026138 ms
May 16, 2026111 ms
May 23, 2026121 ms
May 30, 2026127 ms
Jun 6, 2026125 ms
Jun 13, 2026130 ms
Jun 20, 2026130 ms
Jun 27, 2026136 ms
Jul 4, 2026166 ms
Jul 11, 2026167 ms
Jul 25, 2026129 ms
Aug 8, 2026119 ms
Aug 15, 2026114 ms
Sep 12, 2026111 ms
Sep 19, 2026122 ms
Sep 26, 2026144 ms
Oct 3, 2026147 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 elogia.net (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. elogia.net at 2.1 s2.1 s
  2. elogia.net at 4.2 s4.2 s
  3. elogia.net at 6.3 s6.3 s
  4. elogia.net at 8.4 s8.4 s
  5. elogia.net at 10.5 s10.5 s
  6. elogia.net at 12.5 s12.5 s
  7. elogia.net at 14.6 s14.6 s
  8. elogia.net at 16.7 s16.7 s

Speed

6 to fix51
  • Reduce unused JavaScript

    8.0 s · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.0 s faster on a phone.

  • Main-thread work: 13.1 s

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

  • Mobile performance score: 51

    51/100

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

  • Avoid multiple page redirects

    901 ms

    The page goes through 1 redirect before it starts loading, costing about 901 ms. Link and advertise the final URL directly.

  • Google Tag Manager adds 169 ms

    169 ms

    Google Tag Manager costs a phone 169 ms of main-thread work and 360 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.

  • voiceb.ai adds 1 ms

    1 ms

    voiceb.ai costs a phone 1 ms of main-thread work and 358 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 974 KiB and 215 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 18 KiB

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

  • 14 long tasks on the main thread

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

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

8 to fix100
  • First Contentful Paint: 11.1 s

    11.1 s

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

  • Largest Contentful Paint: 37.8 s

    37.8 s

    Your largest element takes 37.8 s to render on a phone. Google's threshold for “good” is 2.5 s.

  • Speed Index: 17.6 s

    17.6 s

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

  • Time to Interactive: 38.5 s

    38.5 s

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 22 images without width and height

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

  • Total Blocking Time: 242 ms

    242 ms

    Scripts block taps and scrolling for 242 ms in total while the page loads. Good is under 200 ms.

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

    +17%

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

5 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.4 s

    2.4 s

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

  • Real-user CLS: 0.00

    0.00

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

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

    -54%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.1 s to 2.3 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).

Images and page weight

4 to fix25
  • Page weight: 18.7 MB in 116 requests

    18.7 MB

    Your homepage downloads 18.7 MB in 116 requests on a phone: images 15.8 MB (40), scripts 2.8 MB (31) and fonts 65 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    panasonic-featured-D0EiCxA_.jpg weighs 1.4 MB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    682 KiB

    2 images are downloaded at several times the size a phone draws them, for example panasonic-featured-D0EiCxA_.jpg at 1,200 px wide, shown at 342 px. Resized copies would save about 682 KiB.

  • 2 images in older formats

    2 images (1.8 MB) 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 5.3 g of CO₂ per visit

    5.31 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

3 to fixGoogle 9194
  • 24 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 5 buttons without a name

    5 buttons have no accessible name, so screen readers announce just “button”.

2 checks passed
  • Every image has alt text

    All 5 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 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10096
  • No structured data

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

  • 21 internal links, 8 external

    The homepage links to 21 pages on elogia.net and 8 external pages.

7 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “No somos una agencia. Operamos el canal digital completo: marketing, marketplaces, datos y operación conectada. Un solo…”.

  • One H1 headline

    Your main headline reads: “Somos operadoresde negocios digitales”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Elogia · Operadores de negocios digitales · España”.

  • Canonical URL set

    The canonical URL is https://elogia.net/.

  • 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://elogia.net/sitemap.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://elogia.net/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 (852 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix93
  • 3 linked pages hidden from search

    https://elogia.net/politica-de-privacidad, https://elogia.net/marca and https://elogia.net/aviso-legal are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 1 page slow to respond

    https://elogia.net/conocimiento took over 3 s to send its HTML from our server.

  • 13 internal pages checked

    We fetched 13 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 13 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://app.voiceb.ai/api/widget/ed0453d2-31cf-450b-bc8e-31aa202e9548/config' from origin 'https://…”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 22 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 865 words of visible text.

3 checks passed
  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 2 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (measured from a US location before any click).

  • 28 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 elogia.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Tailwind CSS
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on elogia.net, including 14 speed issues, 1 SEO issue and 3 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