Website review, no card needed

ormazabal.com logo

ormazabal.com website review

Visit site (opens in a new tab)Reviewed 27 October 202642 issues · 80 checks

This review found 42 issues worth fixing on ormazabal.com, 19 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. 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.4 s2.9 sMay 9Oct 245.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.2 s
May 23, 20263.2 s
May 30, 20263.2 s
Jun 6, 20263.3 s
Jun 13, 20263.8 s
Jun 20, 20264.0 s
Jun 27, 20264.3 s
Jul 4, 20264.5 s
Jul 11, 20264.3 s
Jul 18, 20264.5 s
Jul 25, 20264.5 s
Aug 1, 20264.5 s
Aug 8, 20264.5 s
Aug 15, 20264.7 s
Aug 22, 20264.8 s
Aug 29, 20265.0 s
Sep 5, 20265.1 s
Sep 12, 20264.9 s
Sep 19, 20265.0 s
Sep 26, 20264.9 s
Oct 3, 20264.9 s
Oct 10, 20265.1 s
Oct 17, 20265.1 s
Oct 24, 20265.0 s
Real-visitor tap response (INP)75th percentile, phones
121 ms102 msMay 9Oct 24118 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026111 ms
May 16, 2026111 ms
May 23, 2026109 ms
May 30, 2026109 ms
Jun 6, 2026105 ms
Jun 13, 2026106 ms
Jun 20, 2026106 ms
Jun 27, 2026106 ms
Jul 4, 2026110 ms
Jul 11, 2026109 ms
Jul 18, 2026109 ms
Jul 25, 2026109 ms
Aug 1, 2026108 ms
Aug 8, 2026109 ms
Aug 15, 2026109 ms
Aug 22, 2026105 ms
Aug 29, 2026104 ms
Sep 5, 2026104 ms
Sep 12, 2026104 ms
Sep 19, 2026107 ms
Sep 26, 2026110 ms
Oct 3, 2026112 ms
Oct 10, 2026113 ms
Oct 17, 2026119 ms
Oct 24, 2026118 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 ormazabal.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ormazabal.com at 1.0 s1.0 s
  2. ormazabal.com at 2.1 s2.1 s
  3. ormazabal.com at 3.1 s3.1 s
  4. ormazabal.com at 4.1 s4.1 s
  5. ormazabal.com at 5.2 s5.2 s
  6. ormazabal.com at 6.2 s6.2 s
  7. ormazabal.com at 7.2 s7.2 s
  8. ormazabal.com at 8.3 s8.3 s

Speed

11 to fix51
  • Use efficient cache lifetimes

    2.7 s · 5.4 MB

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

  • Improve image delivery

    1.2 s · 4.4 MB

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

  • Render-blocking requests

    2.5 s

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

  • Reduce unused JavaScript

    1.2 s · 586 KiB

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

  • 8 third-party services on the page

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

  • Mobile performance score: 51

    51/100

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

  • Reduce unused CSS

    750 ms · 100 KiB

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

  • Font display

    600 ms

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

  • Google CDN adds 473 ms

    473 ms

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

  • Google Tag Manager adds 396 ms

    396 ms

    Google Tag Manager costs a phone 396 ms of main-thread work and 437 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.0 s

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

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    10 KiB

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

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

1 checks passed
  • Server response: 100 ms

    100 ms

    Your server sent the HTML in 100 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 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 FCP: 4.1 s

    4.1 s

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

  • Real-user TTFB: 1.9 s

    1.9 s

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

  • Time to Interactive: 28.3 s

    28.3 s

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

  • Largest Contentful Paint: 8.6 s

    8.6 s

    Your largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SF6 – free Completamos nuestra gama de productos libres de …”. Most of its time is resource load delay (5.5 s).

  • Speed Index: 15.2 s

    15.2 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

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

    +55%

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

  • Total Blocking Time: 397 ms

    397 ms

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

  • 7 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

3 checks passed
  • Real-user INP: 121 ms

    121 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

1 to fix70
  • Page weight: 7.1 MB in 151 requests

    7.1 MB

    Your homepage downloads 7.1 MB in 151 requests on a phone: images 5.0 MB (36), scripts 1.5 MB (69) and other files 362 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

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

  • About 2.0 g of CO₂ per visit

    2.01 g

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

2 checks passed
  • Images load when needed

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 8592
  • Unlabelled dropdowns

    1 dropdown has no label.

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

  • 5 tap targets too small

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

  • 7 links without text

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

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 21 images in the HTML carry an alt attribute.

  • 46 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: 46 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9286
  • Title is short (9 characters)

    Your title is only 9 characters: “Ormazabal”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 3 H1 headlines

    There are 3 <h1> headlines (“SF6 – free”, “Technology for a new electric world” and “Data Center”). One clear main headline is easier for people and search engines.

  • 8 links crawlers can't follow

    8 links have no real href, so search engines can't follow them.

  • 136 internal links, 14 external

    The homepage links to 136 pages on ormazabal.com and 14 external pages.

6 checks passed
  • Meta description: 141 characters

    Your meta description is 141 characters: “Desarrollamos soluciones eléctricas personalizadas y de alta tecnología para todo tipo de aplicaciones ¡Te ayudamos a e…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: 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.ormazabal.com/sitemap_index.xml.

AI search readiness

100
4 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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.ormazabal.com/llms.txt (28 KiB, 127 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

4 to fix75
  • 9 linked pages hidden from search

    https://www.ormazabal.com/blog, https://www.ormazabal.com/casos-de-exito, https://www.ormazabal.com/celdas-de-distribucion-primaria, https://www.ormazabal.com/celdas-de-distribucion-secundaria, https://www.ormazabal.com/transformadores and https://www.ormazabal.com/cuadros-de-baja-tension and 3 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 16 pages share a title

    /, https://www.ormazabal.com/blog, https://www.ormazabal.com/landing/landing-sf6-free-es, https://www.ormazabal.com/solution/smart-digital-grids-2, https://www.ormazabal.com/solution/green-generation-storage-2 and https://www.ormazabal.com/solution/green-mobility-2 and 10 others all use the title “Ormazabal”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 10 pages without a meta description

    https://www.ormazabal.com/blog, https://www.ormazabal.com/landing/landing-sf6-free-es, https://www.ormazabal.com/casos-de-exito, https://www.ormazabal.com/celdas-de-distribucion-primaria, https://www.ormazabal.com/celdas-de-distribucion-secundaria and https://www.ormazabal.com/transformadores and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.ormazabal.com/blog, https://www.ormazabal.com/landing/landing-sf6-free-es and https://www.ormazabal.com/casos-de-exito have no <h1> headline, so visitors and search engines get no clear main topic.

  • 12 pages slow to respond

    https://www.ormazabal.com/blog, https://www.ormazabal.com/landing/landing-sf6-free-es, https://www.ormazabal.com/solution/green-generation-storage-2, https://www.ormazabal.com/solution/green-mobility-2, https://www.ormazabal.com/solution/sustainable-buildings-infrastructures-5 and https://www.ormazabal.com/landing/data-center and 6 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 6 small tap targets

    6 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • A 8-field form

    Your longest form asks for 8 fields (8 required). Every extra field lowers completion.

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

    The homepage carries about 839 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Hotjar (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.

  • 5 cookies set on arrival

    5

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 ormazabal.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 | Google Tag Manager
Hosting
Vodafone Es

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on ormazabal.com, including 22 speed issues, 3 SEO issues and 5 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