Website review, no card needed

mercavalencia.es logo

mercavalencia.es website review

Visit site (opens in a new tab)Reviewed 3 November 202643 issues · 86 checks

This review found 43 issues worth fixing on mercavalencia.es, 15 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. 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
5.7 s2.8 sMay 16Oct 313.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20265.1 s
May 23, 20265.2 s
May 30, 20265.2 s
Jun 6, 20265.3 s
Jun 13, 20265.3 s
Jun 20, 20265.2 s
Jun 27, 20265.3 s
Jul 4, 20265.2 s
Jul 11, 20265.2 s
Jul 18, 20265.2 s
Jul 25, 20265.2 s
Aug 1, 20265.2 s
Aug 8, 20265.3 s
Aug 15, 20265.3 s
Aug 22, 20265.3 s
Aug 29, 20265.3 s
Sep 5, 20265.2 s
Sep 12, 20265.3 s
Sep 19, 20265.2 s
Sep 26, 20265.0 s
Oct 3, 20264.7 s
Oct 10, 20264.2 s
Oct 17, 20263.4 s
Oct 24, 20263.2 s
Oct 31, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
134 ms101 msMay 16Oct 31129 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026110 ms
May 23, 2026105 ms
May 30, 2026108 ms
Jun 6, 2026111 ms
Jun 13, 2026112 ms
Jun 20, 2026111 ms
Jun 27, 2026110 ms
Jul 4, 2026110 ms
Jul 11, 2026111 ms
Jul 18, 2026117 ms
Jul 25, 2026120 ms
Aug 1, 2026121 ms
Aug 8, 2026123 ms
Aug 15, 2026125 ms
Aug 22, 2026129 ms
Aug 29, 2026127 ms
Sep 5, 2026126 ms
Sep 12, 2026123 ms
Sep 19, 2026123 ms
Sep 26, 2026122 ms
Oct 3, 2026124 ms
Oct 10, 2026127 ms
Oct 17, 2026127 ms
Oct 24, 2026130 ms
Oct 31, 2026129 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 mercavalencia.es (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. mercavalencia.es at 1.4 s1.4 s
  2. mercavalencia.es at 2.7 s2.7 s
  3. mercavalencia.es at 4.1 s4.1 s
  4. mercavalencia.es at 5.4 s5.4 s
  5. mercavalencia.es at 6.8 s6.8 s
  6. mercavalencia.es at 8.2 s8.2 s
  7. mercavalencia.es at 9.5 s9.5 s
  8. mercavalencia.es at 10.9 s10.9 s

Speed

9 to fix56
  • Use efficient cache lifetimes

    5.7 s · 2.0 MB

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

  • Reduce unused JavaScript

    3.5 s · 815 KiB

    About 815 KiB 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.

  • Render-blocking requests

    2.8 s

    26 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.

  • Reduce unused CSS

    1.1 s · 249 KiB

    About 249 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Mobile performance score: 56

    56/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 1.5 MB and 816 ms of main-thread time.

  • YouTube adds 444 ms

    444 ms

    YouTube costs a phone 444 ms of main-thread work and 986 KiB 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.

  • Font display

    500 ms

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

  • Main-thread work: 3.8 s

    A phone's processor spends 3.8 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Improve image delivery

    177 KiB

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

  • Legacy JavaScript

    150 ms · 13 KiB

    Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 9 long tasks on the main thread

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

  • Minify JavaScript

    12 KiB

    12 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

9 to fix100
  • 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: 15.2 s

    15.2 s

    Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “HORARIS Mercat del Peix Dimarts a dissabte 3:45h. - 8:00h. …”. Most of its time is resource load delay (8.4 s).

  • Speed Index: 16.3 s

    16.3 s

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

  • Time to Interactive: 16.6 s

    16.6 s

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

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

    +20%

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Total Blocking Time: 230 ms

    230 ms

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

  • 5 images without width and height

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

3 checks passed
  • Real-user CLS: 0.08

    0.08

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

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

    -39%

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

  • Cumulative Layout Shift: 0.095

    0.095

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

Images and page weight

1 to fix85
  • Page weight: 3.4 MB in 107 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 107 requests on a phone: scripts 1.6 MB (31), images 1.1 MB (23) and fonts 331 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • About 1.0 g of CO₂ per visit

    0.97 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.97 g of CO₂e: 117.0 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

9 to fixGoogle 8390
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 18 text elements with low contrast

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

  • <html> element must have a valid value for the lang attribute (1 element)

    <html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.

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

  • 10 links without text

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

  • 1 form field without a label

    1 form field has 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 should not be empty (1 element)

    Headings should not be empty: 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.

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

  • 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

5 to fixGoogle 8580
  • Title is short (21 characters)

    Your title is only 21 characters: “Inici | MERCAVALÈNCIA”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No XML sitemap

    No XML sitemap at https://www.mercavalencia.es/wp-sitemap.xml, so Google discovers your pages only by following links.

  • 2 links crawlers can't follow

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

  • Invalid hreflang

    Your hreflang tags are invalid, so Google may show the wrong language version.

  • One H1 headline

    Your <h1> is empty.

  • Open Graph partly set

    Open Graph is missing og:description, so shared links fall back to guesses.

  • 100 internal links, 15 external

    The homepage links to 100 pages on mercavalencia.es and 15 external pages.

4 checks passed
  • Meta description: 114 characters

    Your meta description is 114 characters: “El mayor Centro Agroalimentario Comercial y Logístico de la Comunitat Valenciana de productos frescos y congelados”.

  • Canonical URL set

    The canonical URL is https://www.mercavalencia.es/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

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

AI search readiness

100
  • No llms.txt

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

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

Other pages

1 to fix75
  • 1 linked page is broken

    Your homepage links to https://www.mercavalencia.es/coneix-nos/som-mercavalencia, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 4 pages slow to respond

    https://www.mercavalencia.es/visites-guiades, https://www.mercavalencia.es/coneix-nos/historia-i-xifres, https://www.mercavalencia.es/info-practica/compra-en-mercavalencia and https://www.mercavalencia.es/info-practica/contractescomercials took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 7 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 7 pages that loaded have a <title>.

Best practices

4 to fixGoogle 6983
  • 7 small tap targets

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

  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 3 JavaScript errors while loading

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Only about 142 words

    The homepage has only about 142 words of visible text; thin pages give Google and first-time buyers little to go on.

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

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics, Meta Pixel and Matomo.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 cookies, 1 of them by other companies (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.

  • 16 other companies contacted

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

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

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Matomo

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on mercavalencia.es, including 18 speed issues, 5 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

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