neubox.com website review

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

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

4 third-party services load with your homepage (Trust Pilot, socket.io and Cloudflare CDN and others), adding 177 KiB and 38 ms of main-thread time.

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

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

8 KiB could be saved by minifying JavaScript.

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

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

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.

Your largest element takes 4.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Nuestro sitio web utiliza cookies para distinguirte de otro…”. Most of its time is element render delay (1.8 s).

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

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

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

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

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

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

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

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

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

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

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

Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.

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

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

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

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

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

The homepage links to 186 pages on neubox.com and 26 external pages.

There is no https://neubox.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.

https://neubox.com/reforestacion is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://neubox.com/tutoriales has no <h1> headline, so visitors and search engines get no clear main topic.

https://neubox.com/programa-de-apoyo-a-las-artes and https://neubox.com/soporte took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: jQuery is not defined”.

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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 756 words of visible text.

Opening the homepage sets 3 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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.