nubaal.com website review

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

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

3 images could be 70 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

4 third-party services load with your homepage (Shopify, Amazon Web Services and nfcube.com and others), adding 261 KiB and 116 ms of main-thread time.

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

1 long task block the main thread while loading, the longest for 97 ms. During a long task the page ignores taps.

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

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

16 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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.

Your homepage downloads 2.2 MB in 162 requests on a phone: other files 717 KiB (72), fonts 628 KiB (2) and images 506 KiB (17). Under 2 MB keeps phones on slow connections fast.

DSC02894.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 14 characters: “Nubal – Nubaal”. Between 30 and 65 characters leaves room to say what you do and for whom.

Structured data found (Organization and WebSite) but with 5 problems, for example “Organization: sameAs is not an absolute URL ("a")”.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Your <h1> is empty.

The homepage links to 40 pages on nubaal.com and 2 external pages.

Your homepage links to https://nubal.mx/a, which answers with an error. Visitors hit a dead end and search engines drop it.

https://nubal.mx/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://nubal.mx/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://nubal.mx/collections/frontpage and https://nubal.mx/collections/all all use the title “Productos – Nubaal”. Search engines can't tell which page to show for a search, so each competes with the others.

https://nubal.mx/collections/colagenos-y-nutrientes, https://nubal.mx/customer_authentication/redirect, https://nubal.mx/collections/frontpage, https://nubal.mx/collections/all, https://nubal.mx/policies/refund-policy and https://nubal.mx/policies/privacy-policy and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://nubal.mx/collections/colagenos-y-nutrientes, https://nubal.mx/pages/quienes-somos, https://nubal.mx/customer_authentication/redirect, https://nubal.mx/collections/frontpage and https://nubal.mx/collections/all have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 332 words of visible text.

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

Opening the homepage sets 11 cookies (measured from a US location before any click).

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.

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