intelecta.com.br website review

About 484 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.

10 images could be 741 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Squarespace, sqspcdn.com and tomticket.com and others), adding 2.8 MB and 593 ms of main-thread time.

Squarespace costs a phone 539 ms of main-thread work and 1.2 MB 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.

Polyfills for old browsers add 94 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.2 MB 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.

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

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

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

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 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

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.9 MB in 115 requests on a phone: images 1.2 MB (14), scripts 1.2 MB (62) and fonts 266 KiB (14). Under 2 MB keeps phones on slow connections fast.

9 images (610 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.

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

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

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

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

Links must have discernible text: 6 elements on the page fail this check, rated serious by axe-core.

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

There are 2 <h1> headlines (“Simplificamos sua gestão!” and “Quanto tempo e dinheiro você já gastou com outras…”). One clear main headline is easier for people and search engines.

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

Structured data found (LocalBusiness, Organization and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/55e0e6c7e4b0cd58cff…”.

The homepage links to 59 pages on intelecta.com.br and 5 external pages.

Your Organization JSON-LD is missing name, url, logo and description. 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://intelecta.com.br/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.

Your homepage links to https://intelecta.com.br/intelecta, https://intelecta.com.br/linha-do-tempo and https://intelecta.com.br/posicionamento, which answer with an error. Visitors hit a dead end and search engines drop them.

https://intelecta.com.br/empresa, https://intelecta.com.br/solucoes, https://intelecta.com.br/servicos, https://intelecta.com.br/blog, https://intelecta.com.br/contato and https://intelecta.com.br/erp-windows all use the title “Sistema de Gestão ERP — Empresário ERP | Sistema de Gestão ERP online…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://intelecta.com.br/cliente has no meta description, so Google writes the search snippet from whatever text it finds.

https://intelecta.com.br/empresa, https://intelecta.com.br/solucoes, https://intelecta.com.br/servicos, https://intelecta.com.br/blog, https://intelecta.com.br/contato and https://intelecta.com.br/erp-windows use the same meta description. A description written for each page earns more clicks.

https://intelecta.com.br/contato and https://intelecta.com.br/md-e have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/55e0e6c7e4b0cd58cff6ec6a/486/5c5…”.

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.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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