Website review, no card needed

ftepeyac.com.mx logo

ftepeyac.com.mx website review

Visit site (opens in a new tab)Reviewed 31 October 202645 issues · 89 checks

This review found 45 issues worth fixing on ftepeyac.com.mx, 24 of them high impact, across 89 checks. The most urgent: use efficient cache lifetimes. 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
4.6 s4.3 sMay 9Oct 244.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.5 s
May 16, 20264.4 s
May 23, 20264.3 s
May 30, 20264.3 s
Jun 6, 20264.3 s
Jun 13, 20264.4 s
Jun 20, 20264.5 s
Jun 27, 20264.5 s
Jul 4, 20264.5 s
Jul 11, 20264.5 s
Jul 18, 20264.4 s
Jul 25, 20264.3 s
Aug 1, 20264.3 s
Aug 8, 20264.3 s
Aug 15, 20264.3 s
Aug 22, 20264.4 s
Aug 29, 20264.3 s
Sep 5, 20264.3 s
Sep 12, 20264.3 s
Sep 19, 20264.4 s
Sep 26, 20264.4 s
Oct 3, 20264.3 s
Oct 10, 20264.4 s
Oct 17, 20264.4 s
Oct 24, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
222 ms134 msMay 9Oct 24186 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026146 ms
May 16, 2026144 ms
May 23, 2026152 ms
May 30, 2026165 ms
Jun 6, 2026166 ms
Jun 13, 2026171 ms
Jun 20, 2026169 ms
Jun 27, 2026166 ms
Jul 4, 2026171 ms
Jul 11, 2026169 ms
Jul 18, 2026165 ms
Jul 25, 2026165 ms
Aug 1, 2026169 ms
Aug 8, 2026169 ms
Aug 15, 2026173 ms
Aug 22, 2026180 ms
Aug 29, 2026187 ms
Sep 5, 2026198 ms
Sep 12, 2026209 ms
Sep 19, 2026212 ms
Sep 26, 2026207 ms
Oct 3, 2026201 ms
Oct 10, 2026193 ms
Oct 17, 2026188 ms
Oct 24, 2026186 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 ftepeyac.com.mx (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ftepeyac.com.mx at 1.5 s1.5 s
  2. ftepeyac.com.mx at 2.9 s2.9 s
  3. ftepeyac.com.mx at 4.4 s4.4 s
  4. ftepeyac.com.mx at 5.9 s5.9 s
  5. ftepeyac.com.mx at 7.4 s7.4 s
  6. ftepeyac.com.mx at 8.8 s8.8 s
  7. ftepeyac.com.mx at 10.3 s10.3 s
  8. ftepeyac.com.mx at 11.8 s11.8 s

Speed

13 to fix27
  • Use efficient cache lifetimes

    20.3 s · 4.9 MB

    97 files are served with short cache lifetimes, so returning visitors download them again (4.9 MB).

  • Render-blocking requests

    13.1 s

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

  • Reduce unused CSS

    9.3 s · 1.8 MB

    About 1.8 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 9.3 s faster on a phone.

  • Reduce unused JavaScript

    8.1 s · 1.5 MB

    About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.1 s faster on a phone.

  • Google Tag Manager adds 1.5 s

    1.5 s

    Google Tag Manager costs a phone 1.5 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.

  • amcharts.com adds 1.1 s

    1.1 s

    amcharts.com costs a phone 1.1 s of main-thread work and 350 KiB 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.

  • Mobile performance score: 27

    27/100

    Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 6.2 s

    A phone's processor spends 6.2 s on main-thread work while loading, 3.3 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, amcharts.com and Facebook and others), adding 1.9 MB and 3.0 s of main-thread time.

  • Improve image delivery

    850 ms · 171 KiB

    2 images could be 171 KiB 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.

  • 20 long tasks on the main thread

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

  • Facebook adds 329 ms

    329 ms

    Facebook costs a phone 329 ms of main-thread work and 251 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.

  • 2,031 HTML elements

    The page has 2,031 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Document request latency

    234 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Font display

    200 ms

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

  • Legacy JavaScript

    150 ms · 43 KiB

    Polyfills for old browsers add 43 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    29 KiB

    29 KiB could be saved by minifying JavaScript.

  • Minify CSS

    25 KiB

    25 KiB could be saved by minifying CSS.

  • 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: 332 ms

    332 ms

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

Core Web Vitals

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

  • Real-user LCP: 6.5 s

    6.5 s

    Real visitors wait 6.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 3.2 s

    3.2 s

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

  • First Contentful Paint: 15.3 s

    15.3 s

    The first text or image appears after 15.3 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 38.2 s

    38.2 s

    Your largest element takes 38.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Tepeyac”.

  • Speed Index: 23.3 s

    23.3 s

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

  • Time to Interactive: 44.1 s

    44.1 s

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

  • Total Blocking Time: 1.9 s

    1.9 s

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

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

    +29%

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

3 checks passed
  • Real-user INP: 141 ms

    141 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0.002

    0.002

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

Images and page weight

3 to fix40
  • Page weight: 7.5 MB in 143 requests

    7.5 MB

    Your homepage downloads 7.5 MB in 143 requests on a phone: scripts 3.0 MB (61), stylesheets 1.8 MB (33) and images 1.5 MB (20). Under 2 MB keeps phones on slow connections fast.

  • 4 images far larger than shown

    1.1 MB

    4 images are downloaded at several times the size a phone draws them, for example 4-scaled.jpg at 2,560 px wide, shown at 340 px. Resized copies would save about 1.1 MB.

  • 5 images in older formats

    5 images (1.5 MB) 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 (195 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.12 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.12 g of CO₂e: 254.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

9 to fixGoogle 7686
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 18 text elements with low contrast

    18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 12 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h3 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 38 automated accessibility rules passed

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

SEO

2 to fixGoogle 9292
  • 4 H1 headlines

    There are 4 <h1> headlines (“+30,000”, “+1,800” and “+160”). One clear main headline is easier for people and search engines.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 133 internal links, 12 external

    The homepage links to 133 pages on ftepeyac.com.mx and 12 external pages.

6 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “Ofrecemos un gran catálogo de soluciones en agricultura, nos distinguimos por nuestra atención personalizada sin interm…”.

  • Title: 30 characters

    Your title is a healthy 30 characters: “Inicio - Fertilizantes Tepeyac”.

  • Canonical URL set

    The canonical URL is https://www.ftepeyac.com.mx/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage 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.ftepeyac.com.mx/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.ftepeyac.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.

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.

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://www.ftepeyac.com.mx/industria, https://www.ftepeyac.com.mx/industria-quimica, https://www.ftepeyac.com.mx/industria-maderera, https://www.ftepeyac.com.mx/nutricion-animal, https://www.ftepeyac.com.mx/nutricion-vegetal and https://www.ftepeyac.com.mx/fertilizantes-solidos and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://www.ftepeyac.com.mx/industria-quimica, https://www.ftepeyac.com.mx/industria-maderera, https://www.ftepeyac.com.mx/nutricion-animal, https://www.ftepeyac.com.mx/fertilizantes-solidos, https://www.ftepeyac.com.mx/mezclas-fisicas and https://www.ftepeyac.com.mx/fertilizantes-solubles and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 pages slow to respond

    https://www.ftepeyac.com.mx/industria, https://www.ftepeyac.com.mx/nutricion-vegetal, https://www.ftepeyac.com.mx/fertilizantes-solidos, https://www.ftepeyac.com.mx/fertilizantes-solubles, https://www.ftepeyac.com.mx/fertilizantes-liquidos and https://www.ftepeyac.com.mx/fertilizantes-organicos and 5 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 48 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 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9293
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Class extends value undefined is not a constructor or null”.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

    16 of 19 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 349 words of copy

    The homepage carries about 349 words of visible text.

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

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.

  • 14 cookies set on arrival

    14

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 ftepeyac.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

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics | Google Tag Manager
Hosting
Cable, S.A. de C.V.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on ftepeyac.com.mx, including 23 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

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