Website review, no card needed
aisolutions.tec.br website review
Visit site (opens in a new tab)Reviewed 18 October 202631 issues · 64 checks
This review found 31 issues worth fixing on aisolutions.tec.br, 7 of them high impact, across 64 checks. The most urgent: page weight: 24.2 MB in 67 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
76CClosest 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.6 s
1.3 s
1.9 s
2.6 s
3.2 s
3.9 s
4.5 s
5.2 s
Speed
Render-blocking requests
2.0 s17 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
Use efficient cache lifetimes
300 ms · 24.0 MB58 files are served with short cache lifetimes, so returning visitors download them again (24.0 MB).
Mobile performance score: 87
87/100Your mobile performance score is 87 (desktop: 90). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
150 ms · 16 KiBAbout 16 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.
Improve image delivery
62 KiB2 images could be 62 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 56 ms. During a long task the page ignores taps.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 131 KiB and 0 ms of main-thread time.
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
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 242 ms of it running JavaScript. That is comfortably low.
Server response: 117 ms
117 msYour server sent the HTML in 117 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 3.0 s
3.0 sYour largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Somos especializados em extração, estruturação e validação …”. Most of its time is element render delay (2.2 s).
3 images without width and height
3 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.
3 checks passed
Time to Interactive: 3.0 s
3.0 sThe page is fully interactive after 3.0 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 24.2 MB in 67 requests
24.2 MBYour homepage downloads 24.2 MB in 67 requests on a phone: media 23.0 MB (2), images 840 KiB (10) and scripts 159 KiB (26). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
11 KiB1 image is downloaded at several times the size a phone draws it, for example Seven1.png at 390 px wide, shown at 116 px. Resized copies would save about 11 KiB.
2 images in older formats
2 images (116 KiB) 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.
1 image below the first screen load straight away
1 image further down the page (55 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 6.8 g of CO₂ per visit
6.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.85 g of CO₂e: 821.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
All page content should be contained by landmarks (24 elements)
All page content should be contained by landmarks: 24 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.
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.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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 (27 characters)
Your title is only 27 characters: “AI Solutions – AI Solutions”. 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 XML sitemap
No XML sitemap at https://www.aisolutions.tec.br/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at aisolutions.tec.br/robots.txt, the first file search crawlers ask for.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
50 internal links, 4 external
The homepage links to 50 pages on aisolutions.tec.br and 4 external pages.
1 checks passed
Canonical URL set
The canonical URL is https://www.aisolutions.tec.br/.
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.aisolutions.tec.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (458 words), so crawlers that don't run JavaScript still read it.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
6 of 7 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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 249 words
The homepage has only about 249 words of visible text; thin pages give Google and first-time buyers little to go on.
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
2 short forms
2 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 7 email links.
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.
2 other companies contacted
Loading the homepage contacts 2 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 aisolutions.tec.br, 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 31 issues on aisolutions.tec.br, including 7 speed issues, 9 SEO issues and 5 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.