remax.pt website review

About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.

Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Google Tag Manager, Cookiebot and deskbolt.com and others), adding 9.8 MB and 801 ms of main-thread time.

maxwork.pt costs a phone 0 ms of main-thread work and 8.8 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.

Google Tag Manager costs a phone 450 ms of main-thread work and 644 KiB 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 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.

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

A phone's processor spends 3.7 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

deskbolt.com costs a phone 65 ms of main-thread work and 297 KiB 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.

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

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

67 KiB could be saved by minifying JavaScript.

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

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

18 KiB could be saved by minifying CSS.

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.

For real visitors the layout shifts by 0.97 (75th percentile). Good is under 0.1.

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

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

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

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

The layout shifts by 0.171 while loading, so content jumps under the reader's thumb. Good is under 0.1.

17 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-31, real Chrome visitors' tap response (inp) went from 344 ms to 360 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 11.4 MB in 151 requests on a phone: images 8.9 MB (31), scripts 1.8 MB (56) and other files 525 KiB (55). Under 2 MB keeps phones on slow connections fast.

5 images weigh 7.1 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example development-main.png at 1,536 px wide, shown at 336 px. Resized copies would save about 1.7 MB.

18 images (8.9 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.

13 images further down the page (8.6 MB) 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 3.24 g of CO₂e: 388.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Inline text spacing must be adjustable with custom stylesheets: 1 element on the page fails this check, rated serious by axe-core.

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

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is only 15 characters: “RE/MAX Portugal”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

The homepage links to 47 pages on remax.pt and 11 external pages.

There is no https://remax.pt/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://remax.pt/pt and https://remax.pt/pt/recrutamento all use the title “RE/MAX Portugal”. Search engines can't tell which page to show for a search, so each competes with the others.

https://remax.pt/pt/recrutamento, https://remax.pt/pt/procuro-imovel, https://remax.pt/pt/institucional/comprarcomconfianca and https://remax.pt/pt/quantovaleaminhacasa use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://remax.pt/pt/bolsadeoportunidades, whose canonical is https://remax.pt/pt/comprar/imoveis/habitacao/r/r/r/t,oportunidade. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://remax.pt/pt/recrutamento, https://remax.pt/pt/comprar-empreendimentos, https://remax.pt/pt/procuro-imovel, https://remax.pt/pt/bolsadeoportunidades, https://remax.pt/pt/propostasmultiplas and https://remax.pt/pt/institucional/comprarcomconfianca and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

Large scripts ship without source maps.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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