Website review, no card needed

pglbr.com.br logo

pglbr.com.br website review

Visit site (opens in a new tab)Reviewed 19 November 202635 issues · 84 checks

This review found 35 issues worth fixing on pglbr.com.br, 14 of them high impact, across 84 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
3.7 s2.0 sMay 30Nov 142.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.5 s
Jun 6, 20263.3 s
Jun 13, 20263.2 s
Jun 20, 20263.2 s
Jun 27, 20263.2 s
Jul 4, 20263.1 s
Jul 11, 20263.0 s
Jul 18, 20262.7 s
Jul 25, 20262.4 s
Aug 1, 20262.6 s
Aug 8, 20262.7 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.5 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.2 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.4 s
Oct 17, 20262.6 s
Oct 24, 20263.1 s
Oct 31, 20262.8 s
Nov 7, 20262.4 s
Nov 14, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
112 ms84 msMay 30Nov 1490 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202688 ms
Jun 6, 202689 ms
Jun 13, 202693 ms
Jun 20, 2026103 ms
Jun 27, 2026105 ms
Jul 4, 2026103 ms
Jul 11, 2026103 ms
Jul 18, 202697 ms
Jul 25, 202694 ms
Aug 1, 2026109 ms
Aug 8, 2026104 ms
Aug 15, 2026108 ms
Aug 22, 2026109 ms
Aug 29, 202698 ms
Sep 5, 2026101 ms
Sep 12, 202699 ms
Sep 19, 202695 ms
Sep 26, 202693 ms
Oct 3, 202693 ms
Oct 10, 202691 ms
Oct 17, 202691 ms
Oct 24, 202697 ms
Oct 31, 202687 ms
Nov 7, 202694 ms
Nov 14, 202690 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 pglbr.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pglbr.com.br at 1.0 s1.0 s
  2. pglbr.com.br at 2.1 s2.1 s
  3. pglbr.com.br at 3.1 s3.1 s
  4. pglbr.com.br at 4.1 s4.1 s
  5. pglbr.com.br at 5.1 s5.1 s
  6. pglbr.com.br at 6.2 s6.2 s
  7. pglbr.com.br at 7.2 s7.2 s
  8. pglbr.com.br at 8.2 s8.2 s

Speed

6 to fix57
  • Render-blocking requests

    3.9 s

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

  • Reduce unused JavaScript

    1.8 s · 280 KiB

    About 280 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Reduce unused CSS

    1.7 s · 244 KiB

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

  • Improve image delivery

    900 ms · 1.4 MB

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

  • Mobile performance score: 57

    57/100

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

  • Font display

    850 ms

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

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    28 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Adobe TypeKit, Google Fonts and bunny.net), adding 162 KiB and 4 ms of main-thread time.

  • Use efficient cache lifetimes

    6 KiB

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

  • 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, 313 ms of it running JavaScript. That is comfortably low.

  • Server response: 144 ms

    144 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 13.3 s

    13.3 s

    Your largest element takes 13.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (7.0 s).

  • Speed Index: 14.6 s

    14.6 s

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

  • Time to Interactive: 13.6 s

    13.6 s

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

  • First Contentful Paint: 4.3 s

    4.3 s

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

  • 1 image without width and height

    1 image 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-11-14, real Chrome visitors' tap response (inp) went from 88 ms to 90 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

9 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 88 ms

    88 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 555 ms

    555 ms

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

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

    -30%

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 59 ms

    59 ms

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

Images and page weight

5 to fix43
  • 1 image over 500 KB

    Post-Blog-1200-x-630-px-8-760x630.png weighs 862 KiB. On a phone connection a single image that size takes seconds.

  • Page weight: 2.9 MB in 47 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 47 requests on a phone: images 1.7 MB (10), scripts 544 KiB (13) and fonts 377 KiB (13). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

    4 images (1.5 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.

  • 2 images below the first screen load straight away

    2 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    155 KiB

    1 image is downloaded at several times the size a phone draws it, for example vaga-popup-site.jpg at 1,801 px wide, shown at 290 px. Resized copies would save about 155 KiB.

  • About 0.8 g of CO₂ per visit

    0.82 g

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

Accessibility

7 to fixGoogle 8191
  • 6 text elements with low contrast

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

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate 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.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • 3 H1 headlines

    There are 3 <h1> headlines (“Melhor caminho entre dois pontos”, “Integração de processos logísticos” and “Integração de processos logísticos”). One clear main headline is easier for people and search engines.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 91 internal links, 9 external

    The homepage links to 91 pages on pglbr.com.br and 9 external pages.

7 checks passed
  • Meta description: 144 characters

    Your meta description is 144 characters: “Melhor caminho entre dois pontos. Qualidade, eficiência e uma estrutura completa para atender às necessidades e expecta…”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “PGL Brasil - Supply Chain Management”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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 and points crawlers to your sitemap.

  • XML sitemap found

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

AI search readiness

100
3 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

Other pages

3 to fix86
  • 3 pages share a title

    /, https://pglbr.com.br/en and https://pglbr.com.br/es all use the title “PGL Brasil - Supply Chain Management”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://pglbr.com.br/quem-somos, https://pglbr.com.br/escritorios, https://pglbr.com.br/certificados-e-premiacoes, https://pglbr.com.br/cases, https://pglbr.com.br/responsabilidade-social and https://pglbr.com.br/servicos-aereos and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://pglbr.com.br/en and https://pglbr.com.br/es use the same meta description. A description written for each page earns more clicks.

  • 4 pages slow to respond

    https://pglbr.com.br/servicos-aereos, https://pglbr.com.br/servicos-maritimos, https://pglbr.com.br/carga-projeto-e-especiais and https://pglbr.com.br/desembaraco-aduaneiro took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 37 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 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 3 small tap targets

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

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

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 274 words of copy

    The homepage carries about 274 words of visible text.

1 checks passed
  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage, asking for an email.

Privacy and tracking

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 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.

  • 5 other companies contacted

    Loading the homepage contacts 5 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 pglbr.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
Hosting
Vultr

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on pglbr.com.br, including 11 speed issues, 2 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