Website review, no card needed
123waldo.es website review
Visit site (opens in a new tab)Reviewed 10 November 202646 issues · 87 checks
This review found 46 issues worth fixing on 123waldo.es, 13 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
One score from every part of this review. How it works
Speed
Reduce unused JavaScript
1.0 s · 631 KiBAbout 631 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.0 s faster on a phone.
Render-blocking requests
1.1 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 64
64/100Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
755 KiB9 images could be 755 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
550 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 550 ms).
Reduce unused CSS
450 ms · 97 KiBAbout 97 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.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, JSDelivr CDN and morrowtheory.com and others), adding 1.3 MB and 164 ms of main-thread time.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,660 HTML elements
The page has 1,660 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google CDN adds 75 ms
75 msGoogle CDN costs a phone 75 ms of main-thread work and 352 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.
123waldo.nl adds 0 ms
0 ms123waldo.nl costs a phone 0 ms of main-thread work and 708 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.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 114 ms. During a long task the page ignores taps.
Minify JavaScript
75 KiB75 KiB could be saved by minifying JavaScript.
Use efficient cache lifetimes
44 KiB3 files are served with short cache lifetimes, so returning visitors download them again (44 KiB).
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.1 s
9.1 sYour largest element takes 9.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 17.7 s
17.7 sThe page becomes fully interactive after 17.7 s. Good is under 3.8 s.
Speed Index: 10.6 s
10.6 sVisually, the page fills in at 10.6 s (Speed Index). Good is under 3.4 s.
27 images without width and height
27 images have no width and height attributes, so the layout jumps as each one loads.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 81 ms
81 msScripts block the page for only 81 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.3 MB in 258 requests
3.3 MBYour homepage downloads 3.3 MB in 258 requests on a phone: images 1.6 MB (48), scripts 1.5 MB (176) and stylesheets 111 KiB (4). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (691 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 far larger than shown
316 KiB2 images are downloaded at several times the size a phone draws them, for example es_3_.png at 1,875 px wide, shown at 360 px. Resized copies would save about 316 KiB.
7 images below the first screen load straight away
7 images further down the page (473 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.94 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.94 g of CO₂e: 112.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Required ARIA attributes must be provided (1 element)
Required ARIA attributes must be provided: 1 element on the page fails this check, rated critical by axe-core.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (79 elements)
All page content should be contained by landmarks: 79 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
12 links without text
12 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.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (97 characters)
Your title is 97 characters, so Google will cut it off around 60: “123waldo.es la web de todos tus adaptadores, baterías e inversores. | 123Waldo.nl In for …”.
Meta description is long (277 characters)
Your meta description is 277 characters; Google truncates after about 160, so the end of your pitch is cut.
17 links crawlers can't follow
17 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
181 internal links, 23 external
The homepage links to 181 pages on 123waldo.es and 23 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://123waldo.es/.
Structured data in place
Structured data found: BreadcrumbList, ElectronicsStore, WebPage and WebSite.
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.
XML sitemap found
Your XML sitemap is reachable at https://123waldo.es/sitemap.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://123waldo.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.
Text is in the HTML
Your server sends the page's text in the HTML (887 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://123waldo.es/catalogsearch/advanced is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
14 pages share a meta description
https://123waldo.es/catalogsearch/advanced, https://123waldo.es/baterias.html, https://123waldo.es/baterias/baterias-para-portatiles.html, https://123waldo.es/baterias/baterias-de-la-camara.html, https://123waldo.es/baterias/baterias-de-herramientas.html and https://123waldo.es/baterias/baterias-de-aspiradora.html and 8 others use the same meta description. A description written for each page earns more clicks.
9 pages without an H1
https://123waldo.es/baterias.html, https://123waldo.es/baterias/baterias-para-portatiles.html, https://123waldo.es/baterias/baterias-de-la-camara.html, https://123waldo.es/baterias/baterias-de-herramientas.html, https://123waldo.es/baterias/baterias-de-telefono.html and https://123waldo.es/baterias/baterias-de-altavoces-inalambricos.html and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
13 pages slow to respond
https://123waldo.es/baterias.html, https://123waldo.es/baterias/baterias-para-portatiles.html, https://123waldo.es/baterias/baterias-de-la-camara.html, https://123waldo.es/baterias/baterias-de-herramientas.html, https://123waldo.es/baterias/baterias-de-aspiradora.html and https://123waldo.es/baterias/baterias-de-telefono.html and 7 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 142 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://d1yf6t30d8nxpr.cloudfront.net/wysiwyg/ups_optimized.jpg.
19 small tap targets
19 of 88 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
17 distorted images
17 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 575 words of copy
The homepage carries about 575 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
18 short forms
18 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
16 cookies set on arrival
16Opening the homepage sets 16 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.
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.
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 123waldo.es, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Magento
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on 123waldo.es, including 16 speed issues, 4 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.