Website review, no card needed
florayfauna.pe website review
Visit site (opens in a new tab)Reviewed 19 October 202660 issues · 98 checks
This review found 60 issues worth fixing on florayfauna.pe, 26 of them high impact, across 98 checks. The most urgent: render-blocking requests. 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
56FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 3.6 s |
| May 2, 2026 | 3.6 s |
| May 9, 2026 | 3.6 s |
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.7 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.6 s |
| Sep 26, 2026 | 3.6 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 277 ms |
| May 2, 2026 | 273 ms |
| May 9, 2026 | 260 ms |
| May 16, 2026 | 260 ms |
| May 23, 2026 | 244 ms |
| May 30, 2026 | 239 ms |
| Jun 6, 2026 | 239 ms |
| Jun 13, 2026 | 249 ms |
| Jun 20, 2026 | 255 ms |
| Jun 27, 2026 | 256 ms |
| Jul 4, 2026 | 255 ms |
| Jul 11, 2026 | 249 ms |
| Jul 18, 2026 | 270 ms |
| Jul 25, 2026 | 265 ms |
| Aug 1, 2026 | 267 ms |
| Aug 8, 2026 | 266 ms |
| Aug 15, 2026 | 234 ms |
| Aug 22, 2026 | 229 ms |
| Aug 29, 2026 | 227 ms |
| Sep 5, 2026 | 227 ms |
| Sep 12, 2026 | 234 ms |
| Sep 19, 2026 | 237 ms |
| Sep 26, 2026 | 238 ms |
| Oct 3, 2026 | 234 ms |
| Oct 10, 2026 | 228 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
0.9 s
1.7 s
2.6 s
3.5 s
4.4 s
5.2 s
6.1 s
7.0 s
Speed
Render-blocking requests
4.0 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.0 s.
Reduce unused CSS
1.8 s · 350 KiBAbout 350 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.
vtexassets.com adds 1.1 s
1.1 svtexassets.com costs a phone 1.1 s of main-thread work and 2.5 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 initial server response time
1.3 sReduce initial server response time. Google estimates savings of 1.3 s on a phone.
Document request latency
1.3 sThe HTML itself could arrive about 1.3 s sooner: redirects, a slow server response or missing compression delay everything after it.
Mobile performance score: 35
35/100Your mobile performance score is 35 (desktop: 43). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.3 s
A phone's processor spends 6.3 s on main-thread work while loading, 3.5 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 CDN and Google Tag Manager and others), adding 5.6 MB and 2.7 s of main-thread time.
Reduce unused JavaScript
150 ms · 1.5 MBAbout 1.5 MB 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
150 ms · 946 KiB34 files are served with short cache lifetimes, so returning visitors download them again (946 KiB).
Google CDN adds 504 ms
504 msGoogle CDN costs a phone 504 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 485 ms
485 msGoogle Tag Manager costs a phone 485 ms of main-thread work and 485 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
459 KiB9 images could be 459 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Facebook adds 261 ms
261 msFacebook costs a phone 261 ms of main-thread work and 221 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 276 ms. During a long task the page ignores taps.
Google Maps adds 190 ms
190 msGoogle Maps costs a phone 190 ms of main-thread work and 383 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.
1,554 HTML elements
The page has 1,554 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 1.4 s
1.4 sYour server takes 1.4 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Legacy JavaScript
150 ms · 47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 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).
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 KiB4 KiB could be saved by minifying JavaScript.
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 CLS: 0.28
0.28For real visitors the layout shifts by 0.28 (75th percentile). Good is under 0.1.
Real-user FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Time to Interactive: 27.8 s
27.8 sThe page becomes fully interactive after 27.8 s. Good is under 3.8 s.
Largest Contentful Paint: 8.0 s
8.0 sYour largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 5.6 s
5.6 sThe first text or image appears after 5.6 s on a phone. Good is under 1.8 s.
Speed Index: 10.7 s
10.7 sVisually, the page fills in at 10.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 985 ms
985 msScripts block taps and scrolling for 985 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.2 s
3.2 sReal visitors wait 3.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 277 ms
277 msReal visitors wait 277 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 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.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Tap response (INP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 277 ms to 228 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 4.5 MB in 149 requests
4.5 MBYour homepage downloads 4.5 MB in 149 requests on a phone: scripts 2.6 MB (55), images 933 KiB (31) and other files 383 KiB (50). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
logo-web-1830.svg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
5 images far larger than shown
321 KiB5 images are downloaded at several times the size a phone draws them, for example 268baf71-0dfb-4ead-82cf-2b15172413a0___76dbd898dbbbdd7baeab4 at 1,594 px wide, shown at 390 px. Resized copies would save about 321 KiB.
5 images in older formats
5 images (335 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.
1 image below the first screen load straight away
1 image further down the page (37 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.28 g of CO₂e: 153.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 buttons without a name
6 buttons have no accessible name, so screen readers announce just “button”.
38 tap targets too small
38 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
7 elements hidden from screen readers can still receive keyboard focus.
Interactive controls must not be nested (6 elements)
Interactive controls must not be nested: 6 elements on the page fail this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 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.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
11 form fields without a label
11 form fields have no label, so screen readers announce an empty box and autofill guesses.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (13 elements).
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 12 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (77 characters)
Your title is 77 characters, so Google will cut it off around 60: “Flora & Fauna - Supermercado Saludable ¡Compra online recíbelos el mismo día!”.
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, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
42 internal links, 2 external
The homepage links to 42 pages on florayfauna.pe and 2 external pages.
4 checks passed
Meta description: 93 characters
Your meta description is 93 characters: “Descubre cómo nuestros miles de productos saludables y orgánicos, pueden transformar tu vida.”.
Canonical URL set
The canonical URL is https://www.florayfauna.pe/.
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.florayfauna.pe/sitemap.xml.
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.florayfauna.pe/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 (372 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages share a title
/, https://www.florayfauna.pe/premios-flora-fauna and https://www.florayfauna.pe/filtro-ingredientes-saludables all use the title “Flora & Fauna - Supermercado Saludable ¡Compra online recíbelos el mi…”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages share a meta description
https://www.florayfauna.pe/promociones, https://www.florayfauna.pe/premios-flora-fauna, https://www.florayfauna.pe/filtro-ingredientes-saludables, https://www.florayfauna.pe/congelados, https://www.florayfauna.pe/hogar-y-limpieza and https://www.florayfauna.pe/frescos and 2 others use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.florayfauna.pe/premios-flora-fauna and https://www.florayfauna.pe/filtro-ingredientes-saludables have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.florayfauna.pe/agua-de-coco-aqua-330ml/p has 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.
2 pages slow to respond
https://www.florayfauna.pe/promociones and https://www.florayfauna.pe/filtro-ingredientes-saludables took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 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.
Every page has a meta description
All 15 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 15 pages that loaded have a <title>.
Best practices
49 small tap targets
49 of 102 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.
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.
Only about 243 words
The homepage has only about 243 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.
3 checks passed
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
19 cookies set on arrival
19Opening the homepage sets 19 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.
29 other companies contacted
Loading the homepage contacts 29 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 florayfauna.pe, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- React
- 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 60 issues on florayfauna.pe, including 30 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.