Website review, no card needed
feriavalencia.com website review
Visit site (opens in a new tab)Reviewed 30 October 202644 issues · 82 checks
This review found 44 issues worth fixing on feriavalencia.com, 20 of them high impact, across 82 checks. The most urgent: font display. 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
61DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.5 s |
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.4 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.2 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 4.3 s |
| Sep 5, 2026 | 4.5 s |
| Sep 12, 2026 | 4.4 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 128 ms |
| May 16, 2026 | 127 ms |
| May 23, 2026 | 128 ms |
| May 30, 2026 | 124 ms |
| Jun 6, 2026 | 123 ms |
| Jun 13, 2026 | 124 ms |
| Jun 20, 2026 | 126 ms |
| Jun 27, 2026 | 134 ms |
| Jul 4, 2026 | 140 ms |
| Jul 11, 2026 | 139 ms |
| Jul 18, 2026 | 139 ms |
| Jul 25, 2026 | 139 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 142 ms |
| Aug 15, 2026 | 139 ms |
| Aug 22, 2026 | 139 ms |
| Aug 29, 2026 | 145 ms |
| Sep 5, 2026 | 150 ms |
| Sep 12, 2026 | 159 ms |
| Sep 19, 2026 | 156 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 148 ms |
| Oct 10, 2026 | 149 ms |
| Oct 17, 2026 | 148 ms |
| Oct 24, 2026 | 145 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.8 s
3.6 s
5.5 s
7.3 s
9.1 s
10.9 s
12.8 s
14.6 s
Speed
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Render-blocking requests
2.9 s44 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Reduce unused JavaScript
1.8 s · 390 KiBAbout 390 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.3 s
A phone's processor spends 7.3 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
700 ms · 3.4 MB25 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
Google CDN adds 452 ms
452 msGoogle CDN costs a phone 452 ms of main-thread work and 734 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 329 ms. During a long task the page ignores taps.
2,513 HTML elements
The page has 2,513 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
3 third-party services on the page
3 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts), adding 799 KiB and 490 ms of main-thread time.
Reduce unused CSS
33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page.
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: 231 ms
231 msYour server sent the HTML in 231 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.
Real-user LCP: 4.3 s
4.3 sReal visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest Contentful Paint: 9.3 s
9.3 sYour largest element takes 9.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Para ofrecer las mejores experiencias, utilizamos tecnologí…”. Most of its time is element render delay (4.3 s).
Time to Interactive: 22.4 s
22.4 sThe page becomes fully interactive after 22.4 s. Good is under 3.8 s.
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user CLS: 0.19
0.19For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Total Blocking Time: 472 ms
472 msScripts block taps and scrolling for 472 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.186
0.186The layout shifts by 0.186 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 128 ms to 145 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 3.5 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 178 ms
178 msReal visitors wait 178 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 593 ms
593 msReal visitors wait 593 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 11.3 MB in 167 requests
11.3 MBYour homepage downloads 11.3 MB in 167 requests on a phone: images 9.4 MB (52), scripts 903 KiB (41) and fonts 539 KiB (11). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (229 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.
2 images below the first screen load straight away
2 images further down the page (229 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.2 g of CO₂ per visit
3.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.21 g of CO₂e: 385.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
Elements must only use permitted ARIA attributes (20 elements)
Elements must only use permitted ARIA attributes: 20 elements on the page fail this check, rated serious by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (34 elements)
All page content should be contained by landmarks: 34 elements on the page fail this check, rated moderate by axe-core.
34 links without text
34 visible links have no text or label, so screen readers cannot say where they go.
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 (h4 → h6, h2 → h5 and h3 → h5), 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).
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 8 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.feriavalencia.com/sitemap_index.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
126 internal links, 19 external
The homepage links to 126 pages on feriavalencia.com and 19 external pages.
3 checks passed
Title: 38 characters
Your title is a healthy 38 characters: “Feria Valencia – tu espacio, tu evento”.
Canonical URL set
The canonical URL is https://www.feriavalencia.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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.feriavalencia.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 (3,226 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share 2 titles
https://www.feriavalencia.com/feria-valencia-2024/calendario-proximos-eventos and https://www.feriavalencia.com/calendario-proximos-eventos all use the title “Calendario eventos – Feria Valencia”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://www.feriavalencia.com/espacios, https://www.feriavalencia.com/organizar, https://www.feriavalencia.com/visitar, https://www.feriavalencia.com/contacto, https://www.feriavalencia.com/feria-valencia-2024/calendario-proximos-eventos and https://www.feriavalencia.com/en and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.feriavalencia.com/feria-valencia-2024/calendario-proximos-eventos, whose canonical is https://www.feriavalencia.com/calendario-proximos-eventos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://www.feriavalencia.com/espacios, https://www.feriavalencia.com/organizar, https://www.feriavalencia.com/visitar, https://www.feriavalencia.com/contacto, https://www.feriavalencia.com/feria-valencia-2024/calendario-proximos-eventos and https://www.feriavalencia.com/en and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages slow to respond
https://www.feriavalencia.com/feria-valencia-2024/calendario-proximos-eventos, https://www.feriavalencia.com/ca, https://www.feriavalencia.com/feria-valencia-2026/sostenibilidad, https://www.feriavalencia.com/feria-valencia-2026/transparencia, https://www.feriavalencia.com/feria-valencia-2024/quienes-somos and https://www.feriavalencia.com/exponer-en-feria-valencia and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 47 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 15 pages that loaded have a <title>.
Best practices
12 small tap targets
12 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.
Thin social proof
Social proof on the homepage: 154 testimonial or review blocks. 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 2,591 words of copy
The homepage carries about 2,591 words of visible text.
1 checks passed
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 cookies (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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 feriavalencia.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
- Uni2
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on feriavalencia.com, including 19 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.