4linux.com.br website review

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

17 files are served with short cache lifetimes, so returning visitors download them again (794 KiB).

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

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

About 519 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.

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

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

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

About 28 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.

Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

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

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

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

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

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

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

Your homepage downloads 2.2 MB in 159 requests on a phone: scripts 1.5 MB (73), fonts 474 KiB (7) and stylesheets 146 KiB (42). Under 2 MB keeps phones on slow connections fast.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.

Your title is 71 characters, so Google will cut it off around 60: “Cursos, Treinamento, Suporte, Consultoria, Desenvolvimento, IA - 4Linux”.

There are 8 <h1> headlines (“Cursos”, “Consultoria e Suporte” and “Jedai”). One clear main headline is easier for people and search engines.

Your meta description is 352 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 20 pages on 4linux.com.br and 22 external pages.

There is no /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.

/politica-de-privacidade/1-1 has no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /consultoria/suporte, whose canonical is /consultoria/suporte-ti. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/consultoria/quem-somos has no <h1> headline, so visitors and search engines get no clear main topic.

/consultoria/suporte took over 3 s to send its HTML from our server.

We fetched 8 pages linked from your homepage and read each the way a search engine does.

3 errors were logged to the browser console while the page loaded, for example “tailwind is not defined”.

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

1 link to other sites is dead, for example https://jedai.ai/ (502).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

4linux.com.br has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

4linux.com.br's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 341 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 17 cookies (measured from a US location before any click).

Loading the homepage contacts 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.