Website review, no card needed

acciona.com logo

acciona.com website review

Visit site (opens in a new tab)Reviewed 18 October 202638 issues · 75 checks

This review found 38 issues worth fixing on acciona.com, 16 of them high impact, across 75 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
4.5 s3.6 sApr 25Oct 104.1 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20263.7 s
May 2, 20263.7 s
May 9, 20263.8 s
May 16, 20263.9 s
May 23, 20264.0 s
May 30, 20264.1 s
Jun 6, 20264.2 s
Jun 13, 20264.2 s
Jun 20, 20264.3 s
Jun 27, 20264.2 s
Jul 4, 20264.2 s
Jul 11, 20264.2 s
Jul 18, 20264.1 s
Jul 25, 20264.2 s
Aug 1, 20264.2 s
Aug 8, 20264.3 s
Aug 15, 20264.4 s
Aug 22, 20264.4 s
Aug 29, 20264.4 s
Sep 5, 20264.3 s
Sep 12, 20264.2 s
Sep 19, 20264.1 s
Sep 26, 20264.1 s
Oct 3, 20264.1 s
Oct 10, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
500 ms274 msApr 25Oct 10474 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026300 ms
May 2, 2026311 ms
May 9, 2026323 ms
May 16, 2026358 ms
May 23, 2026398 ms
May 30, 2026412 ms
Jun 6, 2026411 ms
Jun 13, 2026411 ms
Jun 20, 2026412 ms
Jun 27, 2026411 ms
Jul 4, 2026412 ms
Jul 11, 2026409 ms
Jul 18, 2026412 ms
Jul 25, 2026422 ms
Aug 1, 2026427 ms
Aug 8, 2026435 ms
Aug 15, 2026427 ms
Aug 22, 2026409 ms
Aug 29, 2026409 ms
Sep 5, 2026410 ms
Sep 12, 2026413 ms
Sep 19, 2026429 ms
Sep 26, 2026437 ms
Oct 3, 2026454 ms
Oct 10, 2026474 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 acciona.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. acciona.com at 1.2 s1.2 s
  2. acciona.com at 2.5 s2.5 s
  3. acciona.com at 3.7 s3.7 s
  4. acciona.com at 4.9 s4.9 s
  5. acciona.com at 6.1 s6.1 s
  6. acciona.com at 7.4 s7.4 s
  7. acciona.com at 8.6 s8.6 s
  8. acciona.com at 9.8 s9.8 s

Speed

11 to fix28
  • Reduce unused JavaScript

    1.1 s · 3.1 MB

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

  • Mobile performance score: 28

    28/100

    Your mobile performance score is 28 (desktop: 68). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Use efficient cache lifetimes

    150 ms · 20.5 MB

    25 files are served with short cache lifetimes, so returning visitors download them again (20.5 MB).

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google CDN, bmeinntech.es and Other Google APIs/SDKs and others), adding 7.4 MB and 198 ms of main-thread time.

  • bmeinntech.es adds 66 ms

    66 ms

    bmeinntech.es costs a phone 66 ms of main-thread work and 7.0 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.

  • Font display

    700 ms

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

  • 4 long tasks on the main thread

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

  • Render-blocking requests

    300 ms

    2 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.

  • Main-thread work: 2.9 s

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

  • 2,799 HTML elements

    The page has 2,799 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Google CDN adds 92 ms

    92 ms

    Google CDN costs a phone 92 ms of main-thread work and 383 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.

  • Reduce unused CSS

    150 ms · 59 KiB

    About 59 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.

  • Phones get a much slower page than desktops

    Desktop scores 68 but mobile only 28. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 85 ms

    85 ms

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

Core Web Vitals

13 to fix0
  • 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: 5.1 s

    5.1 s

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

  • Real-user CLS: 1.03

    1.03

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

  • Real-user FCP: 4.0 s

    4.0 s

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

  • Real-user TTFB: 2.5 s

    2.5 s

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

  • Largest Contentful Paint: 35.4 s

    35.4 s

    Your largest element takes 35.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our goal is to lead the transition towards a low-carbon eco…”.

  • Time to Interactive: 62.1 s

    62.1 s

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

  • Cumulative Layout Shift: 1

    1

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Speed Index: 5.9 s

    5.9 s

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

  • Real-user INP: 349 ms

    349 ms

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

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

    +52%

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

  • Total Blocking Time: 348 ms

    348 ms

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

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

    +11%

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

Images and page weight

1 to fix33
  • Page weight: 23.9 MB in 42 requests

    23.9 MB

    Your homepage downloads 23.9 MB in 42 requests on a phone: images 12.2 MB (15), scripts 7.2 MB (5) and media 3.8 MB (1). Under 2 MB keeps phones on slow connections fast.

  • About 6.8 g of CO₂ per visit

    6.77 g

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

Accessibility

5 to fix84
  • 5 buttons without a name

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

  • Invalid ARIA attributes

    4 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • 12 tap targets too small

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (2 elements).

  • 1 form field without a label

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

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (7 elements).

SEO

2 to fixGoogle 10089
  • Title is short (29 characters)

    Your title is only 29 characters: “ACCIONA | Business as unusual”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 12 internal links, 1 external

    The homepage links to 12 pages on acciona.com and 1 external page.

6 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “At ACCIONA we offer sustainable solutions to the most urgent challenges facing the planet, such as global warming, ener…”.

  • One H1 headline

    Your main headline reads: “ACCIONA | BUSINESS AS UNUSUAL”.

  • Canonical URL set

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

  • 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.acciona.com/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.

3 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 (2,185 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.acciona.com/llms.txt (40 KiB, 242 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 1 page without a meta description

    https://www.acciona.com/privacy-policy/exercise-of-personal-data-rights has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.acciona.com/privacy-policy/exercise-of-personal-data-rights has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.acciona.com/our-purpose/work-with-us/job-offers has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 11 internal pages checked

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

5 checks passed
  • Linked pages load

    All 11 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 11 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 456 words of visible text.

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “CONTACT”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

Privacy and tracking

  • 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). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies, 1 of them by other companies (measured from a US location before any click).

  • 11 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 acciona.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Company

Employees
57,843
Founded
1997
Headquarters
Alcobendas

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 acciona.com, including 24 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