Website review, no card needed
farmaciastkl.com website review
Visit site (opens in a new tab)Reviewed 19 October 202661 issues · 98 checks
This review found 61 issues worth fixing on farmaciastkl.com, 24 of them high impact, across 98 checks. The most urgent: reduce initial server response time. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
55FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 3.8 s |
| May 2, 2026 | 3.8 s |
| May 9, 2026 | 3.7 s |
| May 16, 2026 | 3.8 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 3.9 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 3.9 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 4.0 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.1 s |
| Sep 12, 2026 | 4.0 s |
| Sep 19, 2026 | 4.0 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 4.1 s |
| Oct 10, 2026 | 4.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 180 ms |
| May 2, 2026 | 175 ms |
| May 9, 2026 | 174 ms |
| May 16, 2026 | 178 ms |
| May 23, 2026 | 182 ms |
| May 30, 2026 | 187 ms |
| Jun 6, 2026 | 184 ms |
| Jun 13, 2026 | 188 ms |
| Jun 20, 2026 | 187 ms |
| Jun 27, 2026 | 184 ms |
| Jul 4, 2026 | 188 ms |
| Jul 11, 2026 | 184 ms |
| Jul 18, 2026 | 187 ms |
| Jul 25, 2026 | 189 ms |
| Aug 1, 2026 | 185 ms |
| Aug 8, 2026 | 185 ms |
| Aug 15, 2026 | 185 ms |
| Aug 22, 2026 | 182 ms |
| Aug 29, 2026 | 184 ms |
| Sep 5, 2026 | 188 ms |
| Sep 12, 2026 | 188 ms |
| Sep 19, 2026 | 190 ms |
| Sep 26, 2026 | 185 ms |
| Oct 3, 2026 | 189 ms |
| Oct 10, 2026 | 183 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
How it loaded on a phone
1.5 s
3.0 s
4.5 s
6.0 s
7.5 s
9.0 s
10.5 s
12.1 s
Speed
Reduce initial server response time
5.1 sReduce initial server response time. Google estimates savings of 5.1 s on a phone.
Document request latency
5.0 sThe HTML itself could arrive about 5.0 s sooner: redirects, a slow server response or missing compression delay everything after it.
Render-blocking requests
2.0 s25 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.0 s.
Mobile performance score: 40
40/100Your mobile performance score is 40 (desktop: 32). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Server response: 5.2 s
5.2 sYour server takes 5.2 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Main-thread work: 4.5 s
A phone's processor spends 4.5 s on main-thread work while loading, 2.9 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 (vtexassets.com, Google Tag Manager and Google CDN and others), adding 3.0 MB and 2.4 s of main-thread time.
Reduce unused JavaScript
150 ms · 896 KiBAbout 896 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
700 ms · 297 KiB34 files are served with short cache lifetimes, so returning visitors download them again (297 KiB).
vtexassets.com adds 868 ms
868 msvtexassets.com costs a phone 868 ms of main-thread work and 1.2 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 803 ms
803 msGoogle Tag Manager costs a phone 803 ms of main-thread work and 839 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.
Google CDN adds 368 ms
368 msGoogle CDN costs a phone 368 ms of main-thread work and 736 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 351 ms. During a long task the page ignores taps.
1,721 HTML elements
The page has 1,721 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
200 ms · 59 KiB10 images could be 59 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Legacy JavaScript
200 ms · 47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
48 KiB48 KiB could be saved by minifying JavaScript.
Reduce unused CSS
33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page.
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.
Core Web Vitals
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 FCP: 4.0 s
4.0 sReal visitors see the first content after 4.0 s (75th percentile). Good is under 1.8 s.
Speed Index: 13.9 s
13.9 sVisually, the page fills in at 13.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 21.8 s
21.8 sThe page becomes fully interactive after 21.8 s. Good is under 3.8 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is time to first byte (5.2 s).
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 219 ms
219 msReal visitors wait 219 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.22
0.22For real visitors the layout shifts by 0.22 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
34 images without width and height
34 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.151
0.151The layout shifts by 0.151 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 180 ms to 183 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 3.8 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 3.7 MB in 190 requests
3.7 MBYour homepage downloads 3.7 MB in 190 requests on a phone: scripts 2.6 MB (56), other files 376 KiB (44) and images 268 KiB (54). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.05 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.05 g of CO₂e: 126.1 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
19 text elements with low contrast
19 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (23 elements)
All page content should be contained by landmarks: 23 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.
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.
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.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
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 63 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 11 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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 (13 characters)
Your title is only 13 characters: “Farmacias TKL”. Between 30 and 65 characters leaves room to say what you do and for whom.
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 (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.MiTienda.com.br/sitemap.xml, so Google discovers your pages only by following links.
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.
59 internal links, 6 external
The homepage links to 59 pages on farmaciastkl.com and 6 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://www.farmaciastkl.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
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.farmaciastkl.com/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 (414 words), so crawlers that don't run JavaScript still read it.
Other pages
3 linked pages hidden from search
https://www.farmaciastkl.com/OFERTAS, https://www.farmaciastkl.com/332 and https://www.farmaciastkl.com/139 are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
/ and https://www.farmaciastkl.com/mediosdepago all use the title “Farmacias TKL”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://www.farmaciastkl.com/OFERTAS, https://www.farmaciastkl.com/332, https://www.farmaciastkl.com/139, https://www.farmaciastkl.com/mediosdepago, https://www.farmaciastkl.com/sucursales and https://www.farmaciastkl.com/dermocosmetica/limpieza have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.farmaciastkl.com/mediosdepago and https://www.farmaciastkl.com/sucursales have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.farmaciastkl.com/mediosdepago and https://www.farmaciastkl.com/sucursales have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
1 page slow to respond
https://www.farmaciastkl.com/cuidado-de-salud took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 49 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was 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.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 219 words
The homepage has only about 219 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Privacy and tracking
5 trackers load before any consent
5Before 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
18Opening 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 farmaciastkl.com, 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 61 issues on farmaciastkl.com, including 27 speed issues, 7 SEO issues and 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.