Website review, no card needed

padelnuestro.com logo

padelnuestro.com website review

Visit site (opens in a new tab)Reviewed 4 November 202640 issues · 83 checks

This review found 40 issues worth fixing on padelnuestro.com, 18 of them high impact, across 83 checks. The most urgent: google Tag Manager adds 2.1 s. 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.1 s2.8 sMay 16Oct 313.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20262.9 s
Jun 6, 20262.9 s
Jun 13, 20263.0 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20263.0 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 5, 20263.1 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20263.1 s
Oct 3, 20263.1 s
Oct 10, 20263.1 s
Oct 17, 20263.1 s
Oct 24, 20263.0 s
Oct 31, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
202 ms148 msMay 16Oct 31196 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026154 ms
May 23, 2026155 ms
May 30, 2026160 ms
Jun 6, 2026163 ms
Jun 13, 2026166 ms
Jun 20, 2026167 ms
Jun 27, 2026167 ms
Jul 4, 2026169 ms
Jul 11, 2026170 ms
Jul 18, 2026171 ms
Jul 25, 2026173 ms
Aug 1, 2026174 ms
Aug 8, 2026176 ms
Aug 15, 2026178 ms
Aug 22, 2026179 ms
Aug 29, 2026179 ms
Sep 5, 2026178 ms
Sep 12, 2026175 ms
Sep 19, 2026172 ms
Sep 26, 2026173 ms
Oct 3, 2026173 ms
Oct 10, 2026177 ms
Oct 17, 2026187 ms
Oct 24, 2026196 ms
Oct 31, 2026196 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 padelnuestro.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. padelnuestro.com at 0.9 s0.9 s
  2. padelnuestro.com at 1.7 s1.7 s
  3. padelnuestro.com at 2.6 s2.6 s
  4. padelnuestro.com at 3.4 s3.4 s
  5. padelnuestro.com at 4.3 s4.3 s
  6. padelnuestro.com at 5.1 s5.1 s
  7. padelnuestro.com at 6.0 s6.0 s
  8. padelnuestro.com at 6.8 s6.8 s

Speed

11 to fix15
  • Google Tag Manager adds 2.1 s

    2.1 s

    Google Tag Manager costs a phone 2.1 s of main-thread work and 2.3 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.

  • Mobile performance score: 15

    15/100

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

  • Main-thread work: 6.1 s

    A phone's processor spends 6.1 s on main-thread work while loading, 3.8 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, Didomi and Doofinder and others), adding 2.9 MB and 2.3 s of main-thread time.

  • Reduce unused JavaScript

    1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page.

  • Reduce unused CSS

    750 ms · 205 KiB

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

  • Minify JavaScript

    300 ms · 227 KiB

    227 KiB could be saved by minifying JavaScript.

  • Render-blocking requests

    450 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

  • 19 long tasks on the main thread

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

  • Improve image delivery

    300 ms · 32 KiB

    2 images could be 32 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • 2,547 HTML elements

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

  • Use efficient cache lifetimes

    150 ms · 140 KiB

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

  • Duplicated JavaScript

    150 ms · 8 KiB

    8 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

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

1 checks passed
  • Server response: 19 ms

    19 ms

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

Core Web Vitals

11 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: 4.2 s

    4.2 s

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

  • Real-user FCP: 3.8 s

    3.8 s

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

  • Real-user TTFB: 3.4 s

    3.4 s

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

  • Time to Interactive: 29.8 s

    29.8 s

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

  • Cumulative Layout Shift: 0.913

    0.913

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

  • Largest Contentful Paint: 7.3 s

    7.3 s

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

  • Speed Index: 10.9 s

    10.9 s

    Visually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 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 27% slower for real visitors

    +27%

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

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

3 checks passed
  • Real-user INP: 200 ms

    200 ms

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

  • Real-user CLS: 0.03

    0.03

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

  • First Contentful Paint: 1.6 s

    1.6 s

    The first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.

Images and page weight

1 to fix70
  • Page weight: 5.1 MB in 407 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 407 requests on a phone: scripts 3.8 MB (303), fonts 488 KiB (10) and images 428 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • About 1.4 g of CO₂ per visit

    1.44 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.44 g of CO₂e: 173.3 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 8693
  • Required ARIA attributes must be provided (1 element)

    Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 3 images without alt text

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

  • 16 links without text

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

  • 2 form fields without a label

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

1 checks passed
  • 55 automated accessibility rules passed

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

SEO

3 to fixGoogle 7793
  • No social preview image

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

  • 7 links crawlers can't follow

    7 links have no real href, so search engines can't follow them.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 619 internal links, 16 external

    The homepage links to 619 pages on padelnuestro.com and 16 external pages.

7 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Somos la Tienda de Pádel con la Mayor Selección de Palas de Pádel, Zapatillas, Paleteros y todo tipo de Equipación para…”.

  • One H1 headline

    Your main headline reads: “Tienda de Pádel Online, Líderes en Distribución de Pádel”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Tienda de Pádel Online | Líderes en Pádel | Pādel Nuestro”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: 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.padelnuestro.com/sitemapindex.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.padelnuestro.com/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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,091 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix73
  • 1 page points its canonical at the homepage

    https://www.padelnuestro.com/catalogsearch/advanced declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

  • 2 pages share a title

    / and https://www.padelnuestro.com/catalogsearch/advanced all use the title “Tienda de Pádel Online | Líderes en Pádel | Pādel Nuestro”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.padelnuestro.com/tiendas-padel-nuestro has no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://www.padelnuestro.com/catalogsearch/advanced, https://www.padelnuestro.com/stores/store/redirect/___store/fr/___from_store/es/uenc/aHR0cHM6Ly93d3cucGFkZWxudWVzdHJvLmNvbS9mci8%2C, https://www.padelnuestro.com/stores/store/redirect/___store/it/___from_store/es/uenc/aHR0cHM6Ly93d3cucGFkZWxudWVzdHJvLmNvbS9pdC8%2C, https://www.padelnuestro.com/stores/store/redirect/___store/de/___from_store/es/uenc/aHR0cHM6Ly93d3cucGFkZWxudWVzdHJvLmNvbS9kZS8%2C, https://www.padelnuestro.com/stores/store/redirect/___store/uk/___from_store/es/uenc/aHR0cHM6Ly93d3cucGFkZWxudWVzdHJvLmNvbS91ay8%2C and https://www.padelnuestro.com/stores/store/redirect/___store/int/___from_store/es/uenc/aHR0cHM6Ly93d3cucGFkZWxudWVzdHJvLmNvbS9pbnQv and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages slow to respond

    https://www.padelnuestro.com/stores/store/redirect/___store/fr/___from_store/es/uenc/aHR0cHM6Ly93d3cucGFkZWxudWVzdHJvLmNvbS9mci8%2C, https://www.padelnuestro.com/stores/store/redirect/___store/uk/___from_store/es/uenc/aHR0cHM6Ly93d3cucGFkZWxudWVzdHJvLmNvbS91ay8%2C, https://www.padelnuestro.com/stores/store/redirect/___store/pt/___from_store/es/uenc/aHR0cHM6Ly93d3cucGFkZWxudWVzdHJvLmNvbS9wdC8%2C and https://www.padelnuestro.com/outlet-padel took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 12 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 26 small tap targets

    26 of 69 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 “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix70
  • 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.

  • A 9-field form

    Your longest form asks for 9 fields (0 required). Every extra field lowers completion.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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 2,493 words of copy

    The homepage carries about 2,493 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: “Learn More →”.

  • Social proof on the page

    Social proof on the homepage: 17 customer or partner logos and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 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). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies (measured from a US location before any click).

  • 17 other companies contacted

    Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Didomi

    A consent management tool (Didomi) loads with the page.

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 padelnuestro.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Bootstrap
E-commerce
Magento
Analytics
Google Tag Manager
Hosting
Fastly

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on padelnuestro.com, including 22 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