Website review, no card needed
alqvimia.com website review
Visit site (opens in a new tab)Reviewed 19 October 202648 issues · 94 checks
This review found 48 issues worth fixing on alqvimia.com, 23 of them high impact, across 94 checks. The most urgent: render-blocking requests. 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
56F- #114,552 of 115,810 reviewed websitesbeats 1%
- #66,414 of 66,602 online storesbeats 0%
- #680 of 704 Magento storesbeats 2%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 6.1 s |
| May 9, 2026 | 6.5 s |
| May 16, 2026 | 6.5 s |
| May 23, 2026 | 6.4 s |
| May 30, 2026 | 5.8 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 4.6 s |
| Jun 20, 2026 | 4.5 s |
| Jun 27, 2026 | 4.1 s |
| Jul 4, 2026 | 4.0 s |
| Jul 11, 2026 | 4.3 s |
| Jul 18, 2026 | 4.4 s |
| Jul 25, 2026 | 4.3 s |
| Aug 1, 2026 | 4.1 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.3 s |
| Sep 12, 2026 | 4.3 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.1 s |
| Oct 3, 2026 | 3.9 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 225 ms |
| May 9, 2026 | 229 ms |
| May 16, 2026 | 220 ms |
| May 23, 2026 | 217 ms |
| May 30, 2026 | 226 ms |
| Jun 6, 2026 | 220 ms |
| Jun 13, 2026 | 220 ms |
| Jun 20, 2026 | 221 ms |
| Jun 27, 2026 | 211 ms |
| Jul 4, 2026 | 211 ms |
| Jul 11, 2026 | 216 ms |
| Jul 18, 2026 | 218 ms |
| Jul 25, 2026 | 216 ms |
| Aug 1, 2026 | 209 ms |
| Aug 8, 2026 | 210 ms |
| Aug 15, 2026 | 223 ms |
| Aug 22, 2026 | 232 ms |
| Aug 29, 2026 | 241 ms |
| Sep 5, 2026 | 242 ms |
| Sep 12, 2026 | 236 ms |
| Sep 19, 2026 | 231 ms |
| Sep 26, 2026 | 227 ms |
| Oct 3, 2026 | 221 ms |
| Oct 10, 2026 | 222 ms |
| Oct 17, 2026 | 229 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.6 s
3.1 s
4.7 s
6.3 s
7.9 s
9.4 s
11.0 s
12.6 s
Speed
Render-blocking requests
4.2 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.2 s.
Use efficient cache lifetimes
1.9 s · 584 KiB294 files are served with short cache lifetimes, so returning visitors download them again (584 KiB).
Reduce unused CSS
1.5 s · 367 KiBAbout 367 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 28
28/100Your mobile performance score is 28 (desktop: 66). 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 (b-cdn.net, Facebook and ZenDesk and others), adding 2.6 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
310 ms · 674 KiBAbout 674 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 310 ms faster on a phone.
b-cdn.net adds 788 ms
788 msb-cdn.net costs a phone 788 ms of main-thread work and 1.4 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.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
ZenDesk adds 263 ms
263 msZenDesk costs a phone 263 ms of main-thread work and 494 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.
Facebook adds 276 ms
276 msFacebook costs a phone 276 ms of main-thread work and 225 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.
2,080 HTML elements
The page has 2,080 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Tag Manager adds 162 ms
162 msGoogle Tag Manager costs a phone 162 ms of main-thread work and 321 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 182 ms. During a long task the page ignores taps.
Legacy JavaScript
50 ms · 17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Improve image delivery
23 KiB2 images could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Phones get a much slower page than desktops
Desktop scores 66 but mobile only 28. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 113 ms
113 msYour server sent the HTML in 113 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.
Real-user CLS: 0.71
0.71For real visitors the layout shifts by 0.71 (75th percentile). Good is under 0.1.
Real-user FCP: 3.1 s
3.1 sReal visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.5 s
2.5 sReal visitors wait 2.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 10.1 s
10.1 sYour largest element takes 10.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (4.5 s).
Speed Index: 11.6 s
11.6 sVisually, the page fills in at 11.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 17.1 s
17.1 sThe page becomes fully interactive after 17.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.746
0.746The layout shifts by 0.746 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 4.5 s
4.5 sThe first text or image appears after 4.5 s on a phone. Good is under 1.8 s.
Real-user INP: 202 ms
202 msReal visitors wait 202 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 271 ms
271 msScripts block taps and scrolling for 271 ms in total while the page loads. Good is under 200 ms.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 225 ms to 229 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Largest content (LCP) got 38% faster for real visitors
-38%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 6.1 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 2.7 MB in 356 requests
2.7 MBYour homepage downloads 2.7 MB in 356 requests on a phone: scripts 1.8 MB (267), stylesheets 337 KiB (5) and fonts 271 KiB (11). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.77 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 92.2 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
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.
Form elements must have labels (1 element)
Form elements must have labels: 1 element on the page fails this check, rated critical by axe-core.
Interactive controls must not be nested (3 elements)
Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
2 checks passed
Every image has alt text
All 36 images in the HTML carry an alt attribute.
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 6 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.
Title is long (72 characters)
Your title is 72 characters, so Google will cut it off around 60: “ALQVIMIA | ALQVIMIA | Cosmética Natural Holística y Aromaterapia de Lujo”.
Meta description is long (163 characters)
Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
205 internal links, 9 external
The homepage links to 205 pages on alqvimia.com and 9 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.alqvimia.com/es/.
Structured data in place
Structured data found: OnlineStore, SiteNavigationElement and WebSite.
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.alqvimia.com/media/sitemap/sitemap_es.xml.
AI search readiness
4 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, sameAs (social profiles) and contact details; logo and description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (917 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.alqvimia.com/llms.txt (7 KiB, 50 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.alqvimia.com/es/catalogsearch/advanced, which answers with an error. Visitors hit a dead end and search engines drop it.
6 pages slow to respond
https://www.alqvimia.com/es/tienda-online/cuidado-corporal/por-producto/aceites-corporales.html, https://www.alqvimia.com/es/tienda-online/cuidado-corporal/por-producto/elixires-emulsiones-corporales.html, https://www.alqvimia.com/es/tienda-online/cuidado-corporal/por-producto/tonicos.html, https://www.alqvimia.com/es/tienda-online/cuidado-corporal/por-producto/colonias-y-perfumes.html, https://www.alqvimia.com/es/tienda-online/cuidado-corporal/por-producto/nutricosmetica-natural.html and https://www.alqvimia.com/es/tienda-online/cuidado-corporal/por-producto/rituales-corporales.html took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 115 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 14 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 14 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://www.alqvimia.com/es/.
14 small tap targets
14 of 40 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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 378 words of copy
The homepage carries about 378 words of visible text.
3 checks passed
9 short forms
9 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 11 customer or partner logos and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
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.
6 other companies contacted
Loading the homepage contacts 6 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 alqvimia.com, 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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 48 issues on alqvimia.com, including 25 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.