Programmable

Website review, no card needed

frog.com.mx logo

frog.com.mx website review

Visit site (opens in a new tab)Reviewed 11 November 202633 issues · 80 checks

This review found 33 issues worth fixing on frog.com.mx, 16 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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

Site score

66D

Closest competitors among WooCommerce stores

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
3.5 s2.7 sMay 23Sep 123.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20262.8 s
Jun 20, 20262.8 s
Jun 27, 20262.8 s
Jul 4, 20262.9 s
Jul 11, 20263.0 s
Jul 18, 20263.2 s
Jul 25, 20263.4 s
Aug 1, 20263.0 s
Aug 8, 20262.9 s
Aug 15, 20262.8 s
Aug 22, 20262.8 s
Aug 29, 20263.4 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Real-visitor tap response (INP)75th percentile, phones
155 ms109 msMay 23Jun 13114 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026150 ms
May 30, 2026134 ms
Jun 6, 2026122 ms
Jun 13, 2026114 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

www.frog.com.mx (opens in a new tab)
Full-page screenshot of frog.com.mx (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. frog.com.mx at 1.5 s1.5 s
  2. frog.com.mx at 2.9 s2.9 s
  3. frog.com.mx at 4.4 s4.4 s
  4. frog.com.mx at 5.8 s5.8 s
  5. frog.com.mx at 7.3 s7.3 s
  6. frog.com.mx at 8.8 s8.8 s
  7. frog.com.mx at 10.2 s10.2 s
  8. frog.com.mx at 11.7 s11.7 s

Speed

10 to fix31

  • Reduce unused JavaScript

    6.5 s · 905 KiB

    About 905 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.5 s faster on a phone.

  • Use efficient cache lifetimes

    2.7 s · 669 KiB

    176 files are served with short cache lifetimes, so returning visitors download them again (669 KiB).

  • Render-blocking requests

    3.0 s

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

  • Mobile performance score: 31

    31/100

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

  • Main-thread work: 4.7 s

    A phone's processor spends 4.7 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.4 MB and 899 ms of main-thread time.

  • Reduce unused CSS

    640 ms · 115 KiB

    About 115 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 640 ms faster on a phone.

  • Google CDN adds 449 ms

    449 ms

    Google CDN costs a phone 449 ms of main-thread work and 743 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 Tag Manager adds 405 ms

    405 ms

    Google Tag Manager costs a phone 405 ms of main-thread work and 457 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,737 HTML elements

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

  • 16 long tasks on the main thread

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

  • Improve image delivery

    127 KiB

    6 images could be 127 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Legacy JavaScript

    100 ms · 26 KiB

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

  • Font display

    100 ms

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

  • Minify JavaScript

    10 KiB

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed

  • Server response: 188 ms

    188 ms

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

Core Web Vitals

7 to fix33

  • Largest Contentful Paint: 20.7 s

    20.7 s

    Your largest element takes 20.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 14.1 s

    14.1 s

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

  • Time to Interactive: 20.8 s

    20.8 s

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

  • First Contentful Paint: 3.2 s

    3.2 s

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

  • Total Blocking Time: 642 ms

    642 ms

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

  • Cumulative Layout Shift: 0.241

    0.241

    The layout shifts by 0.241 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 16 images without width and height

    16 images have no width and height attributes, so the layout jumps as each one loads.

  • Largest content (LCP) got 11% slower for real visitors

    +11%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed

  • Tap response (INP) got 17% faster for real visitors

    -17%

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

Images and page weight

1 to fix70

  • Page weight: 5.3 MB in 218 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 218 requests on a phone: images 2.0 MB (44), scripts 2.0 MB (86) and fonts 565 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • About 1.5 g of CO₂ per visit

    1.50 g

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

3 checks passed

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

6 to fixGoogle 9292

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 41 text elements with low contrast

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

  • 12 images without alt text

    12 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 2 elements on the page fail 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.

  • 7 form fields without a label

    7 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

1 checks passed

  • 50 automated accessibility rules passed

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

SEO

3 to fixGoogle 10085

  • Title is short (14 characters)

    Your title is only 14 characters: “Home - FrogADN”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (27 characters)

    Your meta description is only 27 characters: “Zippy - Multi-purpose Theme”. 70 to 160 characters is enough to sell the click.

  • No social preview image

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

  • 108 internal links, 12 external

    The homepage links to 108 pages on frog.com.mx and 12 external pages.

5 checks passed

  • One H1 headline

    Your main headline reads: “Insertar/Editar enlace”.

  • Canonical URL set

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

  • Structured data in place

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

AI search readiness

100

  • No llms.txt

    There is no https://www.frog.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 (1,225 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix98

  • 15 pages share a meta description

    https://www.frog.com.mx/ventas-y-distribucion, https://www.frog.com.mx/pilar-de-gestion-comercial, https://www.frog.com.mx/pilar-de-gestion-operativa, https://www.frog.com.mx/pilar-de-gestion-administrativa, https://www.frog.com.mx/froid-aplicacion-de-venta-en-ruta and https://www.frog.com.mx/frappy-e-commerce-web-y-aplicacion and 9 others use the same meta description. A description written for each page earns more clicks.

  • 6 pages slow to respond

    https://www.frog.com.mx/skywire-servidor-de-aplicaciones, https://www.frog.com.mx/soporte-a-usuarios, https://www.frog.com.mx/hospedaje, https://www.frog.com.mx/mantenimiento, https://www.frog.com.mx/implementacion and https://www.frog.com.mx/soportedocumentacionvideos took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 9687

  • 1 small tap target

    1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.frog.com.mx/wp-content/plugins/radiantthemes-core/assets/css/main.css?ver=7.1.…”.

1 checks passed

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix67

  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 813 words of copy

    The homepage carries about 813 words of visible text.

4 checks passed

  • 2 calls to action

    The homepage has 2 calls to action, for example “Register” and “Sign up”.

  • 3 short forms

    3 short forms (7 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 email links.

Privacy and tracking

1 to fix

  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 11 cookies set on arrival

    11

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

  • 9 other companies contacted

    Loading the homepage contacts 9 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 frog.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
A2 Hosting, Inc.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on frog.com.mx, including 17 speed issues, 3 SEO issues and 2 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