Website review, no card needed
flexi.com.mx website review
Visit site (opens in a new tab)Reviewed 4 November 202644 issues · 68 checks
This review found 44 issues worth fixing on flexi.com.mx, 19 of them high impact, across 68 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
51FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 11.0 s |
| May 23, 2026 | 10.8 s |
| May 30, 2026 | 11.6 s |
| Jun 6, 2026 | 12.0 s |
| Jun 13, 2026 | 11.9 s |
| Jun 20, 2026 | 11.6 s |
| Jun 27, 2026 | 9.6 s |
| Jul 4, 2026 | 7.0 s |
| Jul 11, 2026 | 6.4 s |
| Jul 18, 2026 | 6.3 s |
| Jul 25, 2026 | 6.6 s |
| Aug 1, 2026 | 7.6 s |
| Aug 8, 2026 | 8.6 s |
| Aug 15, 2026 | 10.3 s |
| Aug 22, 2026 | 11.2 s |
| Aug 29, 2026 | 11.3 s |
| Sep 5, 2026 | 11.5 s |
| Sep 12, 2026 | 11.0 s |
| Sep 19, 2026 | 10.6 s |
| Sep 26, 2026 | 10.4 s |
| Oct 3, 2026 | 11.6 s |
| Oct 10, 2026 | 13.7 s |
| Oct 17, 2026 | 16.4 s |
| Oct 24, 2026 | 19.3 s |
| Oct 31, 2026 | 20.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 275 ms |
| May 23, 2026 | 272 ms |
| May 30, 2026 | 269 ms |
| Jun 6, 2026 | 264 ms |
| Jun 13, 2026 | 262 ms |
| Jun 20, 2026 | 260 ms |
| Jun 27, 2026 | 254 ms |
| Jul 4, 2026 | 253 ms |
| Jul 11, 2026 | 251 ms |
| Jul 18, 2026 | 251 ms |
| Jul 25, 2026 | 258 ms |
| Aug 1, 2026 | 269 ms |
| Aug 8, 2026 | 284 ms |
| Aug 15, 2026 | 303 ms |
| Aug 22, 2026 | 311 ms |
| Aug 29, 2026 | 317 ms |
| Sep 5, 2026 | 318 ms |
| Sep 12, 2026 | 320 ms |
| Sep 19, 2026 | 321 ms |
| Sep 26, 2026 | 318 ms |
| Oct 3, 2026 | 320 ms |
| Oct 10, 2026 | 321 ms |
| Oct 17, 2026 | 326 ms |
| Oct 24, 2026 | 330 ms |
| Oct 31, 2026 | 329 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.3 s
2.5 s
3.8 s
5.0 s
6.3 s
7.5 s
8.8 s
10.1 s
Speed
Reduce unused JavaScript
5.3 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 454 KiB81 files are served with short cache lifetimes, so returning visitors download them again (454 KiB).
Mobile performance score: 14
14/100Your mobile performance score is 14. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 3.4 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 TikTok and others), adding 1.7 MB and 1.3 s of main-thread time.
Google Tag Manager adds 618 ms
618 msGoogle Tag Manager costs a phone 618 ms of main-thread work and 810 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
450 ms · 151 KiBAbout 151 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Facebook adds 261 ms
261 msFacebook costs a phone 261 ms of main-thread work and 352 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.
TikTok adds 253 ms
253 msTikTok costs a phone 253 ms of main-thread work and 289 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.
Improve image delivery
200 ms · 81 KiB6 images could be 81 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.
Minify JavaScript
150 ms · 5 KiB5 KiB could be saved by minifying JavaScript.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
48 KiBPolyfills for old browsers add 48 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: 1 ms
1 msYour server sent the HTML in 1 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 LCP: 20.2 s
20.2 sReal visitors wait 20.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 2.18
2.18For real visitors the layout shifts by 2.18 (75th percentile). Good is under 0.1.
Real-user FCP: 18.5 s
18.5 sReal visitors see the first content after 18.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 17.4 s
17.4 sReal visitors wait 17.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 2.399
2.399The layout shifts by 2.399 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 22.7 s
22.7 sYour largest element takes 22.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “20261012-OI26-FULL”. Most of its time is resource load delay (9.7 s).
Speed Index: 19.6 s
19.6 sVisually, the page fills in at 19.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 22.7 s
22.7 sThe page becomes fully interactive after 22.7 s. Good is under 3.8 s.
Total Blocking Time: 1.6 s
1.6 sScripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.
Real-user INP: 349 ms
349 msReal visitors wait 349 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 275 ms to 329 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 83% slower for real visitors
+83%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 11.0 s to 20.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
1 checks passed
First Contentful Paint: 0.8 s
0.8 sThe first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 3.1 MB in 186 requests
3.1 MBYour homepage downloads 3.1 MB in 186 requests on a phone: scripts 2.3 MB (83), images 399 KiB (35) and fonts 217 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.88 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.88 g of CO₂e: 105.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
1 checks passed
7 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 9 WCAG 2.2 A/AA and best-practice rules on the phone render: 7 passed and 2 failed. 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 (18 characters)
Your title is only 18 characters: “Storefront - Flexi”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
2 checks passed
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.flexi.com.mx/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.flexi.com.mx/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.
1 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.
Best practices
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 0 words
The homepage has only about 0 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
3 other companies contacted
Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 flexi.com.mx, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Akamai
Hiring
- Hiring
- 4 open roles
- Teams
- Finance & HR (3)
- Job board
- bamboohr
- Careers page
- flexi.bamboohr.com/careers (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on flexi.com.mx, including 24 speed issues, 9 SEO issues and 6 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.