Website review, no card needed

fg.com.br logo

fg.com.br website review

Visit site (opens in a new tab)Reviewed 20 November 202650 issues · 94 checks

This review found 50 issues worth fixing on fg.com.br, 21 of them high impact, across 94 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
3.6 s3.2 sMay 30Nov 143.3 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.5 s
Jun 6, 20263.5 s
Jun 13, 20263.4 s
Jun 20, 20263.4 s
Jun 27, 20263.4 s
Jul 4, 20263.4 s
Jul 11, 20263.4 s
Jul 18, 20263.4 s
Jul 25, 20263.5 s
Aug 1, 20263.5 s
Aug 8, 20263.5 s
Aug 15, 20263.6 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.6 s
Sep 12, 20263.6 s
Sep 19, 20263.5 s
Sep 26, 20263.5 s
Oct 3, 20263.5 s
Oct 10, 20263.5 s
Oct 17, 20263.5 s
Oct 24, 20263.5 s
Oct 31, 20263.4 s
Nov 7, 20263.4 s
Nov 14, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
217 ms202 msMay 30Nov 14213 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026206 ms
Jun 6, 2026209 ms
Jun 13, 2026209 ms
Jun 20, 2026209 ms
Jun 27, 2026207 ms
Jul 4, 2026207 ms
Jul 11, 2026206 ms
Jul 18, 2026204 ms
Jul 25, 2026204 ms
Aug 1, 2026205 ms
Aug 8, 2026207 ms
Aug 15, 2026209 ms
Aug 22, 2026212 ms
Aug 29, 2026214 ms
Sep 5, 2026213 ms
Sep 12, 2026215 ms
Sep 19, 2026214 ms
Sep 26, 2026212 ms
Oct 3, 2026213 ms
Oct 10, 2026213 ms
Oct 17, 2026212 ms
Oct 24, 2026212 ms
Oct 31, 2026212 ms
Nov 7, 2026212 ms
Nov 14, 2026213 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 fg.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fg.com.br at 0.4 s0.4 s
  2. fg.com.br at 0.8 s0.8 s
  3. fg.com.br at 1.2 s1.2 s
  4. fg.com.br at 1.5 s1.5 s
  5. fg.com.br at 1.9 s1.9 s
  6. fg.com.br at 2.3 s2.3 s
  7. fg.com.br at 2.7 s2.7 s
  8. fg.com.br at 3.1 s3.1 s

Speed

12 to fix45
  • Use efficient cache lifetimes

    3.6 s · 1.0 MB

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

  • Reduce unused JavaScript

    2.6 s · 610 KiB

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

  • Render-blocking requests

    2.9 s

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

  • Mobile performance score: 45

    45/100

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

  • 3,317 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, vtex.com.br and Facebook and others), adding 3.4 MB and 1.1 s of main-thread time.

  • Reduce unused CSS

    460 ms · 145 KiB

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

  • Google Tag Manager adds 506 ms

    506 ms

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

    417 KiB

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

  • Main-thread work: 2.8 s

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

  • vteximg.com.br adds 24 ms

    24 ms

    vteximg.com.br costs a phone 24 ms of main-thread work and 2.1 MB 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.

  • goadopt.io adds 91 ms

    91 ms

    goadopt.io costs a phone 91 ms of main-thread work and 299 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.

  • 15 long tasks on the main thread

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

  • Legacy JavaScript

    21 KiB

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

  • Minify JavaScript

    17 KiB

    17 KiB could be saved by minifying JavaScript.

  • Minify CSS

    8 KiB

    8 KiB could be saved by minifying CSS.

  • 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: 17 ms

    17 ms

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

Core Web Vitals

11 to fix33
  • 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 CLS: 0.31

    0.31

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

  • Largest Contentful Paint: 19.6 s

    19.6 s

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

  • Time to Interactive: 19.9 s

    19.9 s

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

  • Speed Index: 7.8 s

    7.8 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Total Blocking Time: 624 ms

    624 ms

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

  • Real-user INP: 286 ms

    286 ms

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

  • Real-user FCP: 2.0 s

    2.0 s

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

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

  • 58 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

2 checks passed
  • 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.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 4.0 MB in 317 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 317 requests on a phone: images 1.7 MB (115), scripts 1.6 MB (54) and other files 380 KiB (138). Under 2 MB keeps phones on slow connections fast.

  • 4 images below the first screen load straight away

    4 images further down the page (87 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.1 g of CO₂ per visit

    1.12 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.12 g of CO₂e: 134.8 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

12 to fixGoogle 7286
  • Hidden but focusable

    17 elements hidden from screen readers can still receive keyboard focus.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 4 images without alt text

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

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

  • Zoom is disabled

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

  • 3 links without text

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

  • 2 form fields without a label

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

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 8587
  • Title is short (18 characters)

    Your title is only 18 characters: “Ferramentas Gerais”. 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.

  • 7 links crawlers can't follow

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

  • 738 internal links, 11 external

    The homepage links to 738 pages on fg.com.br and 11 external pages.

6 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “A Ferramentas Gerais oferece as melhores marcas de Esmerilhadeira, Compressor, Máquina de Solda, Furadeira, Parafusadei…”.

  • One H1 headline

    Your main headline reads: “Categorias em destaque”.

  • Canonical URL set

    The canonical URL is https://www.fg.com.br/.

  • 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://www.fg.com.br/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.fg.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 (1,277 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix76
  • 1 page points its canonical at the homepage

    https://www.fg.com.br/minhas-listas declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.fg.com.br/minhas-listas all use the title “Ferramentas Gerais”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages share a meta description

    https://www.fg.com.br/abrasivos, https://www.fg.com.br/abrasivos/brunidor and https://www.fg.com.br/abrasivos/correia use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://www.fg.com.br/minhas-listas, https://www.fg.com.br/abrasivos, https://www.fg.com.br/abrasivos/bastao, https://www.fg.com.br/abrasivos/brunidor, https://www.fg.com.br/abrasivos/bucha and https://www.fg.com.br/abrasivos/calibrador and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://www.fg.com.br/abrasivos/bucha, https://www.fg.com.br/abrasivos/cortador and https://www.fg.com.br/abrasivos/escova took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

2 to fixGoogle 8591
  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Event name is not defined”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 4 low-resolution images

    4 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    744 of 789 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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 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 1,750 words of copy

    The homepage carries about 1,750 words of visible text.

2 checks passed
  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 2 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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 Meta Pixel (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.

  • 17 cookies set on arrival

    17

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 fg.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

Framework
React
Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 50 issues on fg.com.br, including 23 speed issues, 3 SEO issues and 3 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