Website review, no card needed

penguinlibros.com logo

penguinlibros.com website review

Visit site (opens in a new tab)Reviewed 1 November 202654 issues · 85 checks

This review found 54 issues worth fixing on penguinlibros.com, 26 of them high impact, across 85 checks. The most urgent: improve image delivery. 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
7.0 s5.9 sMay 9Oct 246.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20266.9 s
May 16, 20266.6 s
May 23, 20266.2 s
May 30, 20266.1 s
Jun 6, 20266.0 s
Jun 13, 20266.2 s
Jun 20, 20266.1 s
Jun 27, 20266.2 s
Jul 4, 20266.2 s
Jul 11, 20266.3 s
Jul 18, 20266.4 s
Jul 25, 20266.3 s
Aug 1, 20266.3 s
Aug 8, 20266.2 s
Aug 15, 20266.1 s
Aug 22, 20266.0 s
Aug 29, 20266.1 s
Sep 5, 20266.1 s
Sep 12, 20266.2 s
Sep 19, 20266.2 s
Sep 26, 20266.1 s
Oct 3, 20266.1 s
Oct 10, 20266.1 s
Oct 17, 20266.4 s
Oct 24, 20266.6 s
Real-visitor tap response (INP)75th percentile, phones
280 ms248 msMay 9Oct 24276 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026268 ms
May 16, 2026265 ms
May 23, 2026264 ms
May 30, 2026263 ms
Jun 6, 2026267 ms
Jun 13, 2026269 ms
Jun 20, 2026272 ms
Jun 27, 2026275 ms
Jul 4, 2026275 ms
Jul 11, 2026276 ms
Jul 18, 2026274 ms
Jul 25, 2026273 ms
Aug 1, 2026271 ms
Aug 8, 2026269 ms
Aug 15, 2026264 ms
Aug 22, 2026261 ms
Aug 29, 2026259 ms
Sep 5, 2026255 ms
Sep 12, 2026255 ms
Sep 19, 2026253 ms
Sep 26, 2026252 ms
Oct 3, 2026256 ms
Oct 10, 2026264 ms
Oct 17, 2026272 ms
Oct 24, 2026276 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 penguinlibros.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. penguinlibros.com at 1.9 s1.9 s
  2. penguinlibros.com at 3.8 s3.8 s
  3. penguinlibros.com at 5.7 s5.7 s
  4. penguinlibros.com at 7.6 s7.6 s
  5. penguinlibros.com at 9.5 s9.5 s
  6. penguinlibros.com at 11.4 s11.4 s
  7. penguinlibros.com at 13.3 s13.3 s
  8. penguinlibros.com at 15.3 s15.3 s

Speed

12 to fix21
  • Improve image delivery

    3.9 s · 2.4 MB

    34 images could be 2.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.9 s faster on a phone.

  • Use efficient cache lifetimes

    1.1 s · 1.1 MB

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

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 692 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: 21

    21/100

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

  • 8,110 HTML elements

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

  • Main-thread work: 6.6 s

    A phone's processor spends 6.6 s on main-thread work while loading, 3.0 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, TikTok and cookiebot.eu and others), adding 1.1 MB and 1.7 s of main-thread time.

  • Reduce unused JavaScript

    900 ms · 523 KiB

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

  • Reduce unused CSS

    750 ms · 98 KiB

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

  • Render-blocking requests

    650 ms

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

  • Font display

    500 ms

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

  • 17 long tasks on the main thread

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

  • Legacy JavaScript

    25 KiB

    Polyfills for old browsers add 25 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.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 211 ms

    211 ms

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

Core Web Vitals

13 to fix0
  • 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.3 s

    4.3 s

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

  • Real-user CLS: 0.51

    0.51

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

  • Real-user FCP: 3.3 s

    3.3 s

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

  • Real-user TTFB: 2.1 s

    2.1 s

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

  • Largest Contentful Paint: 16.6 s

    16.6 s

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

  • Time to Interactive: 20.0 s

    20.0 s

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

  • Total Blocking Time: 1.8 s

    1.8 s

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

  • Speed Index: 9.6 s

    9.6 s

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

  • Cumulative Layout Shift: 0.34

    0.34

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

  • Real-user INP: 265 ms

    265 ms

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

  • 32 images without width and height

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

  • Tap response (INP) held steady for real visitors

    +3%

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

  • Largest content (LCP) held steady for real visitors

    -3%

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

Images and page weight

4 to fix35
  • Page weight: 5.8 MB in 266 requests

    5.8 MB

    Your homepage downloads 5.8 MB in 266 requests on a phone: images 3.8 MB (176), scripts 1.4 MB (25) and fonts 276 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    799_mobile.jpg weighs 813 KiB. On a phone connection a single image that size takes seconds.

  • 10 images in older formats

    10 images (1.8 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 far larger than shown

    85 KiB

    1 image is downloaded at several times the size a phone draws it, for example Enigmasyactividades.jpg at 846 px wide, shown at 80 px. Resized copies would save about 85 KiB.

  • About 1.7 g of CO₂ per visit

    1.65 g

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

1 checks passed
  • Images load when needed

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

Accessibility

8 to fixGoogle 7989
  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • 2 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 12 images without alt text

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 71 form fields without a label

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

  • 8 links without text

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

  • ARIA role should be appropriate for the element (5 elements)

    ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

1 checks passed
  • 46 automated accessibility rules passed

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

SEO

5 to fixGoogle 7585
  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • 20 links crawlers can't follow

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

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No XML sitemap

    No XML sitemap at https://url.us.m.mimecastprotect.com/s/z-QrCrkY5gIr8v8wPUjt6Zh48d7W?domain=penguinlibros.com, so Google discovers your pages only by following links.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 831 internal links, 18 external

    The homepage links to 831 pages on penguinlibros.com and 18 external pages.

5 checks passed
  • Meta description: 118 characters

    Your meta description is 118 characters: “Empieza a leer los mejores libros, ebooks y audiolibros en Penguin Libros. Compra tus libros online ahora. ¡Visítanos!”.

  • One H1 headline

    Your main headline reads: “Compra tus libros online, ebooks y audiolibros en Penguinlibros”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Penguin Libros - Comprar libros online, ebook y audiolibros”.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

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

  • Text is in the HTML

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

Other pages

1 to fix0
  • 2 linked pages are broken

    Your homepage links to https://www.penguinlibros.com/es/content/1-entrega and https://www.penguinlibros.com/es/content/category/1-inicio, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 15 internal pages checked

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

Best practices

5 to fixGoogle 7362
  • 1 broken image

    1 image failed to load on a phone, for example https://www.penguinlibros.com/es/img/cms/ES_MARKETING/Banners/Banner%20LENGUA.png.

  • 41 small tap targets

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

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • A 8-field form

    Your longest form asks for 8 fields (6 required). Every extra field lowers completion.

  • 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 1,019 words of copy

    The homepage carries about 1,019 words of visible text.

1 checks passed
  • 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 Tag Manager and Outbrain (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 10 cookies set on arrival

    10

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

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

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) 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 penguinlibros.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
Tailwind CSS
Analytics
Google Tag Manager
Hosting
Imperva

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on penguinlibros.com, including 25 speed issues, 5 SEO issues and 5 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