mapforest.com.br website review

91 files are served with short cache lifetimes, so returning visitors download them again (3.2 MB).

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

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

About 234 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

Your mobile performance score is 62. 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 250 ms).

9 KiB could be saved by minifying CSS.

3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 216 KiB and 99 ms of main-thread time.

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

Polyfills for old browsers add 11 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.

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

4 KiB could be saved by minifying JavaScript.

Your largest element takes 16.7 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 17.0 s. Good is under 3.8 s.

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

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

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

2 images are downloaded at several times the size a phone draws them, for example Banner-1-scaled.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 664 KiB.

Your homepage downloads 3.4 MB in 97 requests on a phone: images 2.4 MB (15), scripts 530 KiB (36) and stylesheets 311 KiB (38). Under 2 MB keeps phones on slow connections fast.

10 images (2.3 MB) 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.

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

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

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

All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate 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.

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

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

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

Your title is only 16 characters: “Home - MapForest”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“A Origem da Inovação na Gestão Geoespacial” and “A MapForest é uma startup (spin-off do Grupo Inde…”). One clear main headline is easier for people and search engines.

The homepage links to 66 pages on mapforest.com.br and 12 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://mapforest.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://mapforest.com.br/blog, which answers with an error. Visitors hit a dead end and search engines drop it.

https://mapforest.com.br/2024/01/16/como-o-grupo-index-revoluciona-a-analise-de-dados-com-o-geobi, https://mapforest.com.br/2023/12/06/marco-legal-das-startups-a-vitoria-do-empreendedorismo and https://mapforest.com.br/2023/12/05/blockchain-liberdade-e-regulacao-os-tres-mosqueteiros-da-revolucao-financeira have no meta description, so Google writes the search snippet from whatever text it finds.

https://mapforest.com.br/faq, https://mapforest.com.br/contato, https://mapforest.com.br/2024/01/16/como-o-grupo-index-revoluciona-a-analise-de-dados-com-o-geobi, https://mapforest.com.br/2023/12/06/marco-legal-das-startups-a-vitoria-do-empreendedorismo and https://mapforest.com.br/2023/12/05/blockchain-liberdade-e-regulacao-os-tres-mosqueteiros-da-revolucao-financeira have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

1 image is served at too low a resolution for sharp phone screens.

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.

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

Before a visitor clicks anything, the page loads 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 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.