Website review, no card needed

westgroup.com.br logo

westgroup.com.br website review

Visit site (opens in a new tab)Reviewed 20 November 202642 issues · 66 checks

This review found 42 issues worth fixing on westgroup.com.br, 20 of them high impact, across 66 checks. The most urgent: reduce unused JavaScript. 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 westgroup.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. westgroup.com.br at 1.6 s1.6 s
  2. westgroup.com.br at 3.2 s3.2 s
  3. westgroup.com.br at 4.8 s4.8 s
  4. westgroup.com.br at 6.4 s6.4 s
  5. westgroup.com.br at 8.0 s8.0 s
  6. westgroup.com.br at 9.6 s9.6 s
  7. westgroup.com.br at 11.3 s11.3 s
  8. westgroup.com.br at 12.9 s12.9 s

Speed

13 to fix35
  • Reduce unused JavaScript

    8.3 s · 1.6 MB

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

  • Reduce unused CSS

    4.1 s · 913 KiB

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

  • Render-blocking requests

    4.8 s

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

  • Use efficient cache lifetimes

    1.9 s · 732 KiB

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 8.9 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and RD Station and others), adding 1.2 MB and 913 ms of main-thread time.

  • Avoid multiple page redirects

    901 ms

    The page goes through 1 redirect before it starts loading, costing about 901 ms. Link and advertise the final URL directly.

  • Google Tag Manager adds 688 ms

    688 ms

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

  • Improve image delivery

    200 ms · 354 KiB

    4 images could be 354 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

  • Document request latency

    420 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 2,540 HTML elements

    The page has 2,540 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • tallos.com.br adds 5 ms

    5 ms

    tallos.com.br costs a phone 5 ms of main-thread work and 335 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.

  • Font display

    250 ms

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

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    77 KiB

    77 KiB could be saved by minifying JavaScript.

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

  • Forced reflow

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

1 checks passed
  • Server response: 306 ms

    306 ms

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

Core Web Vitals

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

  • Real-user LCP: 7.0 s

    7.0 s

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

  • Real-user FCP: 5.1 s

    5.1 s

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

  • Real-user TTFB: 3.5 s

    3.5 s

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

  • First Contentful Paint: 14.9 s

    14.9 s

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

  • Largest Contentful Paint: 49.3 s

    49.3 s

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

  • Speed Index: 21.2 s

    21.2 s

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

  • Time to Interactive: 56.7 s

    56.7 s

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

  • Total Blocking Time: 660 ms

    660 ms

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

  • Real-user INP: 243 ms

    243 ms

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

  • Real-user CLS: 0.13

    0.13

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

  • Cumulative Layout Shift: 0.117

    0.117

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

Images and page weight

1 to fix33
  • Page weight: 12.4 MB in 245 requests

    12.4 MB

    Your homepage downloads 12.4 MB in 245 requests on a phone: images 6.6 MB (81), scripts 3.2 MB (55) and stylesheets 1.7 MB (55). Under 2 MB keeps phones on slow connections fast.

  • About 3.5 g of CO₂ per visit

    3.53 g

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

Accessibility

4 to fixGoogle 8478
  • No main landmark

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

  • Page should contain a level-one heading (1 element)

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

  • 4 text elements with low contrast

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

  • 2 tap targets too small

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 5 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 7 WCAG 2.2 A/AA and best-practice rules on the phone render: 5 passed and 2 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9284
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

6 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “Cursos Online Pesquisa de Certificado Autenticidade de Certificado Download de Apostilas Promoções West Group Assinatur…”.

  • Title: 32 characters

    Your title is a healthy 32 characters: “West Group - Início - West Group”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://westgroup.com.br/sitemap.xml.

AI search readiness

1 to fix83
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, 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.

  • No llms.txt

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

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

Best practices

1 to fixGoogle 9692
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of null (reading 'innerHTML')”.

1 checks passed
  • 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 direct contact details

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

  • Only about 0 words

    The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 cookies, 9 of them by other companies (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.

  • 14 other companies contacted

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

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 westgroup.com.br, 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
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager
Hosting
Vultr

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on westgroup.com.br, including 25 speed issues, 4 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