Website review, no card needed
calidadpascual.com website review
Visit site (opens in a new tab)Reviewed 4 November 202645 issues · 89 checks
This review found 45 issues worth fixing on calidadpascual.com, 18 of them high impact, across 89 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.3 s |
| May 23, 2026 | 4.2 s |
| May 30, 2026 | 4.2 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 4.2 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.0 s |
| Aug 22, 2026 | 4.2 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.3 s |
| Sep 12, 2026 | 4.4 s |
| Sep 19, 2026 | 4.4 s |
| Sep 26, 2026 | 4.3 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.9 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 136 ms |
| May 23, 2026 | 133 ms |
| May 30, 2026 | 132 ms |
| Jun 6, 2026 | 129 ms |
| Jun 13, 2026 | 127 ms |
| Jun 20, 2026 | 132 ms |
| Jun 27, 2026 | 134 ms |
| Jul 4, 2026 | 134 ms |
| Jul 11, 2026 | 135 ms |
| Jul 18, 2026 | 135 ms |
| Jul 25, 2026 | 134 ms |
| Aug 1, 2026 | 134 ms |
| Aug 8, 2026 | 134 ms |
| Aug 15, 2026 | 132 ms |
| Aug 22, 2026 | 134 ms |
| Aug 29, 2026 | 136 ms |
| Sep 5, 2026 | 137 ms |
| Sep 12, 2026 | 143 ms |
| Sep 19, 2026 | 145 ms |
| Sep 26, 2026 | 140 ms |
| Oct 3, 2026 | 139 ms |
| Oct 10, 2026 | 135 ms |
| Oct 17, 2026 | 131 ms |
| Oct 24, 2026 | 128 ms |
| Oct 31, 2026 | 123 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
How it loaded on a phone
0.7 s
1.4 s
2.1 s
2.8 s
3.5 s
4.2 s
5.0 s
5.7 s
Speed
Improve image delivery
9.1 s · 6.8 MB10 images could be 6.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.1 s faster on a phone.
Render-blocking requests
6.7 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.7 s.
Reduce unused CSS
3.9 s · 816 KiBAbout 816 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.9 s faster on a phone.
Reduce unused JavaScript
3.5 s · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Main-thread work: 4.9 s
A phone's processor spends 4.9 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
6 third-party services on the page
6 third-party services load with your homepage (Optanon, Google Maps and Google Tag Manager and others), adding 602 KiB and 659 ms of main-thread time.
Font display
650 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).
Legacy JavaScript
400 ms · 162 KiBPolyfills for old browsers add 162 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
1,789 HTML elements
The page has 1,789 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify JavaScript
150 ms · 45 KiB45 KiB could be saved by minifying JavaScript.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 160 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
147 KiB7 files are served with short cache lifetimes, so returning visitors download them again (147 KiB).
Document request latency
126 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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: 157 ms
157 msYour server sent the HTML in 157 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 26.1 s
26.1 sYour largest element takes 26.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “4 DE NOVIEMBRE DE 2026 • GENERAL• INNOVACIÓN El café en cáp…”.
Time to Interactive: 56.1 s
56.1 sThe page becomes fully interactive after 56.1 s. Good is under 3.8 s.
First Contentful Paint: 6.9 s
6.9 sThe first text or image appears after 6.9 s on a phone. Good is under 1.8 s.
Speed Index: 11.1 s
11.1 sVisually, the page fills in at 11.1 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Total Blocking Time: 288 ms
288 msScripts block taps and scrolling for 288 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 136 ms to 123 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 139 ms
139 msReal visitors wait 139 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 527 ms
527 msReal visitors wait 527 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 56% faster for real visitors
-56%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.3 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
Images and page weight
Page weight: 15.3 MB in 135 requests
15.3 MBYour homepage downloads 15.3 MB in 135 requests on a phone: images 11.2 MB (38), scripts 2.2 MB (48) and stylesheets 878 KiB (21). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
37 KiB1 image is downloaded at several times the size a phone draws it, for example sin-titulo-q.png at 600 px wide, shown at 150 px. Resized copies would save about 37 KiB.
3 images in older formats
3 images (162 KiB) 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.
About 4.3 g of CO₂ per visit
4.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.34 g of CO₂e: 520.9 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
18 tap targets too small
18 tap targets are too small or too close together to hit reliably with a finger.
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
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 (17 elements)
All page content should be contained by landmarks: 17 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.
4 links without text
4 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.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (22 characters)
Your title is only 22 characters: “Pascual - Dar lo mejor”. Between 30 and 65 characters leaves room to say what you do and for whom.
Structured data has 1 problem
Structured data found (BreadcrumbList, ImageObject, WebPage and WebSite) but with 1 problem, for example “BreadcrumbList: itemListElement is an empty list”.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
46 internal links, 8 external
The homepage links to 46 pages on calidadpascual.com and 8 external pages.
6 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Pascual engloba un amplio portafolio de marcas de alimentación y bebidas, innovadoras y líderes en el mercado, bajo un …”.
One H1 headline
Your main headline reads: “Si necesitas contactar con nosotros, puedes llamarnos al teléfono de Atención al Consumidor 900 509 650. Atenderemos tu…”.
Canonical URL set
The canonical URL is https://www.calidadpascual.com/.
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.
XML sitemap found
Your XML sitemap is reachable at http://www.calidadpascual.com/sitemap_index.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.calidadpascual.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 (832 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages are broken
Your homepage links to https://www.calidadpascual.com/category/innovacion and https://www.calidadpascual.com/2026/11/04/el-cafe-en-capsulas-busca-ganar-peso-en-oficinas-y-restauracion-con-el-nuevo-modelo-de-coffee-horeca, which answer with an error. Visitors hit a dead end and search engines drop them.
4 pages share a title
/, https://www.calidadpascual.com/en, https://www.calidadpascual.com/fr and https://www.calidadpascual.com/pt all use the title “Pascual - Dar lo mejor”. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages without a meta description
https://www.calidadpascual.com/quienes-somos, https://www.calidadpascual.com/nuestras-marcas, https://www.calidadpascual.com/bienestar, https://www.calidadpascual.com/desarrollo, https://www.calidadpascual.com/medioambiente and https://www.calidadpascual.com/internacional and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://www.calidadpascual.com/en, https://www.calidadpascual.com/fr and https://www.calidadpascual.com/pt use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.calidadpascual.com/nuestras-marcas, whose canonical is https://www.calidadpascual.com/nuestras-marcas/leche-pascual. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://www.calidadpascual.com/nuestras-marcas, https://www.calidadpascual.com/en, https://www.calidadpascual.com/fr and https://www.calidadpascual.com/pt have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://www.calidadpascual.com/nuestras-marcas and https://www.calidadpascual.com/desarrollo have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
3 pages slow to respond
https://www.calidadpascual.com/en, https://www.calidadpascual.com/fr and https://www.calidadpascual.com/pt took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
2 checks passed
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
34 small tap targets
34 of 60 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 TypeError: Cannot read properties of undefined (reading 'Domain')”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 11 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
A 21-field form
Your longest form asks for 21 fields (11 required). Every extra field lowers completion.
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 846 words of copy
The homepage carries about 846 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 calidadpascual.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 Analytics
- Hosting
- AWS
Company
- Founded
- 1969
- Headquarters
- Aranda de Duero
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 calidadpascual.com, including 18 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.