Website review, no card needed

eltunel.com.uy logo

eltunel.com.uy website review

Visit site (opens in a new tab)Reviewed 19 October 202643 issues · 85 checks

This review found 43 issues worth fixing on eltunel.com.uy, 12 of them high impact, across 85 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.8 sMay 2Oct 172.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.9 s
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, 20261.9 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.0 s
Sep 5, 20262.0 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
212 ms154 msMay 2Oct 17196 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026161 ms
May 9, 2026165 ms
May 16, 2026174 ms
May 23, 2026186 ms
May 30, 2026192 ms
Jun 6, 2026195 ms
Jun 13, 2026196 ms
Jun 20, 2026196 ms
Jun 27, 2026196 ms
Jul 4, 2026201 ms
Jul 11, 2026201 ms
Jul 18, 2026198 ms
Jul 25, 2026200 ms
Aug 1, 2026199 ms
Aug 8, 2026202 ms
Aug 15, 2026205 ms
Aug 22, 2026205 ms
Aug 29, 2026204 ms
Sep 5, 2026201 ms
Sep 12, 2026200 ms
Sep 19, 2026198 ms
Sep 26, 2026197 ms
Oct 3, 2026199 ms
Oct 10, 2026198 ms
Oct 17, 2026196 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 eltunel.com.uy (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eltunel.com.uy at 0.5 s0.5 s
  2. eltunel.com.uy at 1.0 s1.0 s
  3. eltunel.com.uy at 1.6 s1.6 s
  4. eltunel.com.uy at 2.1 s2.1 s
  5. eltunel.com.uy at 2.6 s2.6 s
  6. eltunel.com.uy at 3.1 s3.1 s
  7. eltunel.com.uy at 3.7 s3.7 s
  8. eltunel.com.uy at 4.2 s4.2 s

Speed

11 to fix52
  • Render-blocking requests

    4.3 s

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

  • 4,343 HTML elements

    The page has 4,343 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 (fcdn.app, Google Tag Manager and Facebook and others), adding 3.4 MB and 1.3 s of main-thread time.

  • Improve image delivery

    450 ms · 901 KiB

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

  • Reduce unused JavaScript

    750 ms · 521 KiB

    About 521 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52 (desktop: 58). Pages that score under 90 lose visitors before the first paint.

  • fcdn.app adds 605 ms

    605 ms

    fcdn.app costs a phone 605 ms of main-thread work and 2.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.

  • Google Tag Manager adds 461 ms

    461 ms

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

    300 ms · 43 KiB

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

  • Main-thread work: 3.1 s

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

  • Google Fonts adds 0 ms

    0 ms

    Google Fonts costs a phone 0 ms of main-thread work and 359 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.

  • Use efficient cache lifetimes

    231 KiB

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

  • 12 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    12 KiB

    Polyfills for old browsers add 12 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: 41 ms

    41 ms

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

Core Web Vitals

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

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

  • Largest Contentful Paint: 6.4 s

    6.4 s

    Your largest element takes 6.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Especial Nutrición hasta 40% off”.

  • Time to Interactive: 13.7 s

    13.7 s

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

  • Real-user INP: 226 ms

    226 ms

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

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

    +21%

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

  • Speed Index: 5.4 s

    5.4 s

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

  • Total Blocking Time: 456 ms

    456 ms

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

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

    0.04

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 729 ms

    729 ms

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

  • Cumulative Layout Shift: 0.04

    0.04

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

Images and page weight

2 to fix75
  • Page weight: 3.4 MB in 185 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 185 requests on a phone: images 1.8 MB (145), scripts 1.2 MB (16) and fonts 373 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    9 KiB

    1 image is downloaded at several times the size a phone draws it, for example image-a8g21la8g21la8g2.jpg at 800 px wide, shown at 243 px. Resized copies would save about 9 KiB.

  • 9 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    0.97 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 116.8 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

10 to fixGoogle 7587
  • 32 buttons without a name

    32 buttons have no accessible name, so screen readers announce just “button”.

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

  • 4 tap targets too small

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

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 10 links without text

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

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

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

2 checks passed
  • Every image has alt text

    All 330 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

1 to fixGoogle 10096
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 331 internal links, 7 external

    The homepage links to 331 pages on eltunel.com.uy and 7 external pages.

7 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Comprá Online en tu cadena de Farmacias en Uruguay, medicamentos, dermocosmética, nutrición, fragancias, artículos para…”.

  • One H1 headline

    Your main headline reads: “Farmacia El túnel”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “Farmacia El Túnel - Tienda Online”.

  • Canonical URL set

    The canonical URL is https://eltunel.com.uy/.

  • 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://eltunel.com.uy/sitemap.

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

  • llms.txt published

    The site publishes https://eltunel.com.uy/llms.txt (6 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix65
  • 1 page points its canonical at the homepage

    https://eltunel.com.uy/salir 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://eltunel.com.uy/catalogo is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 7 pages share 2 titles

    / and https://eltunel.com.uy/salir all use the title “Farmacia El Túnel - Tienda Online”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 12 pages without a meta description

    https://eltunel.com.uy/mi-cuenta, https://eltunel.com.uy/mi-cuenta/mis-datos, https://eltunel.com.uy/mi-cuenta/direcciones, https://eltunel.com.uy/mi-cuenta/compras, https://eltunel.com.uy/mi-cuenta/wish-list and https://eltunel.com.uy/cosmetica/maquillaje and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages without an H1

    https://eltunel.com.uy/mi-cuenta, https://eltunel.com.uy/mi-cuenta/mis-datos, https://eltunel.com.uy/mi-cuenta/direcciones, https://eltunel.com.uy/mi-cuenta/compras and https://eltunel.com.uy/mi-cuenta/wish-list 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 148 found) and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 29 small tap targets

    29 of 110 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 manifest at 'https://f.fcdn.app/assets/manifest.json' from origin 'https://eltunel.com.uy' has been blocked b…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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 670 words of copy

    The homepage carries about 670 words of visible text.

4 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Call center 2406 80 96”.

  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage, asking for an email.

  • 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
  • 4 trackers load before any consent

    4

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

  • 7 cookies set on arrival

    7

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

  • 14 other companies contacted

    Loading the homepage contacts 14 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 eltunel.com.uy, 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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on eltunel.com.uy, including 19 speed issues, 1 SEO issue and 2 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