Website review, no card needed

bellota.com logo

bellota.com website review

Visit site (opens in a new tab)Reviewed 28 October 202631 issues · 73 checks

This review found 31 issues worth fixing on bellota.com, 9 of them high impact, across 73 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

Real-visitor load time (LCP)75th percentile, phones
3.4 s1.5 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.2 s
May 16, 20263.1 s
May 23, 20263.1 s
May 30, 20263.1 s
Jun 6, 20263.1 s
Jun 13, 20262.7 s
Jun 20, 20262.2 s
Jun 27, 20261.9 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.9 s
Jul 25, 20262.3 s
Aug 1, 20262.6 s
Aug 8, 20262.7 s
Aug 15, 20262.8 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.6 s
Oct 17, 20262.5 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
323 ms124 msMay 9Oct 24284 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026300 ms
May 16, 2026284 ms
May 23, 2026281 ms
May 30, 2026278 ms
Jun 6, 2026281 ms
Jun 13, 2026227 ms
Jun 20, 2026177 ms
Jun 27, 2026156 ms
Jul 4, 2026147 ms
Jul 11, 2026148 ms
Jul 18, 2026163 ms
Jul 25, 2026193 ms
Aug 1, 2026227 ms
Aug 8, 2026238 ms
Aug 15, 2026246 ms
Aug 22, 2026253 ms
Aug 29, 2026251 ms
Sep 5, 2026260 ms
Sep 12, 2026258 ms
Sep 19, 2026262 ms
Sep 26, 2026269 ms
Oct 3, 2026272 ms
Oct 10, 2026282 ms
Oct 17, 2026279 ms
Oct 24, 2026284 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 bellota.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. bellota.com at 0.5 s0.5 s
  2. bellota.com at 1.1 s1.1 s
  3. bellota.com at 1.6 s1.6 s
  4. bellota.com at 2.2 s2.2 s
  5. bellota.com at 2.7 s2.7 s
  6. bellota.com at 3.3 s3.3 s
  7. bellota.com at 3.8 s3.8 s
  8. bellota.com at 4.3 s4.3 s

Speed

7 to fix81
  • Render-blocking requests

    1.9 s

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

  • Use efficient cache lifetimes

    750 ms · 893 KiB

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

  • Mobile performance score: 81

    81/100

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

  • Reduce unused JavaScript

    677 KiB

    About 677 KiB of JavaScript is downloaded but never used on this page.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google Maps and bemyvega.com and others), adding 1.2 MB and 532 ms of main-thread time.

  • Google Tag Manager adds 344 ms

    344 ms

    Google Tag Manager costs a phone 344 ms of main-thread work and 536 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 Maps adds 106 ms

    106 ms

    Google Maps costs a phone 106 ms of main-thread work and 393 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.

  • 7 long tasks on the main thread

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

  • Reduce unused CSS

    40 ms · 40 KiB

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

  • Legacy JavaScript

    12 KiB

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

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 129 ms

    129 ms

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

Core Web Vitals

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

  • Time to Interactive: 13.3 s

    13.3 s

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

  • Speed Index: 9.2 s

    9.2 s

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

  • Real-user INP: 231 ms

    231 ms

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

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

    1.4 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Largest Contentful Paint: 2.7 s

    2.7 s

    Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Diseñamos, fabricamos y comercializamos en todo el mundo he…”. Most of its time is element render delay (1.5 s).

  • Total Blocking Time: 217 ms

    217 ms

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

  • Tap response (INP) held steady for real visitors

    -4%

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

4 checks passed
  • 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 22% faster for real visitors

    -22%

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

100
  • About 0.5 g of CO₂ per visit

    0.52 g

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

4 checks passed
  • Page weight: 1.8 MB in 77 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 77 requests on a phone: scripts 1.5 MB (38), fonts 125 KiB (3) and images 95 KiB (4). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

1 to fixGoogle 9697
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

2 checks passed
  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 37 automated accessibility rules passed

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

SEO

2 to fixGoogle 10087
  • No H1 headline

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 56 internal links, 1 external

    The homepage links to 56 pages on bellota.com and 1 external page.

6 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “BEllota Fabrica herramientas de alta calidad, ergonómicas, robustas y duraderas para Construcción, Agricultura, Industr…”.

  • Title: 51 characters

    Your title is a healthy 51 characters: “BELLOTA Fabricantes de herramientas de alta calidad”.

  • Canonical URL set

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

  • Structured data in place

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

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

AI search readiness

1 to fix83
  • 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.bellota.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.

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

Other pages

3 to fix86
  • 16 pages share 3 titles

    / and https://www.bellota.com/es-es all use the title “BELLOTA Fabricantes de Herramientas de alta calidad”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 14 pages share a meta description

    https://www.bellota.com/pt-pt, https://www.bellota.com/fr-fr, https://www.bellota.com/en-gb, https://www.bellota.com/en-ie, https://www.bellota.com/it-it and https://www.bellota.com/en-us use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.bellota.com/es-es, https://www.bellota.com/pt-pt, https://www.bellota.com/fr-fr, https://www.bellota.com/en-gb, https://www.bellota.com/en-ie and https://www.bellota.com/it-it and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.bellota.com/es-es, https://www.bellota.com/pt-pt, https://www.bellota.com/fr-fr and https://www.bellota.com/en-gb took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 26 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

2 to fixGoogle 9687
  • 2 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Identifier 'map' has already been declared”.

1 checks passed
  • 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.

  • 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 71 words

    The homepage has only about 71 words of visible text; thin pages give Google and first-time buyers little to go on.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

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 LinkedIn Insight (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.

  • 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 bellota.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
Hosting
Hetzner

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 bellota.com, including 16 speed issues, 2 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