Website review, no card needed

qubbos.es logo

qubbos.es website review

Visit site (opens in a new tab)Reviewed 7 November 202624 issues · 80 checks

This review found 24 issues worth fixing on qubbos.es, 7 of them high impact, across 80 checks. The most urgent: fails Core Web Vitals for real visitors. 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.1 s1.3 sMay 16Oct 311.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.7 s
Jun 20, 20262.4 s
Jun 27, 20262.1 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.8 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.8 s
Aug 22, 20261.8 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.7 s
Oct 24, 20261.6 s
Oct 31, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
247 ms150 msMay 16Oct 31211 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026173 ms
May 23, 2026175 ms
May 30, 2026179 ms
Jun 6, 2026186 ms
Jun 13, 2026181 ms
Jun 20, 2026177 ms
Jun 27, 2026169 ms
Jul 4, 2026164 ms
Jul 11, 2026161 ms
Jul 18, 2026163 ms
Jul 25, 2026172 ms
Aug 1, 2026184 ms
Aug 8, 2026199 ms
Aug 15, 2026207 ms
Aug 22, 2026217 ms
Aug 29, 2026222 ms
Sep 5, 2026221 ms
Sep 12, 2026221 ms
Sep 19, 2026222 ms
Sep 26, 2026227 ms
Oct 3, 2026230 ms
Oct 10, 2026236 ms
Oct 17, 2026234 ms
Oct 24, 2026223 ms
Oct 31, 2026211 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 qubbos.es (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

4 to fix89
  • 8,015 HTML elements

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

  • Mobile performance score: 89

    89/100

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

  • Render-blocking requests

    750 ms

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

  • Main-thread work: 2.7 s

    A phone's processor spends 2.7 s on main-thread work while loading, 817 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 (Klaviyo, Shopify and sequra.com and others), adding 313 KiB and 181 ms of main-thread time.

  • Reduce unused CSS

    150 ms · 16 KiB

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

  • 2 long tasks on the main thread

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

  • Reduce unused JavaScript

    36 KiB

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

  • Use efficient cache lifetimes

    26 KiB

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

  • Duplicated JavaScript

    20 KiB

    20 KiB JavaScript is shipped twice across bundles.

  • Legacy JavaScript

    19 KiB

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

  • Improve image delivery

    9 KiB

    2 images could be 9 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Minify JavaScript

    9 KiB

    9 KiB could be saved by minifying JavaScript.

  • 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: 13 ms

    13 ms

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

Core Web Vitals

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

  • Speed Index: 6.1 s

    6.1 s

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

  • Real-user INP: 213 ms

    213 ms

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

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

    +25%

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

  • Time to Interactive: 5.0 s

    5.0 s

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

  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “qubbos”. Most of its time is resource load delay (1.5 s).

  • 1 image without width and height

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

8 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

    Real visitors wait 1.6 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.

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 589 ms

    589 ms

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

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

    -45%

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

  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 33 ms

    33 ms

    Scripts block the page for only 33 ms while loading. Good is under 200 ms.

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.48 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.48 g of CO₂e: 58.1 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.7 MB in 227 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 227 requests on a phone: other files 834 KiB (113), scripts 494 KiB (64) and images 205 KiB (33). 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

5 to fixGoogle 8894
  • 20 text elements with low contrast

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 32 links without text

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

  • Alternative text of images should not be repeated as text (13 elements)

    Alternative text of images should not be repeated as text: 13 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 52 automated accessibility rules passed

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

SEO

2 to fixGoogle 9288
  • Title is short (26 characters)

    Your title is only 26 characters: “qubbos | Electrodomésticos”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (33 characters)

    Your meta description is only 33 characters: “Primeras marcas. Mejores precios.”. 70 to 160 characters is enough to sell the click.

  • 632 internal links, 13 external

    The homepage links to 632 pages on qubbos.es and 13 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Electrodomésticos de primeras marcas al mejor precio”.

  • Canonical URL set

    The canonical URL is https://qubbos.es/.

  • Structured data in place

    Structured data found: Organization 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://qubbos.es/sitemap.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: 4 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://qubbos.es/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without an H1

    https://qubbos.es/pages/ofertas-electrodomesticos has no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://qubbos.es/collections/frigorificos, https://qubbos.es/collections/frigorificos-combi and https://qubbos.es/collections/frigorificos-de-dos-puertas took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    94 of 95 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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: 10 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

2 checks passed
  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Microsoft Clarity and Hotjar.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 3 cookies set on arrival

    3

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

  • 13 other companies contacted

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

Apps on your store

Your storefront loads 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Pandectes Gdpr · Klaviyo Email Marketing Sms · Gdpr Cookie Consent · sequra.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Hotjar
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on qubbos.es, including 11 speed issues, 2 SEO issues and 4 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