Website review, no card needed
queralto.com website review
Visit site (opens in a new tab)Reviewed 24 October 202643 issues · 85 checks
This review found 43 issues worth fixing on queralto.com, 19 of them high impact, across 85 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
Site score
58FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.7 s |
| May 9, 2026 | 4.8 s |
| May 16, 2026 | 4.8 s |
| May 23, 2026 | 4.8 s |
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.8 s |
| Jun 13, 2026 | 4.8 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 5.1 s |
| Jul 4, 2026 | 5.3 s |
| Jul 11, 2026 | 5.6 s |
| Jul 18, 2026 | 5.9 s |
| Jul 25, 2026 | 5.8 s |
| Aug 1, 2026 | 5.5 s |
| Aug 8, 2026 | 4.9 s |
| Aug 15, 2026 | 4.4 s |
| Aug 22, 2026 | 4.4 s |
| Aug 29, 2026 | 4.4 s |
| Sep 5, 2026 | 4.4 s |
| Sep 12, 2026 | 4.5 s |
| Sep 19, 2026 | 4.5 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.6 s |
| Oct 10, 2026 | 4.6 s |
| Oct 17, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 354 ms |
| May 9, 2026 | 357 ms |
| May 16, 2026 | 348 ms |
| May 23, 2026 | 353 ms |
| May 30, 2026 | 353 ms |
| Jun 6, 2026 | 358 ms |
| Jun 13, 2026 | 361 ms |
| Jun 20, 2026 | 361 ms |
| Jun 27, 2026 | 362 ms |
| Jul 4, 2026 | 358 ms |
| Jul 11, 2026 | 363 ms |
| Jul 18, 2026 | 359 ms |
| Jul 25, 2026 | 357 ms |
| Aug 1, 2026 | 347 ms |
| Aug 8, 2026 | 343 ms |
| Aug 15, 2026 | 348 ms |
| Aug 22, 2026 | 356 ms |
| Aug 29, 2026 | 360 ms |
| Sep 5, 2026 | 368 ms |
| Sep 12, 2026 | 368 ms |
| Sep 19, 2026 | 369 ms |
| Sep 26, 2026 | 375 ms |
| Oct 3, 2026 | 373 ms |
| Oct 10, 2026 | 379 ms |
| Oct 17, 2026 | 391 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.2 s
2.5 s
3.7 s
5.0 s
6.2 s
7.5 s
8.7 s
9.9 s
Speed
Reduce unused JavaScript
3.0 s · 873 KiBAbout 873 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.0 s faster on a phone.
Use efficient cache lifetimes
2.1 s · 649 KiB63 files are served with short cache lifetimes, so returning visitors download them again (649 KiB).
Render-blocking requests
1.9 s32 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 32
32/100Your mobile performance score is 32 (desktop: 44). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 1.6 MB and 757 ms of main-thread time.
Reduce unused CSS
600 ms · 98 KiBAbout 98 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Google Tag Manager adds 290 ms
290 msGoogle Tag Manager costs a phone 290 ms of main-thread work and 694 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.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google CDN adds 95 ms
95 msGoogle CDN costs a phone 95 ms of main-thread work and 294 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.
Minify JavaScript
150 ms · 32 KiB32 KiB could be saved by minifying JavaScript.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 135 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Improve image delivery
20 KiB2 images could be 20 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need.
Minify CSS
6 KiB6 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.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 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.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.98
0.98For real visitors the layout shifts by 0.98 (75th percentile). Good is under 0.1.
Real-user TTFB: 2.1 s
2.1 sReal visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 2.758
2.758The layout shifts by 2.758 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 14.4 s
14.4 sYour largest element takes 14.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “girl with cookies”.
Time to Interactive: 20.0 s
20.0 sThe page becomes fully interactive after 20.0 s. Good is under 3.8 s.
Speed Index: 10.8 s
10.8 sVisually, the page fills in at 10.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user INP: 331 ms
331 msReal visitors wait 331 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
31 images without width and height
31 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 354 ms to 391 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-17, real Chrome visitors' largest content (lcp) went from 4.7 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Total Blocking Time: 195 ms
195 msScripts block the page for only 195 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.8 MB in 136 requests
2.8 MBYour homepage downloads 2.8 MB in 136 requests on a phone: scripts 2.2 MB (74), fonts 286 KiB (6) and images 142 KiB (20). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (40 KiB) is 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 0.8 g of CO₂ per visit
0.80 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.80 g of CO₂e: 95.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Images must have alternative text (7 elements)
Images must have alternative text: 7 elements on the page fail this check, rated critical by axe-core.
34 text elements with low contrast
34 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (26 elements)
All page content should be contained by landmarks: 26 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
37 links without text
37 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.
1 checks passed
39 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 4 failed. 2 mores 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.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “WebSite: missing name”.
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.queralto.com/sitemap.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.
269 internal links, 10 external
The homepage links to 269 pages on queralto.com and 10 external pages.
4 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Descubre el mayor catálogo de productos de ortopedia y material médico online en Queraltó. Compra segura con envíos gra…”.
Title: 45 characters
Your title is a healthy 45 characters: “Ortopedia Online y Material Médico - Queraltó”.
Canonical URL set
The canonical URL is https://www.queralto.com/.
robots.txt in place
robots.txt is in place.
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.queralto.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 (2,508 words), so crawlers that don't run JavaScript still read it.
Other pages
9 linked pages hidden from search
https://www.queralto.com/contactanos, https://www.queralto.com/content/248-novedades, https://www.queralto.com/11336-silla-de-ruedas-electrica-con-motor, https://www.queralto.com/11269-accesorios-y-repuestos, https://www.queralto.com/11530-andadores-sin-ruedas and https://www.queralto.com/11529-accesorios-para-andadores and 3 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages without a meta description
https://www.queralto.com/pedido-rapido and https://www.queralto.com/content/248-novedades have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.queralto.com/pedido-rapido and https://www.queralto.com/content/248-novedades have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages slow to respond
https://www.queralto.com/11336-silla-de-ruedas-electrica-con-motor, https://www.queralto.com/11269-accesorios-y-repuestos, https://www.queralto.com/11530-andadores-sin-ruedas, https://www.queralto.com/11529-accesorios-para-andadores, https://www.queralto.com/11853-andadores-con-2-ruedas and https://www.queralto.com/11855-andadores-con-3-ruedas 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 181 found) and read each the way a search engine does.
4 checks passed
Linked pages load
10 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 a title
All 10 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17132943&tm=gtm002&Ver=2&mid=8ca34b8b-7145-45e2-89e1-a1eef42721fb&bo=1&sid=0f88c050cfb411f1a611adb7f80c5b82&vid=0f88c910cfb411f190e9c1113a92fa2f&vids=1&msclkid=N&pi=91.
36 small tap targets
36 of 52 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
5 low-resolution images
5 images are served at too low a resolution for sharp phone screens.
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.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
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 537 words of copy
The homepage carries about 537 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, Microsoft Clarity and Hotjar.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 2 mores (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
34 other companies contacted
Loading the homepage contacts 34 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 queralto.com, 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 © 2016.
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager | Hotjar | Microsoft Clarity
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 queralto.com, including 21 speed issues, 4 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.