Website review, no card needed
pastasgallo.es website review
Visit site (opens in a new tab)Reviewed 3 November 202638 issues · 82 checks
This review found 38 issues worth fixing on pastasgallo.es, 18 of them high impact, across 82 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 97 ms |
| May 23, 2026 | 97 ms |
| May 30, 2026 | 97 ms |
| Jun 6, 2026 | 95 ms |
| Jun 13, 2026 | 96 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 97 ms |
| Jul 11, 2026 | 95 ms |
| Jul 18, 2026 | 95 ms |
| Jul 25, 2026 | 90 ms |
| Aug 1, 2026 | 88 ms |
| Aug 8, 2026 | 87 ms |
| Aug 15, 2026 | 84 ms |
| Aug 22, 2026 | 85 ms |
| Aug 29, 2026 | 85 ms |
| Sep 5, 2026 | 84 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 87 ms |
| Sep 26, 2026 | 87 ms |
| Oct 3, 2026 | 86 ms |
| Oct 10, 2026 | 86 ms |
| Oct 17, 2026 | 86 ms |
| Oct 24, 2026 | 88 ms |
| Oct 31, 2026 | 92 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
1.4 s
2.9 s
4.3 s
5.8 s
7.2 s
8.7 s
10.1 s
11.6 s
Speed
Improve image delivery
3.0 s · 3.2 MB83 images could be 3.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Reduce unused JavaScript
3.6 s · 682 KiBAbout 682 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
Render-blocking requests
4.3 s18 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.3 s.
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Unpkg and Cookiebot and others), adding 1.3 MB and 922 ms of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 647 ms
647 msGoogle Tag Manager costs a phone 647 ms of main-thread work and 1.1 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.
Reduce unused CSS
450 ms · 99 KiBAbout 99 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 2.9 s
A phone's processor spends 2.9 s on main-thread work while loading, 1.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
250 ms · 50 KiB5 files are served with short cache lifetimes, so returning visitors download them again (50 KiB).
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 128 ms. During a long task the page ignores taps.
Minify CSS
23 KiB23 KiB could be saved by minifying CSS.
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: 44 ms
44 msYour server sent the HTML in 44 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: 33.7 s
33.7 sYour largest element takes 33.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “2 / 5”.
Time to Interactive: 34.2 s
34.2 sThe page becomes fully interactive after 34.2 s. Good is under 3.8 s.
Speed Index: 10.4 s
10.4 sVisually, the page fills in at 10.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Real-user TTFB: 947 ms
947 msReal visitors wait 947 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 286 ms
286 msScripts block taps and scrolling for 286 ms in total while the page loads. Good is under 200 ms.
7 images without width and height
7 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 97 ms to 92 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
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.
Real-user INP: 107 ms
107 msReal visitors wait 107 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.005
0.005The layout barely moves while loading (CLS 0.005, good is under 0.1).
Images and page weight
Page weight: 11.9 MB in 186 requests
11.9 MBYour homepage downloads 11.9 MB in 186 requests on a phone: images 9.9 MB (117), scripts 1.5 MB (38) and fonts 323 KiB (5). Under 2 MB keeps phones on slow connections fast.
27 images far larger than shown
1.1 MB27 images are downloaded at several times the size a phone draws them, for example Pollo-relleno-al-horno.webp at 1,600 px wide, shown at 370 px. Resized copies would save about 1.1 MB.
27 images in older formats
27 images (2.9 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.
13 images below the first screen load straight away
13 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.4 g of CO₂ per visit
3.37 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.37 g of CO₂e: 405.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
39 tap targets too small
39 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
35 links without text
35 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (7 elements)
Headings should not be empty: 7 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 115 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (66 characters)
Your title is 66 characters, so Google will cut it off around 60: “Pastas Gallo - Sitio Oficial - Alimentación Natural : Pastas Gallo”.
5 H1 headlines
There are 5 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
138 internal links, 5 external
The homepage links to 138 pages on pastasgallo.es and 5 external pages.
5 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Alimentación natural con Pastas Gallo. Web oficial de Pastas Gallo, el nombre de la pasta en España. Pastas de diferent…”.
Canonical URL set
The canonical URL is https://www.pastasgallo.es/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person 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.pastasgallo.es/sitemap_index.xml.
AI search readiness
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 contact details; sameAs (social profiles) and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (564 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.pastasgallo.es/productos has no meta description, so Google writes the search snippet from whatever text it finds.
6 pages slow to respond
https://www.pastasgallo.es/categorias-productos/pasta-seca, https://www.pastasgallo.es/categorias-productos/proteina, https://www.pastasgallo.es/categorias-productos/pasta-infantil, https://www.pastasgallo.es/categorias-productos/integral, https://www.pastasgallo.es/categorias-productos/100-legumbre and https://www.pastasgallo.es/categorias-productos/multi-ingrediente took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 78 found) and read each the way a search engine does.
6 checks passed
Linked pages load
12 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 12 pages that loaded have a <title>.
Best practices
37 small tap targets
37 of 64 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
60 distorted images
60 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 JavaScript error while loading
1 error was 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
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.
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 552 words of copy
The homepage carries about 552 words of visible text.
3 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
3 trackers load before any consent
3Before 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 (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
6 cookies set on arrival
6Opening the homepage sets 6 cookies (measured from a US location before any click).
10 other companies contacted
Loading the homepage contacts 10 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 pastasgallo.es, 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 | Google Tag Manager
- Hosting
- OXIGEN Data Center S.L.
Company
- Founded
- 1946
- Headquarters
- El Carpio
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on pastasgallo.es, including 17 speed issues, 3 SEO issues and 3 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.