Website review, no card needed

hexis.com.br logo

hexis.com.br website review

Visit site (opens in a new tab)Reviewed 28 October 202656 issues · 93 checks

This review found 56 issues worth fixing on hexis.com.br, 24 of them high impact, across 93 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

Real-visitor load time (LCP)75th percentile, phones
3.8 s2.2 sMay 9Oct 243.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.5 s
May 23, 20263.6 s
May 30, 20263.5 s
Jun 6, 20263.1 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.8 s
Jul 11, 20262.7 s
Jul 18, 20262.6 s
Jul 25, 20262.5 s
Aug 1, 20262.4 s
Aug 8, 20262.4 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.6 s
Sep 5, 20262.5 s
Sep 12, 20262.6 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.9 s
Oct 24, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
181 ms97 msMay 9Oct 24171 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026111 ms
May 16, 2026116 ms
May 23, 2026118 ms
May 30, 2026116 ms
Jun 6, 2026117 ms
Jun 13, 2026116 ms
Jun 20, 2026114 ms
Jun 27, 2026120 ms
Jul 4, 2026113 ms
Jul 11, 2026107 ms
Jul 18, 2026111 ms
Jul 25, 2026111 ms
Aug 1, 2026118 ms
Aug 8, 2026119 ms
Aug 15, 2026109 ms
Aug 22, 2026109 ms
Aug 29, 2026108 ms
Sep 5, 2026109 ms
Sep 12, 2026112 ms
Sep 19, 2026113 ms
Sep 26, 2026114 ms
Oct 3, 2026118 ms
Oct 10, 2026122 ms
Oct 17, 2026137 ms
Oct 24, 2026171 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

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

How it loaded on a phone

  1. hexis.com.br at 1.0 s1.0 s
  2. hexis.com.br at 2.1 s2.1 s
  3. hexis.com.br at 3.1 s3.1 s
  4. hexis.com.br at 4.2 s4.2 s
  5. hexis.com.br at 5.2 s5.2 s
  6. hexis.com.br at 6.3 s6.3 s
  7. hexis.com.br at 7.3 s7.3 s
  8. hexis.com.br at 8.4 s8.4 s

Speed

13 to fix19
  • Use efficient cache lifetimes

    19.6 s · 17.6 MB

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

  • Improve image delivery

    16.3 s · 13.2 MB

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

  • Reduce unused JavaScript

    1.2 s · 609 KiB

    About 609 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Render-blocking requests

    1.8 s

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

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 647 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 19

    19/100

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

  • Main-thread work: 6.2 s

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

  • 8 third-party services on the page

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

  • Font display

    450 ms

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

  • Facebook adds 415 ms

    415 ms

    Facebook costs a phone 415 ms of main-thread work and 280 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.

  • 20 long tasks on the main thread

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

  • Reduce unused CSS

    310 ms · 82 KiB

    About 82 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 310 ms faster on a phone.

  • ContentSquare adds 274 ms

    274 ms

    ContentSquare costs a phone 274 ms of main-thread work and 178 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

    170 ms · 8 KiB

    8 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    21 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 45 but mobile only 19. 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.

  • 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: 35 ms

    35 ms

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

Core Web Vitals

12 to fix33
  • 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.

  • Largest Contentful Paint: 61.8 s

    61.8 s

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

  • Time to Interactive: 65.5 s

    65.5 s

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

  • Speed Index: 13.4 s

    13.4 s

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

  • Total Blocking Time: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0.373

    0.373

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

  • Real-user LCP: 2.6 s

    2.6 s

    Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.12

    0.12

    For real visitors the layout shifts by 0.12 (75th percentile). Good is under 0.1.

  • Tap response (INP) got 36% slower for real visitors

    +36%

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

  • Real-user FCP: 1.9 s

    1.9 s

    Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

  • First Contentful Paint: 2.1 s

    2.1 s

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

  • 16 images without width and height

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

3 checks passed
  • Real-user INP: 157 ms

    157 ms

    Real visitors wait 157 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user TTFB: 692 ms

    692 ms

    Real visitors wait 692 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 13% faster for real visitors

    -13%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Images and page weight

5 to fix18
  • Page weight: 18.7 MB in 126 requests

    18.7 MB

    Your homepage downloads 18.7 MB in 126 requests on a phone: images 17.0 MB (45), scripts 1.5 MB (38) and stylesheets 110 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 8 images over 500 KB

    8 images weigh 11.5 MB together. On a phone connection a single image that size takes seconds.

  • 15 images far larger than shown

    10.9 MB

    15 images are downloaded at several times the size a phone draws them, for example Linkedin-C4.png at 2,001 px wide, shown at 270 px. Resized copies would save about 10.9 MB.

  • 29 images in older formats

    29 images (15.2 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.

  • 14 images below the first screen load straight away

    14 images further down the page (4.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 5.3 g of CO₂ per visit

    5.31 g

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

Accessibility

9 to fixGoogle 8388
  • 7 buttons without a name

    7 buttons have no accessible name, so screen readers announce just “button”.

  • 4 text elements with low contrast

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

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

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

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

  • 4 links without text

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

  • 2 form fields without a label

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 45 automated accessibility rules passed

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

SEO

7 to fixGoogle 8267
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (16 characters)

    Your title is only 16 characters: “Hexis Científica”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“HEXIS Cientifica - Produtos para Laboratório, Pro…” and “Quando o resultado importa, escolha Hach”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No robots.txt

    There is no robots.txt at hexis.com.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.

  • 1 link crawlers can't follow

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

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 172 internal links, 6 external

    The homepage links to 172 pages on hexis.com.br and 6 external pages.

2 checks passed
  • Structured data in place

    Structured data found: Organization.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.hexis.com.br/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing logo, description 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.

  • No llms.txt

    There is no https://www.hexis.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

    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 (996 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://www.hexis.com.br/produtos, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 5 pages without a meta description

    https://www.hexis.com.br/fale-conosco, https://www.hexis.com.br/produtos/geral, https://www.hexis.com.br/seletor-produto, https://www.hexis.com.br/hach/sc4500 and https://www.hexis.com.br/trojan have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://www.hexis.com.br/suporte/sac, https://www.hexis.com.br/seletor-produto and https://www.hexis.com.br/hach/sc4500 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 69 found) and read each the way a search engine does.

4 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • 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 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 8587
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • No HTML doctype

    The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

  • 7 distorted images

    7 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    35 of 42 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 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

    The homepage carries about 340 words of visible text.

3 checks passed
  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and LinkedIn Insight.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 2 email links.

Privacy and tracking

  • 6 trackers load before any consent

    6

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

  • 9 cookies set on arrival

    9

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

  • 28 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 hexis.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
Hosting
Azure

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 56 issues on hexis.com.br, including 25 speed issues, 7 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