Website review, no card needed
engeman.net website review
Visit site (opens in a new tab)Reviewed 19 November 202629 issues · 82 checks
This review found 29 issues worth fixing on engeman.net, 10 of them high impact, across 82 checks. The most urgent: page weight: 61.8 MB in 107 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.7 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.4 s |
| Nov 7, 2026 | 2.4 s |
| Nov 14, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 117 ms |
| Jun 20, 2026 | 116 ms |
| Jun 27, 2026 | 119 ms |
| Jul 4, 2026 | 114 ms |
| Jul 11, 2026 | 119 ms |
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 114 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 111 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 126 ms |
| Aug 29, 2026 | 130 ms |
| Sep 5, 2026 | 143 ms |
| Sep 12, 2026 | 147 ms |
| Sep 19, 2026 | 146 ms |
| Sep 26, 2026 | 135 ms |
| Oct 3, 2026 | 137 ms |
| Oct 10, 2026 | 134 ms |
| Oct 17, 2026 | 132 ms |
| Oct 24, 2026 | 148 ms |
| Oct 31, 2026 | 149 ms |
| Nov 7, 2026 | 152 ms |
| Nov 14, 2026 | 157 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
Speed
Render-blocking requests
2.1 s40 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Use efficient cache lifetimes
21.0 MB95 files are served with short cache lifetimes, so returning visitors download them again (21.0 MB).
Google CDN adds 308 ms
308 msGoogle CDN costs a phone 308 ms of main-thread work and 742 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.
Reduce unused JavaScript
351 KiBAbout 351 KiB of JavaScript is downloaded but never used on this page.
4 third-party services on the page
4 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Cloudflare and others), adding 856 KiB and 352 ms of main-thread time.
Reduce unused CSS
150 ms · 79 KiBAbout 79 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.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 91 ms. During a long task the page ignores taps.
Improve image delivery
56 KiB1 image could be 56 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need.
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
3 checks passed
Mobile performance score: 94
94/100Your mobile performance score is 94. That is in Google's “good” band (90 and up).
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 994 ms of it running JavaScript. That is comfortably low.
Server response: 152 ms
152 msYour server sent the HTML in 152 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Time to Interactive: 11.7 s
11.7 sThe page becomes fully interactive after 11.7 s. Good is under 3.8 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 120 ms to 157 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Speed Index: 5.1 s
5.1 sVisually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
7 checks passed
Real-user INP: 173 ms
173 msReal visitors wait 173 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user TTFB: 800 ms
800 msReal visitors wait 800 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Engeman Soluções Industriais”.
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Total Blocking Time: 29 ms
29 msScripts block the page for only 29 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 61.8 MB in 107 requests
61.8 MBYour homepage downloads 61.8 MB in 107 requests on a phone: media 59.0 MB (3), images 1.0 MB (13) and scripts 928 KiB (37). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
14 KiB1 image is downloaded at several times the size a phone draws it, for example oleo-e-gas.webp at 390 px wide, shown at 114 px. Resized copies would save about 14 KiB.
1 image below the first screen load straight away
1 image further down the page (63 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 17.5 g of CO₂ per visit
17.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 17.51 g of CO₂e: 2100.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
10 tap targets too small
10 tap targets are too small or too close together to hit reliably with a finger.
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.
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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 11 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 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (14 characters)
Your title is only 14 characters: “HOME - Engeman”. Between 30 and 65 characters leaves room to say what you do and for whom.
86 internal links, 18 external
The homepage links to 86 pages on engeman.net and 18 external pages.
6 checks passed
Meta description: 153 characters
Your meta description is 153 characters: “Mais de 4 décadas de Inovação Engeman Soluções Industriais Soluções inteligentes para os desafios da indústria. Engenha…”.
Canonical URL set
The canonical URL is https://engeman.net/.
Structured data in place
Structured data found: Article, BreadcrumbList, ImageObject, Organization and Person.
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://engeman.net/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) 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.
Opted out of AI training for 5 crawlers
robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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.
Text is in the HTML
Your server sends the page's text in the HTML (738 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://engeman.net/llms.txt (16 KiB, 54 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
9 pages without an H1
https://engeman.net/conheca-a-engeman/quem-somos, https://engeman.net/conheca-a-engeman/valores-engeman, https://engeman.net/conheca-a-engeman/clientes, https://engeman.net/conheca-a-engeman/cqte-engeman, https://engeman.net/conheca-a-engeman/igualdade-de-mulheres-e-homens and https://engeman.net/nosso-time and 3 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 21 found) and read each the way a search engine does.
6 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 a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
1 small tap target
1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.
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”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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.
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 353 words of copy
The homepage carries about 353 words of visible text.
3 checks passed
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
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.
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 engeman.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on engeman.net, 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.