Website review, no card needed

ferrazmaquinas.com.br logo

ferrazmaquinas.com.br website review

Visit site (opens in a new tab)Reviewed 24 October 202646 issues · 88 checks

This review found 46 issues worth fixing on ferrazmaquinas.com.br, 21 of them high impact, across 88 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

Full-page screenshot of ferrazmaquinas.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ferrazmaquinas.com.br at 1.6 s1.6 s
  2. ferrazmaquinas.com.br at 3.3 s3.3 s
  3. ferrazmaquinas.com.br at 4.9 s4.9 s
  4. ferrazmaquinas.com.br at 6.6 s6.6 s
  5. ferrazmaquinas.com.br at 8.2 s8.2 s
  6. ferrazmaquinas.com.br at 9.9 s9.9 s
  7. ferrazmaquinas.com.br at 11.5 s11.5 s
  8. ferrazmaquinas.com.br at 13.1 s13.1 s

Speed

13 to fix32
  • Use efficient cache lifetimes

    9.4 s · 4.4 MB

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

  • Reduce unused JavaScript

    7.7 s · 1.1 MB

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

  • Improve image delivery

    1.9 s · 1.6 MB

    26 images could be 1.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

  • Font display

    3.0 s

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

  • Render-blocking requests

    2.1 s

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

  • Reduce unused CSS

    1.2 s · 209 KiB

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

  • Mobile performance score: 32

    32/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 1.7 MB and 1.2 s of main-thread time.

  • Google Tag Manager adds 573 ms

    573 ms

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

  • Google CDN adds 373 ms

    373 ms

    Google CDN costs a phone 373 ms of main-thread work and 737 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.

  • Minify CSS

    300 ms · 37 KiB

    37 KiB could be saved by minifying CSS.

  • Main-thread work: 3.0 s

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

  • 13 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 12 KiB

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

  • Minify JavaScript

    9 KiB

    9 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: 4 ms

    4 ms

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

Core Web Vitals

7 to fix37
  • Largest Contentful Paint: 29.2 s

    29.2 s

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

  • Speed Index: 23.2 s

    23.2 s

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

  • Time to Interactive: 32.0 s

    32.0 s

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

  • First Contentful Paint: 5.0 s

    5.0 s

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

  • Cumulative Layout Shift: 0.271

    0.271

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

  • Total Blocking Time: 420 ms

    420 ms

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

  • 32 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

4 to fix33
  • Page weight: 6.2 MB in 119 requests

    6.2 MB

    Your homepage downloads 6.2 MB in 119 requests on a phone: images 3.2 MB (39), scripts 2.3 MB (36) and other files 362 KiB (19). Under 2 MB keeps phones on slow connections fast.

  • 3 images far larger than shown

    619 KiB

    3 images are downloaded at several times the size a phone draws them, for example familia-rosca-dupla-copy.jpg at 1,920 px wide, shown at 390 px. Resized copies would save about 619 KiB.

  • 23 images in older formats

    23 images (2.1 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.

  • 17 images below the first screen load straight away

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

  • About 1.8 g of CO₂ per visit

    1.76 g

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

Accessibility

12 to fixGoogle 7582
  • ARIA input fields must have an accessible name (2 elements)

    ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • 2 text elements with low contrast

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

  • Malformed lists

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

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

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

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

  • Zoom is disabled

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

  • 2 form fields without a label

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

  • 2 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

    Headings skip levels (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 33 images in the HTML carry an alt attribute.

  • 34 automated accessibility rules passed

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

SEO

2 to fixGoogle 9294
  • No structured data

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

  • 1 link crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 142 internal links, 15 external

    The homepage links to 142 pages on ferrazmaquinas.com.br and 15 external pages.

7 checks passed
  • Meta description: 136 characters

    Your meta description is 136 characters: “Fábrica de Ração é Ferraz. Empresa líder no mercado nacional na fabricação de máquinas extrusoras e fábricas de ração a…”.

  • One H1 headline

    Your main headline reads: “MÁQUINAS EXTRUSORAS E FÁBRICA DE RAÇÃO”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Máquinas Extrusoras e Fábrica de Ração - Ferraz Máquinas”.

  • Canonical URL set

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

Other pages

2 to fix88
  • 2 pages share a title

    https://ferrazmaquinas.com.br/conteudos/institucional.html and https://ferrazmaquinas.com.br/conteudos/equipamentos.html all use the title “Ferraz Máquinas”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 links to non-canonical URLs

    Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://ferrazmaquinas.com.br/conteudos/a-empresa.html, whose canonical is https://ferrazmaquinas.com.br/conteudo/a-empresa.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 77 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 9293
  • 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”.

  • 2 low-resolution images

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

2 checks passed
  • Tap targets are thumb-sized

    30 of 31 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 863 words of visible text.

3 checks passed
  • 5 calls to action

    The homepage has 5 calls to action, for example “Start-Up de Fábrica de Ração”, “Download Catálogo de Produtos” and “Download dos Catálogos 2023”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 7 cookies set on arrival

    7

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 ferrazmaquinas.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

Framework
jQuery
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 46 issues on ferrazmaquinas.com.br, including 20 speed issues, 2 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