Website review, no card needed
flamingo.com.co website review
Visit site (opens in a new tab)Reviewed 26 October 202641 issues · 82 checks
This review found 41 issues worth fixing on flamingo.com.co, 19 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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
66D- #110,179 of 120,585 reviewed websitesbeats 7%
- #65,279 of 68,274 online storesbeats 4%
- #59,947 of 62,216 Shopify storesbeats 3%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.7 s |
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.4 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.5 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.5 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 245 ms |
| May 16, 2026 | 249 ms |
| May 23, 2026 | 251 ms |
| May 30, 2026 | 254 ms |
| Jun 6, 2026 | 260 ms |
| Jun 13, 2026 | 260 ms |
| Jun 20, 2026 | 258 ms |
| Jun 27, 2026 | 257 ms |
| Jul 4, 2026 | 251 ms |
| Jul 11, 2026 | 249 ms |
| Jul 18, 2026 | 248 ms |
| Jul 25, 2026 | 254 ms |
| Aug 1, 2026 | 291 ms |
| Aug 8, 2026 | 327 ms |
| Aug 15, 2026 | 359 ms |
| Aug 22, 2026 | 395 ms |
| Aug 29, 2026 | 403 ms |
| Sep 5, 2026 | 409 ms |
| Sep 12, 2026 | 410 ms |
| Sep 19, 2026 | 419 ms |
| Sep 26, 2026 | 434 ms |
| Oct 3, 2026 | 442 ms |
| Oct 10, 2026 | 451 ms |
| Oct 17, 2026 | 450 ms |
| Oct 24, 2026 | 451 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.1 s
2.2 s
3.3 s
4.5 s
5.6 s
6.7 s
7.8 s
8.9 s
Speed
Reduce unused JavaScript
6.0 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.0 s faster on a phone.
Use efficient cache lifetimes
2.5 s · 324 KiB18 files are served with short cache lifetimes, so returning visitors download them again (324 KiB).
Google Tag Manager adds 1.0 s
1.0 sGoogle Tag Manager costs a phone 1.0 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: 10.7 s
A phone's processor spends 10.7 s on main-thread work while loading, 6.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 36
36/100Your mobile performance score is 36 (desktop: 38). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
4,768 HTML elements
The page has 4,768 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
850 ms · 1.7 MB46 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 850 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Clarity and Shopify and others), adding 2.0 MB and 2.4 s of main-thread time.
Clarity adds 650 ms
650 msClarity costs a phone 650 ms of main-thread work and 29 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.
Render-blocking requests
650 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 520 ms. During a long task the page ignores taps.
Shopify adds 378 ms
378 msShopify costs a phone 378 ms of main-thread work and 518 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
150 ms · 39 KiBAbout 39 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Legacy JavaScript
150 ms · 12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
26 KiB26 KiB could be saved by minifying JavaScript.
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: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
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 INP: 530 ms
530 msReal visitors wait 530 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest Contentful Paint: 40.3 s
40.3 sYour largest element takes 40.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 41.3 s
41.3 sThe page becomes fully interactive after 41.3 s. Good is under 3.8 s.
Speed Index: 9.2 s
9.2 sVisually, the page fills in at 9.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
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.
Tap response (INP) got 82% slower for real visitors
+82%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 245 ms to 451 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.7 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 672 ms
672 msReal visitors wait 672 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Images and page weight
Page weight: 7.8 MB in 393 requests
7.8 MBYour homepage downloads 7.8 MB in 393 requests on a phone: images 3.9 MB (88), scripts 2.6 MB (96) and other files 1.0 MB (186). Under 2 MB keeps phones on slow connections fast.
6 images below the first screen load straight away
6 images further down the page (256 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.2 g of CO₂ per visit
2.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.20 g of CO₂e: 264.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
48 buttons without a name
48 buttons have no accessible name, so screen readers announce just “button”.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
48 links without text
48 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (18 characters)
Your title is only 18 characters: “Almacenes Flamingo”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
379 internal links, 20 external
The homepage links to 379 pages on flamingo.com.co and 20 external pages.
6 checks passed
Meta description: 121 characters
Your meta description is 121 characters: “Compra fácil y seguro en Flamingo.com.co: tecnología, hogar, moda y más. ¡Aprovecha nuestras promociones y paga a cuota…”.
One H1 headline
Your main headline reads: “Almacenes Flamingo”.
Canonical URL set
The canonical URL is https://www.flamingo.com.co/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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.flamingo.com.co/sitemap.xml.
AI search readiness
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 (1,896 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.flamingo.com.co/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without a meta description
https://www.flamingo.com.co/collections/celulares, https://www.flamingo.com.co/collections/accesorios-para-celulares, https://www.flamingo.com.co/collections/super-oferta-1, https://www.flamingo.com.co/collections/tecnologia, https://www.flamingo.com.co/collections/televisores and https://www.flamingo.com.co/collections/soportes and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://www.flamingo.com.co/collections/celulares, https://www.flamingo.com.co/collections/accesorios-para-celulares, https://www.flamingo.com.co/collections/super-oferta-1, https://www.flamingo.com.co/collections/tecnologia, https://www.flamingo.com.co/collections/televisores and https://www.flamingo.com.co/collections/soportes and 8 others 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 193 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.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
87 small tap targets
87 of 146 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 “Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'.”.
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.
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 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 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,348 words of copy
The homepage carries about 1,348 words of visible text.
2 checks passed
36 short forms
36 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (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.
28 cookies set on arrival
28Opening the homepage sets 28 cookies, 3 of them by other companies (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.
47 other companies contacted
Loading the homepage contacts 47 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 flamingo.com.co, 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 | Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 13 open roles
- Teams
- Centralized Insights and Analytics (4), Growth Marketing (3), Product Development (2), Legal (1)
- Job board
- greenhouse
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on flamingo.com.co, including 22 speed issues, 2 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.