Website review, no card needed

ibyte.com.br logo

ibyte.com.br website review

Visit site (opens in a new tab)Reviewed 18 November 202651 issues · 89 checks

This review found 51 issues worth fixing on ibyte.com.br, 24 of them high impact, across 89 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
5.3 s2.4 sMay 30Nov 144.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.8 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20262.8 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20262.8 s
Sep 5, 20262.8 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20263.0 s
Oct 17, 20263.1 s
Oct 24, 20263.5 s
Oct 31, 20264.1 s
Nov 7, 20264.7 s
Nov 14, 20264.9 s
Real-visitor tap response (INP)75th percentile, phones
510 ms188 msMay 30Nov 14425 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026257 ms
Jun 6, 2026261 ms
Jun 13, 2026263 ms
Jun 20, 2026263 ms
Jun 27, 2026267 ms
Jul 4, 2026266 ms
Jul 11, 2026262 ms
Jul 18, 2026256 ms
Jul 25, 2026254 ms
Aug 1, 2026254 ms
Aug 8, 2026256 ms
Aug 15, 2026260 ms
Aug 22, 2026256 ms
Aug 29, 2026251 ms
Sep 5, 2026243 ms
Sep 12, 2026237 ms
Sep 19, 2026229 ms
Sep 26, 2026226 ms
Oct 3, 2026227 ms
Oct 10, 2026225 ms
Oct 17, 2026238 ms
Oct 24, 2026287 ms
Oct 31, 2026370 ms
Nov 7, 2026473 ms
Nov 14, 2026425 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 ibyte.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ibyte.com.br at 1.2 s1.2 s
  2. ibyte.com.br at 2.3 s2.3 s
  3. ibyte.com.br at 3.5 s3.5 s
  4. ibyte.com.br at 4.6 s4.6 s
  5. ibyte.com.br at 5.8 s5.8 s
  6. ibyte.com.br at 6.9 s6.9 s
  7. ibyte.com.br at 8.1 s8.1 s
  8. ibyte.com.br at 9.2 s9.2 s

Speed

13 to fix32
  • Use efficient cache lifetimes

    1.6 s · 828 KiB

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

  • Reduce unused JavaScript

    1.2 s · 903 KiB

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

  • vtexassets.com adds 1.6 s

    1.6 s

    vtexassets.com costs a phone 1.6 s of main-thread work and 3.4 MB 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: 32

    32/100

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

  • Main-thread work: 8.2 s

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

  • 3,229 HTML elements

    The page has 3,229 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 8 third-party services on the page

    8 third-party services load with your homepage (vtexassets.com, Google Tag Manager and Facebook and others), adding 5.2 MB and 3.2 s of main-thread time.

  • Improve image delivery

    300 ms · 1.4 MB

    81 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Google Tag Manager adds 992 ms

    992 ms

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

  • Reduce unused CSS

    600 ms · 238 KiB

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

  • 20 long tasks on the main thread

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

  • Render-blocking requests

    350 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 350 ms.

  • usebeon.io adds 173 ms

    173 ms

    usebeon.io costs a phone 173 ms of main-thread work and 423 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.

  • Legacy JavaScript

    150 ms · 63 KiB

    Polyfills for old browsers add 63 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 58 ms

    58 ms

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

Core Web Vitals

14 to fix0
  • 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.

  • Real-user LCP: 4.1 s

    4.1 s

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

  • Real-user INP: 910 ms

    910 ms

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

  • Real-user CLS: 0.33

    0.33

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

  • Largest Contentful Paint: 16.8 s

    16.8 s

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

  • Time to Interactive: 31.1 s

    31.1 s

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

  • Speed Index: 11.8 s

    11.8 s

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

  • Total Blocking Time: 1.5 s

    1.5 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

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

    +73%

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

  • Largest content (LCP) got 69% slower for real visitors

    +69%

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

  • Real-user FCP: 2.2 s

    2.2 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 10 images without width and height

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

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 6.7 MB in 420 requests

    6.7 MB

    Your homepage downloads 6.7 MB in 420 requests on a phone: images 2.6 MB (173), scripts 2.5 MB (67) and other files 854 KiB (171). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    61 KiB

    1 image is downloaded at several times the size a phone draws it, for example bde2b486-2ecf-458b-a87b-51413c5053b6___6f8cfe71d992e4f04d350 at 1,080 px wide, shown at 60 px. Resized copies would save about 61 KiB.

  • 7 images below the first screen load straight away

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

  • About 1.9 g of CO₂ per visit

    1.91 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

8 to fixGoogle 8587
  • 21 text elements with low contrast

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

  • Interactive controls must not be nested (2 elements)

    Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.

  • ARIA commands must have an accessible name (1 element)

    ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Scrollable region must have keyboard access (1 element)

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

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

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

  • Alternative text of images should not be repeated as text (26 elements)

    Alternative text of images should not be repeated as text: 26 elements on the page fail this check, rated minor by axe-core.

  • 12 links without text

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (6 elements).

2 checks passed
  • Every image has alt text

    All 42 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • Structured data has 1 problem

    Structured data found (ItemList and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No social preview image

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

  • No X (Twitter) card tag

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

  • 91 internal links, 23 external

    The homepage links to 91 pages on ibyte.com.br and 23 external pages.

6 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Preço baixo em Notebooks, PC Gamer e Eletrônicos é na ibyte. Aproveite descontos imperdíveis, parcelamento facilitado e…”.

  • One H1 headline

    Your main headline reads: “É mais que tecnologia, é do seu jeito”.

  • Title: 65 characters

    Your title is a healthy 65 characters: “Eletrônicos, Computadores, Notebooks, Áudio, Vídeo e mais | Ibyte”.

  • Canonical URL set

    The canonical URL is https://www.ibyte.com.br/.

  • 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.ibyte.com.br/sitemap.xml.

AI search readiness

2 to fix75
  • 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.

  • Some text only appears after JavaScript runs

    50%

    The HTML your server sends has 487 of the 969 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

  • No llms.txt

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

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

5 to fix67
  • 5 pages without a title

    https://www.ibyte.com.br/notebooks, https://www.ibyte.com.br/pcs-e-notebooks/computador, https://www.ibyte.com.br/pcs-e-notebooks/perifericos, https://www.ibyte.com.br/hardware/placa-de-video and https://www.ibyte.com.br/casa-inteligente have no <title>, so Google invents the link text in results.

  • 2 linked pages hidden from search

    https://www.ibyte.com.br/1122 and https://www.ibyte.com.br/1391 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 5 pages without a meta description

    https://www.ibyte.com.br/notebooks, https://www.ibyte.com.br/pcs-e-notebooks/computador, https://www.ibyte.com.br/pcs-e-notebooks/perifericos, https://www.ibyte.com.br/hardware/placa-de-video and https://www.ibyte.com.br/casa-inteligente have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.ibyte.com.br/1122 and https://www.ibyte.com.br/1391 use the same meta description. A description written for each page earns more clicks.

  • 9 pages without an H1

    https://www.ibyte.com.br/1122, https://www.ibyte.com.br/notebooks, https://www.ibyte.com.br/pcs-e-notebooks/computador, https://www.ibyte.com.br/pcs-e-notebooks/perifericos/monitor, https://www.ibyte.com.br/audio-e-video/projetores and https://www.ibyte.com.br/pcs-e-notebooks/perifericos and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages slow to respond

    https://www.ibyte.com.br/pcs-e-notebooks/computador, https://www.ibyte.com.br/impressao-e-suprimentos/impressora, https://www.ibyte.com.br/pcs-e-notebooks/perifericos/monitor, https://www.ibyte.com.br/pcs-e-notebooks/perifericos, https://www.ibyte.com.br/energia/nobreak and https://www.ibyte.com.br/hardware/placa-de-video and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 81 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.

  • 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.

Best practices

1 to fixGoogle 9293
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistrations')”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    83 of 84 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: 23 customer or partner logos. 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 969 words of copy

    The homepage carries about 969 words of visible text.

3 checks passed
  • 1 short form

    A short form (0 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Meta Pixel and TikTok Pixel.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager and Meta Pixel (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.

  • 12 cookies set on arrival

    12

    Opening the homepage sets 12 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.

  • 16 other companies contacted

    Loading the homepage contacts 16 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 ibyte.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

Analytics
Google Tag Manager
Hosting
As266444 3l Cloud Internet Services Ltda Epp

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 51 issues on ibyte.com.br, including 27 speed issues, 2 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