Website review, no card needed

canon.com.br logo

canon.com.br website review

Visit site (opens in a new tab)Reviewed 28 October 202660 issues · 95 checks

This review found 60 issues worth fixing on canon.com.br, 27 of them high impact, across 95 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.0 s2.6 sMay 9Oct 242.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.0 s
May 16, 20262.9 s
May 23, 20263.0 s
May 30, 20262.9 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.8 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20262.8 s
Aug 22, 20262.7 s
Aug 29, 20262.7 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.6 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
131 ms99 msMay 9Oct 24127 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026104 ms
May 16, 2026104 ms
May 23, 2026105 ms
May 30, 2026105 ms
Jun 6, 2026106 ms
Jun 13, 2026107 ms
Jun 20, 2026105 ms
Jun 27, 2026104 ms
Jul 4, 2026103 ms
Jul 11, 2026103 ms
Jul 18, 2026103 ms
Jul 25, 2026104 ms
Aug 1, 2026104 ms
Aug 8, 2026105 ms
Aug 15, 2026106 ms
Aug 22, 2026109 ms
Aug 29, 2026113 ms
Sep 5, 2026117 ms
Sep 12, 2026119 ms
Sep 19, 2026120 ms
Sep 26, 2026120 ms
Oct 3, 2026121 ms
Oct 10, 2026123 ms
Oct 17, 2026125 ms
Oct 24, 2026127 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 canon.com.br (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. canon.com.br at 1.5 s1.5 s
  2. canon.com.br at 2.9 s2.9 s
  3. canon.com.br at 4.4 s4.4 s
  4. canon.com.br at 5.8 s5.8 s
  5. canon.com.br at 7.3 s7.3 s
  6. canon.com.br at 8.7 s8.7 s
  7. canon.com.br at 10.2 s10.2 s
  8. canon.com.br at 11.6 s11.6 s

Speed

16 to fix4
  • Use efficient cache lifetimes

    6.3 s · 10.0 MB

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

  • Reduce unused JavaScript

    10.5 s · 3.1 MB

    About 3.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.5 s faster on a phone.

  • Render-blocking requests

    5.5 s

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

  • YouTube adds 3.3 s

    3.3 s

    YouTube costs a phone 3.3 s of main-thread work and 2.9 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.

  • Reduce unused CSS

    2.5 s · 512 KiB

    About 512 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.5 s faster on a phone.

  • Font display

    1.7 s

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

  • Main-thread work: 13.9 s

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

  • Mobile performance score: 4

    4/100

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

  • Improve image delivery

    7.1 MB

    25 images could be 7.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 8 third-party services on the page

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

  • Minify JavaScript

    600 ms · 438 KiB

    438 KiB could be saved by minifying JavaScript.

  • Minify CSS

    600 ms · 114 KiB

    114 KiB could be saved by minifying CSS.

  • Google Tag Manager adds 577 ms

    577 ms

    Google Tag Manager costs a phone 577 ms of main-thread work and 436 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 590 ms. During a long task the page ignores taps.

  • Facebook adds 310 ms

    310 ms

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

  • nama.ai adds 74 ms

    74 ms

    nama.ai costs a phone 74 ms of main-thread work and 1.3 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.

  • Legacy JavaScript

    150 ms · 12 KiB

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

  • Document request latency

    50 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Phones get a much slower page than desktops

    Desktop scores 34 but mobile only 4. 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: 5 ms

    5 ms

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

Core Web Vitals

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

  • Real-user CLS: 0.65

    0.65

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

  • Largest Contentful Paint: 46.0 s

    46.0 s

    Your largest element takes 46.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “EOS R8 Mark II”.

  • Speed Index: 19.5 s

    19.5 s

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

  • Time to Interactive: 55.0 s

    55.0 s

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

  • Total Blocking Time: 2.9 s

    2.9 s

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

  • First Contentful Paint: 5.4 s

    5.4 s

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

  • Cumulative Layout Shift: 0.597

    0.597

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

  • Real-user LCP: 3.4 s

    3.4 s

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

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

    +21%

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 21 images without width and height

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

2 checks passed
  • Real-user INP: 143 ms

    143 ms

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

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

    -10%

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

Images and page weight

5 to fix18
  • Page weight: 15.0 MB in 160 requests

    15.0 MB

    Your homepage downloads 15.0 MB in 160 requests on a phone: images 8.7 MB (62), scripts 5.1 MB (48) and stylesheets 620 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 6 images over 500 KB

    6 images weigh 5.7 MB together. On a phone connection a single image that size takes seconds.

  • 14 images far larger than shown

    1.6 MB

    14 images are downloaded at several times the size a phone draws them, for example 1330x400imagembanner.png at 1,330 px wide, shown at 390 px. Resized copies would save about 1.6 MB.

  • 33 images in older formats

    33 images (8.5 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.

  • 9 images below the first screen load straight away

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

  • About 4.3 g of CO₂ per visit

    4.25 g

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

Accessibility

8 to fixGoogle 8388
  • Frames without titles

    3 frames have no title, so screen-reader users cannot tell what they contain.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • 41 images without alt text

    41 images have no alt text, which hurts accessibility and image search.

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

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

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

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

  • 20 links without text

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

  • 3 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

1 checks passed
  • 39 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 45 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 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

8 to fixGoogle 6760
  • 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 (5 characters)

    Your title is only 5 characters: “Canon”. 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 canonical URL

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

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

  • 16 links with vague text

    16 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 8 links crawlers can't follow

    8 links have no real href, so search engines can't follow them.

  • No X (Twitter) card tag

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

  • 72 internal links, 25 external

    The homepage links to 72 pages on canon.com.br and 25 external pages.

2 checks passed
  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.canon.com.br/sitemap.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.

  • No llms.txt

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

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

Other pages

2 to fix90
  • 12 pages without a meta description

    https://www.canon.com.br/para-voce/lentes-e-outros, https://www.canon.com.br/para-voce/impressoras-e-multifuncionais, https://www.canon.com.br/para-voce/suprimentos, https://www.canon.com.br/para-voce/biblioteca, https://www.canon.com.br/para-empresas/cinema/video/broadcast and https://www.canon.com.br/para-empresas/escritorio and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://www.canon.com.br/atendimento/contatos-e-suporte-tecnico, https://www.canon.com.br/atendimento/onde-comprar, https://www.canon.com.br/atendimento/imprensa and https://www.canon.com.br/atendimento/produtos-falsificados-e-mercado-cinza have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.canon.com.br/para-voce/lentes-e-outros, https://www.canon.com.br/para-voce/impressoras-e-multifuncionais, https://www.canon.com.br/para-voce/suprimentos and https://www.canon.com.br/para-empresas/cinema/video/broadcast took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7376
  • 2 broken images

    2 images failed to load on a phone, for example https://www.canon.com.br/files/img/frontend/product/pic-preview-v.png.

  • 6 third-party cookies

    6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    58 of 58 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: 15 testimonial or review blocks. 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 642 words of copy

    The homepage carries about 642 words of visible text.

3 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

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

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Hotjar 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.

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies, 1 of them by other companies (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.

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

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 canon.com.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 60 issues on canon.com.br, including 29 speed issues, 8 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