Website review, no card needed

grupomater.com.br logo

grupomater.com.br website review

Visit site (opens in a new tab)Reviewed 23 October 202636 issues · 82 checks

This review found 36 issues worth fixing on grupomater.com.br, 14 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. 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
4.4 s2.4 sMay 2Oct 172.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.2 s
May 9, 20264.1 s
May 16, 20263.7 s
May 23, 20263.9 s
May 30, 20263.5 s
Jun 6, 20263.4 s
Jun 13, 20263.4 s
Jun 20, 20263.4 s
Jun 27, 20263.4 s
Jul 4, 20263.0 s
Jul 11, 20262.8 s
Jul 18, 20262.7 s
Jul 25, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.9 s
Aug 22, 20263.1 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20263.2 s
Oct 3, 20263.2 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
108 ms72 msMay 2Sep 2687 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202696 ms
Jun 20, 202698 ms
Jun 27, 2026104 ms
Jul 4, 202689 ms
Aug 8, 202676 ms
Aug 29, 202685 ms
Sep 5, 202693 ms
Sep 12, 202693 ms
Sep 19, 202693 ms
Sep 26, 202687 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 grupomater.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. grupomater.com.br at 0.5 s0.5 s
  2. grupomater.com.br at 1.0 s1.0 s
  3. grupomater.com.br at 1.5 s1.5 s
  4. grupomater.com.br at 2.0 s2.0 s
  5. grupomater.com.br at 2.5 s2.5 s
  6. grupomater.com.br at 3.1 s3.1 s
  7. grupomater.com.br at 3.6 s3.6 s
  8. grupomater.com.br at 4.1 s4.1 s

Speed

5 to fix60
  • Use efficient cache lifetimes

    1.8 s · 1.1 MB

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

  • Render-blocking requests

    2.9 s

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

  • Reduce unused CSS

    1.4 s · 272 KiB

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

  • Mobile performance score: 60

    60/100

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

  • Reduce unused JavaScript

    300 ms · 57 KiB

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

  • Improve image delivery

    197 KiB

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

  • Minify JavaScript

    150 ms · 30 KiB

    30 KiB could be saved by minifying JavaScript.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 179 ms. During a long task the page ignores taps.

  • Font display

    150 ms

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (goadopt.io, Google Fonts and pjn.com.br), adding 312 KiB and 101 ms of main-thread time.

  • Minify CSS

    10 KiB

    10 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    9 KiB

    Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

  • 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: 0.7 s

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

  • Server response: 140 ms

    140 ms

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

Core Web Vitals

9 to fix0
  • 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.

  • Largest Contentful Paint: 7.9 s

    7.9 s

    Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Em atividade há mais de 58 anos, o Grupo Mater integra os n…”. Most of its time is element render delay (3.4 s).

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Speed Index: 6.8 s

    6.8 s

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

  • Time to Interactive: 7.9 s

    7.9 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user CLS: 0.12

    0.12

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 3 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -7%

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

4 checks passed
  • Real-user FCP: 1.7 s

    1.7 s

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

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

    -32%

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

  • Cumulative Layout Shift: 0.091

    0.091

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.36 g

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

4 checks passed
  • Page weight: 1.3 MB in 49 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 49 requests on a phone: scripts 467 KiB (20), images 358 KiB (9) and stylesheets 250 KiB (9). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

6 to fixGoogle 8692
  • 10 text elements with low contrast

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

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 3 form fields without a label

    3 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 3 links without text

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

  • Headings skip levels

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

1 checks passed
  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 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

5 to fixGoogle 8571
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (11 characters)

    Your title is only 11 characters: “Grupo Mater”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 25 internal links, 13 external

    The homepage links to 25 pages on grupomater.com.br and 13 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://grupomater.com.br/.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://grupomater.com.br/wp-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://grupomater.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.

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 (463 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix78
  • 4 pages share 2 titles

    https://grupomater.com.br/quem-somos and https://grupomater.com.br/grupomater/quem-somos all use the title “Quem somos – Grupo Mater”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages without a meta description

    https://grupomater.com.br/quem-somos, https://grupomater.com.br/lgpd, https://grupomater.com.br/carreiras, https://grupomater.com.br/responsabilidade-social, https://grupomater.com.br/contato and https://grupomater.com.br/grupomater/quem-somos and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://grupomater.com.br/grupomater/quem-somos, whose canonical is https://grupomater.com.br/quem-somos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages without an H1

    https://grupomater.com.br/quem-somos, https://grupomater.com.br/lgpd, https://grupomater.com.br/carreiras, https://grupomater.com.br/responsabilidade-social, https://grupomater.com.br/contato and https://grupomater.com.br/grupomater/quem-somos and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://grupomater.com.br/carreiras and https://grupomater.com.br/grupomater/carreiras have 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.

  • 7 internal pages checked

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

3 checks passed
  • Linked pages load

    All 7 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

2 to fixGoogle 6987
  • 4 small tap targets

    4 of 12 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 “Failed to load resource: net::ERR_FAILED”.

  • 1 low-resolution image

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 421 words of visible text.

1 checks passed
  • 1 short form

    A short form (3 fields at most) is right on the homepage, asking for an email.

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • No consent tool detected

    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.

  • 6 other companies contacted

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

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

Upkeep, stack and company

  • The footer still says © 2021.

Stack

CMS
WordPress
Framework
jQuery

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on grupomater.com.br, including 14 speed issues, 5 SEO issues and 4 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