Website review, no card needed

blgcloud.es logo

blgcloud.es website review

Visit site (opens in a new tab)Reviewed 10 November 202638 issues · 80 checks

This review found 38 issues worth fixing on blgcloud.es, 10 of them high impact, across 80 checks. The most urgent: page weight: 4.4 MB in 81 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

Full-page screenshot of blgcloud.es (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. blgcloud.es at 0.5 s0.5 s
  2. blgcloud.es at 1.0 s1.0 s
  3. blgcloud.es at 1.4 s1.4 s
  4. blgcloud.es at 1.9 s1.9 s
  5. blgcloud.es at 2.4 s2.4 s
  6. blgcloud.es at 2.9 s2.9 s
  7. blgcloud.es at 3.3 s3.3 s
  8. blgcloud.es at 3.8 s3.8 s

Speed

9 to fix66
  • Improve image delivery

    1,021 KiB

    21 images could be 1,021 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 66

    66/100

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

  • Render-blocking requests

    800 ms

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

  • Reduce unused JavaScript

    729 KiB

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

  • Font display

    500 ms

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

  • Use efficient cache lifetimes

    388 KiB

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

  • 8 long tasks on the main thread

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

  • Google Maps adds 232 ms

    232 ms

    Google Maps costs a phone 232 ms of main-thread work and 394 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: 2.6 s

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Maps, Google Tag Manager and Google Analytics and others), adding 868 KiB and 454 ms of main-thread time.

  • Reduce unused CSS

    183 KiB

    About 183 KiB of CSS is downloaded but never applied on this page.

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 106 ms

    106 ms

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

Core Web Vitals

5 to fix63
  • Time to Interactive: 17.2 s

    17.2 s

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

  • Total Blocking Time: 716 ms

    716 ms

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

  • Cumulative Layout Shift: 0.248

    0.248

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

  • Speed Index: 4.7 s

    4.7 s

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

  • 3 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Largest Contentful Paint: 1.8 s

    1.8 s

    Your largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “ERP del mañana el único SaaS rápido, fácil de usar e interc…”.

Images and page weight

4 to fix33
  • Page weight: 4.4 MB in 81 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 81 requests on a phone: images 1.4 MB (45), fonts 1.4 MB (8) and scripts 1.3 MB (17). Under 2 MB keeps phones on slow connections fast.

  • 9 images far larger than shown

    767 KiB

    9 images are downloaded at several times the size a phone draws them, for example groupeDouillet-logo.png at 2,048 px wide, shown at 82 px. Resized copies would save about 767 KiB.

  • 19 images below the first screen load straight away

    19 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 11 images in older formats

    11 images (983 KiB) 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 1.2 g of CO₂ per visit

    1.24 g

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

Accessibility

12 to fixGoogle 7583
  • 8 buttons without a name

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

  • Hidden but focusable

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

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

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

  • 10 images without alt text

    10 images have no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

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

  • 4 links without text

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

  • ARIA role should be appropriate for the element (3 elements)

    ARIA role should be appropriate for the element: 3 elements on the page fail this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

4 to fixGoogle 9282
  • Title is long (86 characters)

    Your title is 86 characters, so Google will cut it off around 60: “BlgCloud | El ERP sectorial para concesionarios, arrendadores y talleres de reparación”.

  • No structured data

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

  • Meta description is long (215 characters)

    Your meta description is 215 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 106 internal links, 18 external

    The homepage links to 106 pages on blgcloud.es and 18 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “ERP del mañanael único SaaS rápido, fácil de usar e interconectado con su ecosistema”.

  • Canonical URL set

    The canonical URL is https://www.blgcloud.es/.

  • 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.blgcloud.es/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://www.blgcloud.es/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 (981 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.blgcloud.es/iniciar-sesion has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.blgcloud.es/iniciar-sesion 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.

  • 15 internal pages checked

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

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

  • 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 42 small tap targets

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

  • Missing source maps

    Large scripts ship without source maps.

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

100
  • 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 1,337 words of copy

    The homepage carries about 1,337 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Solicitar una demo”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Solicitar una demo” and “Solicito mi demo”.

  • Social proof on the page

    Social proof on the homepage: 11 testimonial or review blocks, 12 customer or partner logos, a star rating and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Matomo.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads 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.

  • 6 cookies set on arrival

    6

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

  • 8 other companies contacted

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

Upkeep, stack and company

Stack

Analytics
Google Tag Manager | Matomo
Hosting
OVHcloud

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 blgcloud.es, including 14 speed issues and 4 SEO issues. 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