Website review, no card needed

pixeon.com logo

pixeon.com website review

Visit site (opens in a new tab)Reviewed 1 November 202636 issues · 78 checks

This review found 36 issues worth fixing on pixeon.com, 9 of them high impact, across 78 checks. The most urgent: render-blocking requests. 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
2.1 s1.6 sMay 9Oct 241.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20261.9 s
Jun 20, 20261.9 s
Jun 27, 20262.0 s
Jul 4, 20262.0 s
Jul 11, 20261.9 s
Jul 18, 20262.0 s
Jul 25, 20262.0 s
Aug 1, 20262.1 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
211 ms130 msMay 9Oct 24185 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026153 ms
May 16, 2026155 ms
May 23, 2026169 ms
May 30, 2026172 ms
Jun 6, 2026172 ms
Jun 13, 2026173 ms
Jun 20, 2026168 ms
Jun 27, 2026149 ms
Jul 4, 2026145 ms
Jul 11, 2026139 ms
Jul 18, 2026140 ms
Jul 25, 2026162 ms
Aug 1, 2026171 ms
Aug 8, 2026179 ms
Aug 15, 2026172 ms
Aug 22, 2026179 ms
Aug 29, 2026172 ms
Sep 5, 2026171 ms
Sep 12, 2026176 ms
Sep 19, 2026179 ms
Sep 26, 2026195 ms
Oct 3, 2026202 ms
Oct 10, 2026198 ms
Oct 17, 2026193 ms
Oct 24, 2026185 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 pixeon.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pixeon.com at 0.7 s0.7 s
  2. pixeon.com at 1.4 s1.4 s
  3. pixeon.com at 2.2 s2.2 s
  4. pixeon.com at 2.9 s2.9 s
  5. pixeon.com at 3.6 s3.6 s
  6. pixeon.com at 4.3 s4.3 s
  7. pixeon.com at 5.0 s5.0 s
  8. pixeon.com at 5.7 s5.7 s

Speed

9 to fix75
  • Render-blocking requests

    1.0 s

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

  • Main-thread work: 4.3 s

    A phone's processor spends 4.3 s on main-thread work while loading, 2.7 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, posthog.com and Clarity and others), adding 1.6 MB and 1.6 s of main-thread time.

  • Mobile performance score: 75

    75/100

    Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 729 ms

    729 ms

    Google Tag Manager costs a phone 729 ms of main-thread work and 1.0 MB 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

    721 KiB

    About 721 KiB of JavaScript is downloaded but never used on this page.

  • posthog.com adds 384 ms

    384 ms

    posthog.com costs a phone 384 ms of main-thread work and 228 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

    314 KiB

    13 images could be 314 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    290 KiB

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

  • 14 long tasks on the main thread

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

  • Legacy JavaScript

    33 KiB

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

  • Duplicated JavaScript

    8 KiB

    8 KiB JavaScript is shipped twice across bundles.

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

    201 ms

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

Core Web Vitals

7 to fix67
  • 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: 23.4 s

    23.4 s

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

  • Real-user INP: 213 ms

    213 ms

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

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

    +23%

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

  • Total Blocking Time: 580 ms

    580 ms

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

  • Largest Contentful Paint: 3.5 s

    3.5 s

    Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Tecnologia aliada à inteligência para evoluir a saúde Soluç…”.

  • Speed Index: 3.7 s

    3.7 s

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

7 checks passed
  • Real-user LCP: 1.6 s

    1.6 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 706 ms

    706 ms

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

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

    -11%

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.006

    0.006

    The layout barely moves while loading (CLS 0.006, good is under 0.1).

Images and page weight

3 to fix53
  • Page weight: 4.9 MB in 130 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 130 requests on a phone: scripts 1.6 MB (42), images 1.6 MB (47) and other files 1.2 MB (32). Under 2 MB keeps phones on slow connections fast.

  • 13 images below the first screen load straight away

    13 images further down the page (600 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 5 images far larger than shown

    140 KiB

    5 images are downloaded at several times the size a phone draws them, for example SELOS-SBIS-2026-_2_.webp at 1,000 px wide, shown at 112 px. Resized copies would save about 140 KiB.

  • 4 images in older formats

    4 images (253 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.

  • About 1.4 g of CO₂ per visit

    1.40 g

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

Accessibility

6 to fixGoogle 9793
  • 7 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 52 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. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10097
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 79 internal links, 15 external

    The homepage links to 79 pages on pixeon.com and 15 external pages.

7 checks passed
  • Meta description: 157 characters

    Your meta description is 157 characters: “A Pixeon é líder em tecnologia para gestão de laboratórios, clínicas e hospitais com software e sistema para automatiza…”.

  • One H1 headline

    Your main headline reads: “Tecnologia aliadaà eficiência para evoluir a saúde”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Pixeon | Gestão, Softwares e Sistemas para Medicina e Saúde”.

  • Canonical URL set

    The canonical URL is https://www.pixeon.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, WebPage and WebSite.

  • 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://www.pixeon.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • 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.

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

  • llms.txt published

    The site publishes https://www.pixeon.com/llms.txt (5 KiB, 39 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix70
  • 1 page points its canonical at the homepage

    https://www.pixeon.com/sistema 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.

  • 1 linked page hidden from search

    https://www.pixeon.com/cases/case-hospital-de-amor is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages share a title

    / and https://www.pixeon.com/sistema all use the title “Pixeon | Gestão, Softwares e Sistemas para Medicina e Saúde”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages without a meta description

    https://www.pixeon.com/novidades, https://www.pixeon.com/cases/case-hospital-de-amor, https://www.pixeon.com/sobre, https://www.pixeon.com/blog and https://www.pixeon.com/parceiros have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “%c%d font-size:0;color:transparent NaN”.

2 checks passed
  • Tap targets are thumb-sized

    8 of 9 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.

  • A 8-field form

    Your longest form asks for 8 fields (7 required). Every extra field lowers completion.

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

    The homepage carries about 871 words of visible text.

3 checks passed
  • Social proof on the page

    Social proof on the homepage: 10 customer or partner logos and 4 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies (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.

  • 29 other companies contacted

    Loading the homepage contacts 29 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 pixeon.com, 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 36 issues on pixeon.com, including 16 speed issues, 1 SEO issue 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