Website review, no card needed
excelbr.com.br website review
Visit site (opens in a new tab)Reviewed 22 October 202633 issues · 75 checks
This review found 33 issues worth fixing on excelbr.com.br, 12 of them high impact, across 75 checks. The most urgent: use efficient cache lifetimes. 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
69DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.5 s
0.9 s
1.4 s
1.9 s
2.3 s
2.8 s
3.3 s
3.7 s
Speed
Use efficient cache lifetimes
1.7 s · 1.7 MB67 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Reduce unused JavaScript
1.8 s · 386 KiBAbout 386 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.
Render-blocking requests
1.4 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 57
57/100Your mobile performance score is 57 (desktop: 87). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
610 ms · 120 KiBAbout 120 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (zohocdn.com, Google Tag Manager and zohopublic.com and others), adding 1.0 MB and 468 ms of main-thread time.
Font display
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
zohocdn.com adds 216 ms
216 mszohocdn.com costs a phone 216 ms of main-thread work and 584 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
150 ms · 19 KiB2 images could be 19 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
150 ms · 10 KiB10 KiB could be saved by minifying JavaScript.
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.
Minify CSS
30 ms · 13 KiB13 KiB could be saved by minifying CSS.
Phones get a much slower page than desktops
Desktop scores 87 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 551 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.0 s
14.0 sYour largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
First Contentful Paint: 5.2 s
5.2 sThe first text or image appears after 5.2 s on a phone. Good is under 1.8 s.
Time to Interactive: 14.4 s
14.4 sThe page becomes fully interactive after 14.4 s. Good is under 3.8 s.
Speed Index: 9.2 s
9.2 sVisually, the page fills in at 9.2 s (Speed Index). Good is under 3.4 s.
47 images without width and height
47 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.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 34 ms
34 msScripts block the page for only 34 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.8 MB in 123 requests
2.8 MBYour homepage downloads 2.8 MB in 123 requests on a phone: images 1.4 MB (49), scripts 861 KiB (29) and fonts 235 KiB (7). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (71 KiB) is 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.
7 images below the first screen load straight away
7 images further down the page (152 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.8 g of CO₂ per visit
0.79 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.79 g of CO₂e: 94.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 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.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
5 form fields without a label
5 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 42 images in the HTML carry an alt attribute.
31 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (175 characters)
Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
44 internal links, 16 external
The homepage links to 44 pages on excelbr.com.br and 16 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Excel Fueling Technologies”.
Title: 55 characters
Your title is a healthy 55 characters: “Excel Fueling Technologies - Excelência em cada detalhe”.
Canonical URL set
The canonical URL is https://www.excelft.com/.
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://excelft.com/sitemap.xml.
AI search readiness
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.excelft.com/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.
1 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.
Other pages
1 linked page is broken
Your homepage links to https://www.excelft.com/produtos-servicos, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page points its canonical at the homepage
https://www.excelft.com/index 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.excelft.com/index all use the title “Excel Fueling Technologies - Excelência em cada detalhe”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.excelft.com/institucional and https://www.excelft.com/quem-somos use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.
4 checks passed
Every page has a meta description
All 14 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 14 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
Tap targets are thumb-sized
13 of 13 tappable elements near the top are at least 24 px.
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.
Thin social proof
Social proof on the homepage: 22 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 80 words
The homepage has only about 80 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 3 email links.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
5 cookies set on arrival
5Opening the homepage sets 5 cookies, 1 of them by other companies (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.
14 other companies contacted
Loading the homepage contacts 14 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 excelbr.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on excelbr.com.br, including 13 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.