Website review, no card needed

opticasvision.co.cr logo

opticasvision.co.cr website review

Visit site (opens in a new tab)Reviewed 30 October 202639 issues · 85 checks

This review found 39 issues worth fixing on opticasvision.co.cr, 20 of them high impact, across 85 checks. The most urgent: google Tag Manager adds 2.0 s. 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.0 s901 msMay 9Oct 241.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.8 s
May 16, 20261.3 s
May 23, 20261.2 s
May 30, 20261.2 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.1 s
Aug 8, 20261.0 s
Aug 15, 20261.0 s
Aug 22, 20261.1 s
Aug 29, 20261.1 s
Sep 5, 20261.1 s
Sep 12, 20261.1 s
Sep 19, 20261.1 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
144 ms124 msMay 9Oct 24137 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026142 ms
May 16, 2026135 ms
May 23, 2026136 ms
May 30, 2026137 ms
Jun 6, 2026137 ms
Jun 13, 2026135 ms
Jun 20, 2026132 ms
Jun 27, 2026129 ms
Jul 4, 2026129 ms
Jul 11, 2026130 ms
Jul 18, 2026130 ms
Jul 25, 2026132 ms
Aug 1, 2026129 ms
Aug 8, 2026127 ms
Aug 15, 2026126 ms
Aug 22, 2026129 ms
Aug 29, 2026130 ms
Sep 5, 2026135 ms
Sep 12, 2026137 ms
Sep 19, 2026137 ms
Sep 26, 2026138 ms
Oct 3, 2026137 ms
Oct 10, 2026136 ms
Oct 17, 2026136 ms
Oct 24, 2026137 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 opticasvision.co.cr (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. opticasvision.co.cr at 0.9 s0.9 s
  2. opticasvision.co.cr at 1.9 s1.9 s
  3. opticasvision.co.cr at 2.8 s2.8 s
  4. opticasvision.co.cr at 3.8 s3.8 s
  5. opticasvision.co.cr at 4.7 s4.7 s
  6. opticasvision.co.cr at 5.6 s5.6 s
  7. opticasvision.co.cr at 6.6 s6.6 s
  8. opticasvision.co.cr at 7.5 s7.5 s

Speed

11 to fix18
  • Google Tag Manager adds 2.0 s

    2.0 s

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

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

  • Mobile performance score: 18

    18/100

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

  • Main-thread work: 5.5 s

    A phone's processor spends 5.5 s on main-thread work while loading, 2.8 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 Hotjar and others), adding 2.9 MB and 2.4 s of main-thread time.

  • Reduce unused JavaScript

    950 KiB

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

  • Reduce unused CSS

    300 ms · 51 KiB

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

  • 18 long tasks on the main thread

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

  • Use efficient cache lifetimes

    315 KiB

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

  • 2,854 HTML elements

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

  • Facebook adds 215 ms

    215 ms

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

    150 ms · 215 KiB

    14 images could be 215 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    50 ms

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

  • Legacy JavaScript

    13 KiB

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

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

    8 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 11.9 s

    11.9 s

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

  • Time to Interactive: 33.0 s

    33.0 s

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

  • Cumulative Layout Shift: 0.836

    0.836

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

  • Speed Index: 9.1 s

    9.1 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • Real-user INP: 216 ms

    216 ms

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

  • Real-user TTFB: 949 ms

    949 ms

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

  • 71 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -1%

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

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user CLS: 0.02

    0.02

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

  • Real-user FCP: 1.4 s

    1.4 s

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

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

    -32%

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

Images and page weight

2 to fix63
  • Page weight: 6.7 MB in 419 requests

    6.7 MB

    Your homepage downloads 6.7 MB in 419 requests on a phone: scripts 2.7 MB (73), images 2.7 MB (207) and other files 747 KiB (106). Under 2 MB keeps phones on slow connections fast.

  • 7 images below the first screen load straight away

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

  • 2 images in older formats

    2 images (100 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.9 g of CO₂ per visit

    1.89 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

10 to fixGoogle 7685
  • 1 button without a name

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

  • 39 text elements with low contrast

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

  • <svg> elements with an img or image role must have alternative text (3 elements)

    <svg> elements with an img or image role must have alternative text: 3 elements on the page fail this check, rated serious by axe-core.

  • 3 tap targets too small

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

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

  • 46 images without alt text

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

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

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

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 26 links without text

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

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • Headings skip levels

    Headings skip levels (h1 → h4), 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 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

Google 92100
  • 385 internal links, 19 external

    The homepage links to 385 pages on opticasvision.co.cr and 19 external pages.

8 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “Descubre lentes de sol y oftálmicos en Costa Rica 👁️ Marcas originales, asesoría experta y estilos para toda ocasión. …”.

  • One H1 headline

    Your main headline reads: “Encuentra los mejores lentes de sol, lentes oftálmicos y lentes de contacto | Ópticas Visión | Todas las marcas de lent…”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Ópticas Visión Costa Rica 👓 Venta de Lentes de sol y graduados”.

  • Canonical URL set

    The canonical URL is https://www.opticasvision.co.cr/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.opticasvision.co.cr/sitemap.xml.

AI search readiness

100
4 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.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (2,256 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.opticasvision.co.cr/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 1 page without a meta description

    https://www.opticasvision.co.cr/pages/examen-visual has 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 169 found) and read each the way a search engine does.

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 9687
  • 35 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://pro.fontawesome.com/releases/v5.10.0/css/all.css' from origin 'https://www.opticas…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 1,595 words of copy

    The homepage carries about 1,595 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.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 18 cookies set on arrival

    18

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

  • 27 other companies contacted

    Loading the homepage contacts 27 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 opticasvision.co.cr, 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
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on opticasvision.co.cr, including 20 speed 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