Website review, no card needed

oticagrandvision.com.br logo

oticagrandvision.com.br website review

Visit site (opens in a new tab)Reviewed 31 October 202662 issues · 101 checks

This review found 62 issues worth fixing on oticagrandvision.com.br, 31 of them high impact, across 101 checks. The most urgent: reduce unused JavaScript. 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.4 s2.7 sMay 9Oct 245.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.1 s
May 16, 20263.1 s
May 23, 20263.1 s
May 30, 20263.1 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Jun 20, 20263.0 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.3 s
Jul 25, 20263.5 s
Aug 1, 20263.8 s
Aug 8, 20263.9 s
Aug 15, 20263.9 s
Aug 22, 20263.9 s
Aug 29, 20263.8 s
Sep 5, 20263.7 s
Sep 12, 20263.8 s
Sep 19, 20263.8 s
Sep 26, 20263.9 s
Oct 3, 20264.2 s
Oct 10, 20264.4 s
Oct 17, 20264.7 s
Oct 24, 20265.1 s
Real-visitor tap response (INP)75th percentile, phones
394 ms238 msMay 9Oct 24371 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026259 ms
May 16, 2026256 ms
May 23, 2026257 ms
May 30, 2026261 ms
Jun 6, 2026259 ms
Jun 13, 2026265 ms
Jun 20, 2026263 ms
Jun 27, 2026273 ms
Jul 4, 2026279 ms
Jul 11, 2026274 ms
Jul 18, 2026270 ms
Jul 25, 2026265 ms
Aug 1, 2026271 ms
Aug 8, 2026278 ms
Aug 15, 2026286 ms
Aug 22, 2026290 ms
Aug 29, 2026286 ms
Sep 5, 2026287 ms
Sep 12, 2026294 ms
Sep 19, 2026323 ms
Sep 26, 2026355 ms
Oct 3, 2026374 ms
Oct 10, 2026376 ms
Oct 17, 2026373 ms
Oct 24, 2026371 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 oticagrandvision.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. oticagrandvision.com.br at 2.0 s2.0 s
  2. oticagrandvision.com.br at 4.1 s4.1 s
  3. oticagrandvision.com.br at 6.1 s6.1 s
  4. oticagrandvision.com.br at 8.2 s8.2 s
  5. oticagrandvision.com.br at 10.2 s10.2 s
  6. oticagrandvision.com.br at 12.3 s12.3 s
  7. oticagrandvision.com.br at 14.3 s14.3 s
  8. oticagrandvision.com.br at 16.4 s16.4 s

Speed

17 to fix26
  • Reduce unused JavaScript

    12.2 s · 1.8 MB

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

  • Use efficient cache lifetimes

    4.5 s · 774 KiB

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

  • Reduce initial server response time

    4.2 s

    Reduce initial server response time. Google estimates savings of 4.2 s on a phone.

  • Document request latency

    4.2 s

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

  • vtexassets.com adds 1.8 s

    1.8 s

    vtexassets.com costs a phone 1.8 s of main-thread work and 1.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.

  • Render-blocking requests

    1.7 s

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

  • Google Tag Manager adds 1.3 s

    1.3 s

    Google Tag Manager costs a phone 1.3 s of main-thread work and 1.1 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.

  • Main-thread work: 11.0 s

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

  • Mobile performance score: 26

    26/100

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

  • Server response: 4.3 s

    4.3 s

    Your server takes 4.3 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • 8 third-party services on the page

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

  • Reduce unused CSS

    750 ms · 129 KiB

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

  • Google CDN adds 652 ms

    652 ms

    Google CDN costs a phone 652 ms of main-thread work and 1.5 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

    350 ms · 66 KiB

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

  • 20 long tasks on the main thread

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

  • 2,934 HTML elements

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

  • Facebook adds 255 ms

    255 ms

    Facebook costs a phone 255 ms of main-thread work and 269 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

    40 KiB

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

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

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

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: 10.3 s

    10.3 s

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

  • Real-user INP: 1.1 s

    1.1 s

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

  • Real-user CLS: 0.36

    0.36

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

  • Real-user FCP: 10.1 s

    10.1 s

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

  • Largest Contentful Paint: 43.8 s

    43.8 s

    Your largest element takes 43.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “X 15% OFF NA SUA PRIMEIRA COMPRA PREENCHA OS DADOS E RECEBA…”.

  • Speed Index: 26.3 s

    26.3 s

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

  • Time to Interactive: 43.9 s

    43.9 s

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

  • First Contentful Paint: 7.4 s

    7.4 s

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

  • Total Blocking Time: 2.6 s

    2.6 s

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

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

    +44%

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

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

    +58%

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

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

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

    0.039

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

Images and page weight

1 to fix70
  • Page weight: 7.5 MB in 235 requests

    7.5 MB

    Your homepage downloads 7.5 MB in 235 requests on a phone: scripts 4.4 MB (95), HTML 1.0 MB (5) and fonts 840 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (27 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.14 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

11 to fixGoogle 8086
  • 20 tap targets too small

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

  • 5 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Orphan list items

    Some list items are not inside a list.

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

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

  • 4 form fields without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

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

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

  • ARIA role should be appropriate for the element (1 element)

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

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

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

2 checks passed
  • Every image has alt text

    All 144 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

5 to fixGoogle 9277
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is long (414 characters)

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

  • Structured data has 2 problems

    Structured data found (ItemList and WebSite) but with 2 problems, 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.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 246 internal links, 0 external

    The homepage links to 246 pages on oticagrandvision.com.br and 0 external pages.

4 checks passed
  • Title: 65 characters

    Your title is a healthy 65 characters: “GrandVision by Fototica - Óculos de Sol, Grau e Lentes de Contato”.

  • Canonical URL set

    The canonical URL is https://www.oticagrandvision.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.oticagrandvision.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.oticagrandvision.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 (1,106 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix62
  • 6 linked pages are broken

    Your homepage links to https://www.oticagrandvision.com.br/armacao/havana, https://www.oticagrandvision.com.br/armacao/preto, https://www.oticagrandvision.com.br/armacao/transparente, https://www.oticagrandvision.com.br/armacao/burberry, https://www.oticagrandvision.com.br/armacao/coach and https://www.oticagrandvision.com.br/armacao/ea, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages share a title

    / and https://www.oticagrandvision.com.br/contatologia all use the title “GrandVision by Fototica - Óculos de Sol, Grau e Lentes de Contato”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 5 pages share a meta description

    https://www.oticagrandvision.com.br/experimentar-oculos-online, https://www.oticagrandvision.com.br/nossas-lojas, https://www.oticagrandvision.com.br/contatologia, https://www.oticagrandvision.com.br/novidades and https://www.oticagrandvision.com.br/par-completo use the same meta description. A description written for each page earns more clicks.

  • 3 pages without an H1

    https://www.oticagrandvision.com.br/experimentar-oculos-online, https://www.oticagrandvision.com.br/nossas-lojas and https://www.oticagrandvision.com.br/contatologia 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 137 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.

  • Every page has a meta description

    All 9 pages that loaded have a meta description.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 9 pages that loaded have a <title>.

Best practices

5 to fix69
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187148276&Ver=2&mid=6082234d-0d80-47a8-bbf9-47f6c722986c&bo=1&sid=fafcd0e0d4fa11f1be29b1e77ac29e7c&vid=fafcf530d4fa11f1820e2d8f2c66e772&vids=1&msclkid=N&pi=918639831&l.

  • 13 small tap targets

    13 of 39 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 5 JavaScript errors while loading

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix40
  • 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: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No form on the homepage

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

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

    The homepage carries about 655 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

Privacy and tracking

  • 9 trackers load before any consent

    9

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

  • 35 cookies set on arrival

    35

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

  • 46 other companies contacted

    Loading the homepage contacts 46 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 oticagrandvision.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

Hosting
CloudFront

Company

Founded
1920
Headquarters
São Paulo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 62 issues on oticagrandvision.com.br, including 31 speed issues, 5 SEO issues and 4 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