Website review, no card needed

pandape.com logo

pandape.com website review

Visit site (opens in a new tab)Reviewed 18 November 202627 issues · 73 checks

This review found 27 issues worth fixing on pandape.com, 4 of them high impact, across 73 checks. The most urgent: fails Core Web Vitals for real visitors. 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
3.5 s2.4 sMay 30Nov 142.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20263.3 s
Jun 6, 20263.4 s
Jun 13, 20263.4 s
Jun 20, 20263.4 s
Jun 27, 20263.2 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s
Jul 25, 20263.2 s
Aug 1, 20263.2 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20262.8 s
Sep 12, 20262.7 s
Sep 19, 20262.8 s
Sep 26, 20263.0 s
Oct 3, 20263.1 s
Oct 10, 20263.1 s
Oct 17, 20263.1 s
Oct 24, 20263.0 s
Oct 31, 20262.8 s
Nov 7, 20262.6 s
Nov 14, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
236 ms171 msMay 30Nov 14225 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026178 ms
Jun 6, 2026180 ms
Jun 13, 2026180 ms
Jun 20, 2026182 ms
Jun 27, 2026182 ms
Jul 4, 2026182 ms
Jul 11, 2026182 ms
Jul 18, 2026180 ms
Jul 25, 2026182 ms
Aug 1, 2026184 ms
Aug 8, 2026188 ms
Aug 15, 2026193 ms
Aug 22, 2026196 ms
Aug 29, 2026198 ms
Sep 5, 2026200 ms
Sep 12, 2026202 ms
Sep 19, 2026204 ms
Sep 26, 2026207 ms
Oct 3, 2026216 ms
Oct 10, 2026220 ms
Oct 17, 2026223 ms
Oct 24, 2026228 ms
Oct 31, 2026226 ms
Nov 7, 2026228 ms
Nov 14, 2026225 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 pandape.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pandape.com at 0.4 s0.4 s
  2. pandape.com at 0.8 s0.8 s
  3. pandape.com at 1.1 s1.1 s
  4. pandape.com at 1.5 s1.5 s
  5. pandape.com at 1.9 s1.9 s
  6. pandape.com at 2.3 s2.3 s
  7. pandape.com at 2.6 s2.6 s
  8. pandape.com at 3.0 s3.0 s

Speed

5 to fix87
  • Mobile performance score: 87

    87/100

    Your mobile performance score is 87. Pages that score under 90 lose visitors before the first paint.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Wistia and Sentry), adding 4.3 MB and 392 ms of main-thread time.

  • Wistia adds 380 ms

    380 ms

    Wistia costs a phone 380 ms of main-thread work and 4.2 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.

  • Improve image delivery

    772 KiB

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

  • Reduce unused JavaScript

    460 ms · 109 KiB

    About 109 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.

  • 2 long tasks on the main thread

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

  • Reduce unused CSS

    21 KiB

    About 21 KiB of CSS is downloaded but never applied on this page.

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

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 641 ms of it running JavaScript. That is comfortably low.

  • Server response: 14 ms

    14 ms

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

Core Web Vitals

10 to fix33
  • 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: 241 ms

    241 ms

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

  • Real-user CLS: 0.19

    0.19

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

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

    +27%

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

  • Real-user TTFB: 982 ms

    982 ms

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

  • Speed Index: 5.6 s

    5.6 s

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

  • 45 images without width and height

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Largest Contentful Paint: 2.7 s

    2.7 s

    Your largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Pandapé ATS combina inteligencia artificial en todo tu proc…”. Most of its time is element render delay (2.3 s).

  • Time to Interactive: 4.1 s

    4.1 s

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

5 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Largest content (LCP) got 22% faster for real visitors

    -22%

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

  • Total Blocking Time: 98 ms

    98 ms

    Scripts block the page for only 98 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 8.3 MB in 75 requests

    8.3 MB

    Your homepage downloads 8.3 MB in 75 requests on a phone: media 5.4 MB (1), images 1.2 MB (48) and other files 983 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    230 KiB

    1 image is downloaded at several times the size a phone draws it, for example case_study_y_testimonial_logo_happyland.webp at 1,828 px wide, shown at 120 px. Resized copies would save about 230 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (264 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.4 g of CO₂ per visit

    2.36 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

5 to fixGoogle 8491
  • 7 text elements with low contrast

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

  • 50 images without alt text

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

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

    All page content should be contained by landmarks: 21 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.

  • 18 links without text

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

  • Headings skip levels

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

1 checks passed
  • 36 automated accessibility rules passed

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

SEO

1 to fixGoogle 9297
  • No social preview image

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

  • 110 internal links, 10 external

    The homepage links to 110 pages on pandape.com and 10 external pages.

7 checks passed
  • Meta description: 115 characters

    Your meta description is 115 characters: “Optimiza la atracción, la selección y la evaluación del talento con el software Pandapé, el ATS más usado en LATAM.”.

  • One H1 headline

    Your main headline reads: “Más alcance, más velocidad y más certeza al contratar”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Pandapé | Software de reclutamiento y selección | LATAM | ATS”.

  • Canonical URL set

    The canonical URL is https://www.pandape.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, ImageObject, Organization and WebPage.

  • 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.pandape.com/sitemap_index.xml.

AI search readiness

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

  • llms.txt published

    The site publishes https://www.pandape.com/llms.txt (5 KiB, 46 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 38 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 10087
  • 4 small tap targets

    4 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix80
  • Thin social proof

    Social proof on the homepage: 23 testimonial or review blocks. 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 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.

  • About 539 words of copy

    The homepage carries about 539 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Solicita una demo”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Solicita una demo” and “Solicitar demo”.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

Privacy and tracking

  • 2 cookies set on arrival

    2

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 pandape.com, 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
Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on pandape.com, including 15 speed issues, 1 SEO issue 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