Website review, no card needed

sonaesierra.com logo

sonaesierra.com website review

Visit site (opens in a new tab)Reviewed 29 October 202637 issues · 81 checks

This review found 37 issues worth fixing on sonaesierra.com, 12 of them high impact, across 81 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of sonaesierra.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sonaesierra.com at 0.4 s0.4 s
  2. sonaesierra.com at 0.8 s0.8 s
  3. sonaesierra.com at 1.1 s1.1 s
  4. sonaesierra.com at 1.5 s1.5 s
  5. sonaesierra.com at 1.9 s1.9 s
  6. sonaesierra.com at 2.3 s2.3 s
  7. sonaesierra.com at 2.6 s2.6 s
  8. sonaesierra.com at 3.0 s3.0 s

Speed

9 to fix56
  • Render-blocking requests

    6.5 s

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

  • Reduce unused CSS

    3.3 s · 669 KiB

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

  • Use efficient cache lifetimes

    2.2 s · 403 KiB

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

  • Reduce unused JavaScript

    1.2 s · 1.3 MB

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

  • Mobile performance score: 56

    56/100

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

  • Minify JavaScript

    150 ms · 489 KiB

    489 KiB could be saved by minifying JavaScript.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Cookiebot and Google CDN and others), adding 1.1 MB and 406 ms of main-thread time.

  • Google Tag Manager adds 214 ms

    214 ms

    Google Tag Manager costs a phone 214 ms of main-thread work and 469 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.

  • Google Maps adds 0 ms

    0 ms

    Google Maps costs a phone 0 ms of main-thread work and 392 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.

  • 3 long tasks on the main thread

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

  • Minify CSS

    150 ms · 7 KiB

    7 KiB could be saved by minifying CSS.

  • Font display

    100 ms

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

  • Improve image delivery

    32 KiB

    1 image could be 32 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Chained critical requests

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

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 484 ms of it running JavaScript. That is comfortably low.

  • Server response: 96 ms

    96 ms

    Your server sent the HTML in 96 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix65
  • Largest Contentful Paint: 20.4 s

    20.4 s

    Your largest element takes 20.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.

  • First Contentful Paint: 7.5 s

    7.5 s

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

  • Time to Interactive: 20.4 s

    20.4 s

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

  • Speed Index: 7.5 s

    7.5 s

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

  • 1 image without width and height

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

  • Not enough real-visitor data yet

    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 checks passed
  • Total Blocking Time: 140 ms

    140 ms

    Scripts block the page for only 140 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

3 to fix55
  • Page weight: 5.6 MB in 90 requests

    5.6 MB

    Your homepage downloads 5.6 MB in 90 requests on a phone: scripts 3.9 MB (72), images 905 KiB (3) and stylesheets 728 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    id-sonae-sierra.svg weighs 752 KiB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    Banner-paginas-website-11-768x429.png.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image below the first screen load straight away

    1 image further down the page (102 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.6 g of CO₂ per visit

    1.60 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 9391
  • Elements must only use permitted ARIA attributes (2 elements)

    Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

    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 (43 elements)

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

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

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

  • 1 form field without a label

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

  • Headings should not be empty (4 elements)

    Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 36 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9285
  • Meta description is short (48 characters)

    Your meta description is only 48 characters: “We pursue an integrated approach to real estate.”. 70 to 160 characters is enough to sell the click.

  • Structured data has 3 problems

    Structured data found (BreadcrumbList, ImageObject, WebPage and WebSite) but with 3 problems, for example “WebPage: thumbnailUrl is not an absolute URL ("https://sonaesierra.com/wp-content/uploads/2023/01/SIERRA_PEOPLE_1x1_thumb1…”.

  • No XML sitemap

    No XML sitemap at https://sonaesierra.com/sitemap.xml, so Google discovers your pages only by following links.

  • 9 links with vague text

    9 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 99 internal links, 9 external

    The homepage links to 99 pages on sonaesierra.com and 9 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Sonae Sierra signs agreement to acquire URW German third party real estate management business”.

  • Title: 38 characters

    Your title is a healthy 38 characters: “Sonae Sierra | Open mind Greater value”.

  • Canonical URL set

    The canonical URL is https://www.sonaesierra.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

  • No llms.txt

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

2 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Text is in the HTML

    Your server sends the page's text in the HTML (864 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix86
  • 6 pages share a title

    /, https://sonaesierra.com/pt, https://sonaesierra.com/es, https://sonaesierra.com/de, https://sonaesierra.com/fr and https://sonaesierra.com/it all use the title “Sonae Sierra | Open mind Greater value”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages share a meta description

    https://sonaesierra.com/personal-data-protection-commitment and https://sonaesierra.com/cookie-declaration use the same meta description. A description written for each page earns more clicks.

  • 6 pages without an H1

    https://sonaesierra.com/pt, https://sonaesierra.com/es, https://sonaesierra.com/de, https://sonaesierra.com/fr, https://sonaesierra.com/it and https://sonaesierra.com/reports-posts/economic-environmental-and-social-report-2025 have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://sonaesierra.com/cookie-declaration has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9683
  • 13 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.sonaesierra.com/wp-includes/css/dist/block-library/style.min.css?ver=6.9.10' f…”.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

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

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 857 words of copy

    The homepage carries about 857 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “LEARN MORE”.

  • 9 calls to action

    The homepage has 9 calls to action, for example “Learn more”, “Learn More” and “Contact Us”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Matomo.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

  • 2 cookies set on arrival

    2

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

  • 8 other companies contacted

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at sonaesierra.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager | Matomo
Hosting
Azure

Company

Founded
1989
Headquarters
Lisbon

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on sonaesierra.com, including 14 speed issues, 4 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25