Website review, no card needed

mdsgroup.com logo

mdsgroup.com website review

Visit site (opens in a new tab)Reviewed 26 October 202635 issues · 79 checks

This review found 35 issues worth fixing on mdsgroup.com, 16 of them high impact, across 79 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

Real-visitor load time (LCP)75th percentile, phones
5.6 s2.0 sMay 9Oct 243.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20265.2 s
May 16, 20265.2 s
May 23, 20264.8 s
May 30, 20264.2 s
Jun 6, 20263.4 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.8 s
Jul 4, 20263.1 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20263.1 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.6 s
Aug 22, 20262.7 s
Aug 29, 20262.8 s
Sep 5, 20262.9 s
Sep 12, 20263.3 s
Sep 19, 20263.0 s
Sep 26, 20263.1 s
Oct 3, 20263.2 s
Oct 10, 20262.9 s
Oct 17, 20263.2 s
Oct 24, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
101 ms77 msMay 9Oct 2498 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202698 ms
May 16, 202687 ms
May 23, 202696 ms
May 30, 202681 ms
Jun 6, 202683 ms
Jun 13, 202680 ms
Jun 20, 202683 ms
Jun 27, 202691 ms
Jul 4, 202693 ms
Jul 11, 202693 ms
Jul 18, 202690 ms
Jul 25, 202696 ms
Aug 1, 202687 ms
Aug 8, 202688 ms
Aug 15, 202688 ms
Aug 22, 202687 ms
Aug 29, 202693 ms
Sep 5, 202692 ms
Sep 12, 202687 ms
Sep 19, 202686 ms
Sep 26, 202684 ms
Oct 3, 202686 ms
Oct 10, 202690 ms
Oct 17, 202694 ms
Oct 24, 202698 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of mdsgroup.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix70
  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 70

    70/100

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

  • Reduce unused JavaScript

    160 ms · 430 KiB

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

  • Improve image delivery

    560 KiB

    2 images could be 560 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused CSS

    310 ms · 67 KiB

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

  • Google CDN adds 147 ms

    147 ms

    Google CDN costs a phone 147 ms of main-thread work and 348 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google CDN, Cookiebot and mPulse and others), adding 615 KiB and 344 ms of main-thread time.

  • Use efficient cache lifetimes

    150 ms · 39 KiB

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

  • 4 long tasks on the main thread

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

  • 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.1 s

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

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

9 to fix50
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user LCP: 4.7 s

    4.7 s

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

  • Real-user FCP: 4.2 s

    4.2 s

    Real visitors see the first content after 4.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 2.6 s

    2.6 s

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

  • Time to Interactive: 34.8 s

    34.8 s

    The page becomes fully interactive after 34.8 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.

  • Largest Contentful Paint: 4.9 s

    4.9 s

    Your largest element takes 4.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

4 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 37% faster for real visitors

    -37%

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

  • Total Blocking Time: 115 ms

    115 ms

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

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

1 to fix70
  • Page weight: 10.2 MB in 66 requests

    10.2 MB

    Your homepage downloads 10.2 MB in 66 requests on a phone: images 9.2 MB (43), scripts 876 KiB (13) and stylesheets 60 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (105 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.

  • About 2.9 g of CO₂ per visit

    2.90 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.90 g of CO₂e: 347.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 load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8692
  • 1 button without a name

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

  • Input buttons must have discernible text (1 element)

    Input buttons must have discernible text: 1 element on the page fails this check, rated critical 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.

  • Zoom is disabled

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

  • 1 form field without a label

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

2 checks passed
  • Every image has alt text

    All 18 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

3 to fixGoogle 9290
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No robots.txt

    There is no robots.txt at mdsgroup.com/robots.txt, the first file search crawlers ask for.

  • 3 links crawlers can't follow

    3 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 45 internal links, 24 external

    The homepage links to 45 pages on mdsgroup.com and 24 external pages.

6 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Na MDS move-nos a vontade de assegurar que, para onde quer que vá, nós estaremos lá, tanto a protegê-lo como a aconselh…”.

  • One H1 headline

    Your main headline reads: “Sempre próximos onde quer que vá”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Global Insurance and Risk Consultants - MDS Portugal”.

  • Canonical URL set

    The canonical URL is https://www.mdsgroup.com/pt/.

  • Open Graph tags complete

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.mdsgroup.com/sitemap.xml.

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://www.mdsgroup.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

    There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.

  • Text is in the HTML

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

Other pages

5 to fix57
  • 1 linked page is broken

    Your homepage links to https://www.mdsgroup.com/pt/noticias/detalhes.php, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 5 pages share 2 titles

    https://www.mdsgroup.com/pt, https://www.mdsgroup.com/pt/solucoes and / all use the title “Global Insurance and Risk Consultants - MDS Portugal”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.mdsgroup.com/en has no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages share a meta description

    https://www.mdsgroup.com/pt/procurar, https://www.mdsgroup.com/pt/descubra-a-mds/quem-somos, https://www.mdsgroup.com/pt/descubra-a-mds/como-trabalhamos, https://www.mdsgroup.com/pt/descubra-a-mds/a-nossa-historia, https://www.mdsgroup.com/pt/descubra-a-mds/management-team and https://www.mdsgroup.com/pt/solucoes and 7 others use the same meta description. A description written for each page earns more clicks.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.mdsgroup.com/pt/media/mds-news, whose canonical is https://www.mdsgroup.com/pt/noticias. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page with very little text

    https://www.mdsgroup.com/pt/procurar 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 26 found) and read each the way a search engine does.

3 checks passed
  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    27 of 33 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix33
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 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 322 words of copy

    The homepage carries about 322 words of visible text.

1 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (measured from a US location before any click).

  • 7 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

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

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 mdsgroup.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on mdsgroup.com, including 15 speed issues, 3 SEO issues and 5 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