nathor.com website review

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

8 images could be 5.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

About 59 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

4 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Google Analytics and others), adding 200 KiB and 187 ms of main-thread time.

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

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 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FECHAR INÍCIO SOBRE PRODUTOS TRICICLOS BALANCE BIKE ARO 12"…”.

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

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

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

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

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

Your homepage downloads 9.5 MB in 107 requests on a phone: images 8.7 MB (42), fonts 419 KiB (6) and scripts 312 KiB (30). Under 2 MB keeps phones on slow connections fast.

IMG_0739-Hot-Wheels-em-Alteracao-Selo-INMETRO-1.webp weighs 521 KiB. On a phone connection a single image that size takes seconds.

11 images (974 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.

5 images further down the page (743 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images are downloaded at several times the size a phone draws them, for example IMG_0739-Hot-Wheels-em-Alteracao-Selo-INMETRO-1.webp at 1,024 px wide, shown at 300 px. Resized copies would save about 299 KiB.

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

1 button has no accessible name, so screen readers announce just “button”.

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

9 tap targets are too small or too close together to hit reliably with a finger.

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

All page content should be contained by landmarks: 12 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.

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

Your title is only 15 characters: “Início - Nathor”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 19 pages on nathor.com and 3 external pages.

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.

There is no https://nathor.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://nathor.com/quem-somos and https://nathor.com/sobre all use the title “Quem somos - Nathor”, and 3 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://nathor.com/quem-somos, https://nathor.com/onde-comprar, https://nathor.com/sobre and https://nathor.com/blog have no meta description, so Google writes the search snippet from whatever text it finds.

https://nathor.com/nossos-produtos and https://nathor.com/shopping use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://nathor.com/sobre, whose canonical is https://nathor.com/quem-somos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://nathor.com/quem-somos, https://nathor.com/nossos-produtos, https://nathor.com/onde-comprar, https://nathor.com/sobre and https://nathor.com/shopping have no <h1> headline, so visitors and search engines get no clear main topic.

https://nathor.com/sobre, https://nathor.com/seja-um-revendedor and https://nathor.com/contato took over 3 s to send their HTML from our server.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

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

5 errors were logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of null (reading 'addEventListener')”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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

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

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