Website review, no card needed

alfainstrumentos.com.br logo

alfainstrumentos.com.br website review

Visit site (opens in a new tab)Reviewed 20 October 202635 issues · 81 checks

This review found 35 issues worth fixing on alfainstrumentos.com.br, 13 of them high impact, across 81 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
2.5 s1.4 sSep 5Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
Sep 5, 20262.4 s
Sep 12, 20261.9 s
Sep 19, 20261.8 s
Sep 26, 20261.6 s
Oct 3, 20261.5 s
Oct 10, 20261.6 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
119 ms99 msSep 5Oct 17101 ms
Show as table
DateReal-visitor tap response (INP)
Sep 5, 2026117 ms
Sep 12, 2026117 ms
Sep 19, 2026114 ms
Sep 26, 2026114 ms
Oct 3, 2026109 ms
Oct 10, 2026103 ms
Oct 17, 2026101 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 alfainstrumentos.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix57
  • Render-blocking requests

    2.7 s

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

  • Improve image delivery

    1.1 s · 654 KiB

    7 images could be 654 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 57

    57/100

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

  • Reduce unused JavaScript

    750 ms · 166 KiB

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

  • Google Tag Manager adds 370 ms

    370 ms

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

  • Main-thread work: 2.4 s

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

  • 1,879 HTML elements

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Cloudflare and Fastest Forward and others), adding 305 KiB and 379 ms of main-thread time.

  • 5 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 43 KiB

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

  • Legacy JavaScript

    150 ms · 10 KiB

    Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify CSS

    150 ms · 5 KiB

    5 KiB could be saved by minifying CSS.

  • Phones get a much slower page than desktops

    Desktop scores 90 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Use efficient cache lifetimes

    5 KiB

    2 files are served with short cache lifetimes, so returning visitors download them again (5 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.

  • Forced reflow

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

  • Minify JavaScript

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

7 to fix100
  • 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: 13.8 s

    13.8 s

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

  • Time to Interactive: 14.2 s

    14.2 s

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

  • First Contentful Paint: 4.7 s

    4.7 s

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

  • Speed Index: 7.0 s

    7.0 s

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

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

    1.0 s

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

7 checks passed
  • Real-user LCP: 2.0 s

    2.0 s

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

  • Real-user INP: 77 ms

    77 ms

    Real visitors wait 77 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.

  • Tap response (INP) got 13% faster for real visitors

    -13%

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

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

    -23%

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

  • Total Blocking Time: 178 ms

    178 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix58
  • Page weight: 4.0 MB in 177 requests

    4.0 MB

    Your homepage downloads 4.0 MB in 177 requests on a phone: images 2.9 MB (57), scripts 628 KiB (48) and stylesheets 249 KiB (64). Under 2 MB keeps phones on slow connections fast.

  • 15 images in older formats

    15 images (1.6 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.

  • An image on the first screen is lazy-loaded

    TETRACELL-DACT-removebg-preview.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 5 images far larger than shown

    452 KiB

    5 images are downloaded at several times the size a phone draws them, for example WhatsApp-Image-2024-05-24-at-09.46.15-1-600x524.png at 390 px wide, shown at 95 px. Resized copies would save about 452 KiB.

  • 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.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

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

  • 3 tap targets too small

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

  • 13 links without text

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

2 checks passed
  • Every image has alt text

    All 87 images in the HTML carry an alt attribute.

  • 50 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: 50 passed and 3 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 8566
  • No meta description

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

  • No H1 headline

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

  • Title is short (17 characters)

    Your title is only 17 characters: “Alfa Instrumentos”. 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.

  • No X (Twitter) card tag

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

  • 139 internal links, 19 external

    The homepage links to 139 pages on alfainstrumentos.com.br and 19 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://alfainstrumentos.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://alfainstrumentos.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://alfainstrumentos.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,074 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 13 pages without a meta description

    https://alfainstrumentos.com.br/pesagem-tanques-silos-estruturas, https://alfainstrumentos.com.br/product/sistemas-de-pesagem, https://alfainstrumentos.com.br/novo-samel, https://alfainstrumentos.com.br/product/suporte-articulado-sadel, https://alfainstrumentos.com.br/celulas-de-carga and https://alfainstrumentos.com.br/celulas-de-carga-2 and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://alfainstrumentos.com.br/pesagem-tanques-silos-estruturas, https://alfainstrumentos.com.br/product/sistemas-de-pesagem, https://alfainstrumentos.com.br/novo-samel, https://alfainstrumentos.com.br/product/suporte-articulado-sadel, https://alfainstrumentos.com.br/celulas-de-carga and https://alfainstrumentos.com.br/indicadores-e-transmissores and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “The Content Security Policy directive 'upgrade-insecure-requests' is ignored when delivered in a report-only policy.”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

    28 of 34 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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.

  • Thin social proof

    Social proof on the homepage: 67 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 264 words of visible text.

3 checks passed
  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 6 phone links and 0 email links.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 4 other companies contacted

    Loading the homepage contacts 4 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 alfainstrumentos.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 © 2025.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager

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 alfainstrumentos.com.br, including 14 speed issues, 5 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