Website review, no card needed
fantasiasmiguel.com website review
Visit site (opens in a new tab)Reviewed 29 October 202651 issues · 95 checks
This review found 51 issues worth fixing on fantasiasmiguel.com, 16 of them high impact, across 95 checks. The most urgent: improve image delivery. 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
70C- #103,224 of 123,940 reviewed websitesbeats 14%
- #62,610 of 69,726 online storesbeats 8%
- #57,915 of 63,424 Shopify storesbeats 7%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.9 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.9 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.1 s |
| Sep 26, 2026 | 3.2 s |
| Oct 3, 2026 | 3.2 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 3.2 s |
| Oct 24, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 257 ms |
| May 16, 2026 | 261 ms |
| May 23, 2026 | 267 ms |
| May 30, 2026 | 277 ms |
| Jun 6, 2026 | 289 ms |
| Jun 13, 2026 | 297 ms |
| Jun 20, 2026 | 306 ms |
| Jun 27, 2026 | 311 ms |
| Jul 4, 2026 | 313 ms |
| Jul 11, 2026 | 312 ms |
| Jul 18, 2026 | 310 ms |
| Jul 25, 2026 | 309 ms |
| Aug 1, 2026 | 309 ms |
| Aug 8, 2026 | 318 ms |
| Aug 15, 2026 | 328 ms |
| Aug 22, 2026 | 336 ms |
| Aug 29, 2026 | 342 ms |
| Sep 5, 2026 | 343 ms |
| Sep 12, 2026 | 343 ms |
| Sep 19, 2026 | 359 ms |
| Sep 26, 2026 | 380 ms |
| Oct 3, 2026 | 395 ms |
| Oct 10, 2026 | 390 ms |
| Oct 17, 2026 | 391 ms |
| Oct 24, 2026 | 407 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
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.3 s
2.7 s
3.1 s
Speed
Improve image delivery
1.6 s · 1.9 MB21 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
7,511 HTML elements
The page has 7,511 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 6.5 s
A phone's processor spends 6.5 s on main-thread work while loading, 3.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
750 ms · 954 KiBAbout 954 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (SearchSpring, Google Tag Manager and rebuyengine.com and others), adding 2.3 MB and 1.3 s of main-thread time.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
450 ms · 257 KiB26 files are served with short cache lifetimes, so returning visitors download them again (257 KiB).
Reduce unused CSS
300 ms · 189 KiBAbout 189 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
400 ms12 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
SearchSpring adds 382 ms
382 msSearchSpring costs a phone 382 ms of main-thread work and 159 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.
Google Tag Manager adds 312 ms
312 msGoogle Tag Manager costs a phone 312 ms of main-thread work and 699 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.
rebuyengine.com adds 141 ms
141 msrebuyengine.com costs a phone 141 ms of main-thread work and 648 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.
Klaviyo adds 104 ms
104 msKlaviyo costs a phone 104 ms of main-thread work and 325 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.
Shopify adds 103 ms
103 msShopify costs a phone 103 ms of main-thread work and 310 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 170 ms. During a long task the page ignores taps.
Legacy JavaScript
65 KiBPolyfills for old browsers add 65 KiB JavaScript that modern phones do not need.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 14 ms
14 msYour server sent the HTML in 14 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.
Largest Contentful Paint: 55.6 s
55.6 sYour largest element takes 55.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 57.2 s
57.2 sThe page becomes fully interactive after 57.2 s. Good is under 3.8 s.
Speed Index: 11.5 s
11.5 sVisually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 391 ms
391 msReal visitors wait 391 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 54% slower for real visitors
+54%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 257 ms to 407 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 357 ms
357 msScripts block taps and scrolling for 357 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 s on a phone. Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 628 ms
628 msReal visitors wait 628 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 16.8 MB in 507 requests
16.8 MBYour homepage downloads 16.8 MB in 507 requests on a phone: images 12.4 MB (179), scripts 2.6 MB (115) and other files 1.1 MB (175). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
banner_madera_pinturas.jpg weighs 580 KiB. On a phone connection a single image that size takes seconds.
3 images in older formats
3 images (1.3 MB) 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.
An image on the first screen is lazy-loaded
10728-28925_c7fda864-1d71-4b6b-b767-391acfaac95d.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
13 images far larger than shown
318 KiB13 images are downloaded at several times the size a phone draws them, for example bedazzled2.jpg at 1,000 px wide, shown at 310 px. Resized copies would save about 318 KiB.
2 images below the first screen load straight away
2 images further down the page (224 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.8 g of CO₂ per visit
4.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.76 g of CO₂e: 571.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 buttons without a name
3 buttons have no accessible name, so screen readers announce just “button”.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Summary elements must have discernible text (1 element)
Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (248 elements)
All page content should be contained by landmarks: 248 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.
Alternative text of images should not be repeated as text (74 elements)
Alternative text of images should not be repeated as text: 74 elements on the page fail this check, rated minor by axe-core.
14 links without text
14 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.
Headings skip levels
Headings skip levels (h1 → h4, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 H1 headlines
There are 4 <h1> headlines (“”, “¡Los más vendidos de la temporada!” and “¡Descubre lo que tenemos para ti!”). One clear main headline is easier for people and search engines.
1,306 internal links, 12 external
The homepage links to 1,306 pages on fantasiasmiguel.com and 12 external pages.
7 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Fantasias Miguel es la tienda de manualidades, bisutería, flores de seda, madera, artes manuales y goma eva más grande …”.
Title: 60 characters
Your title is a healthy 60 characters: “Fantasias Miguel ⎮ Tienda de Manualidades – Fantasías Miguel”.
Canonical URL set
The canonical URL is https://fantasiasmiguel.com/.
Structured data in place
Structured data found: Organization 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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://fantasiasmiguel.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 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 (4,132 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://fantasiasmiguel.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://fantasiasmiguel.com/collections/proyectos, https://fantasiasmiguel.com/pages/videos, https://fantasiasmiguel.com/apps/store-locator, https://fantasiasmiguel.com/collections/novedades and https://fantasiasmiguel.com/collections/promociones have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://fantasiasmiguel.com/collections/productos-para-manualidades/ARTICULOS-PARA-MESA, whose canonical is https://fantasiasmiguel.com/collections/productos-para-manualidades. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 pages without an H1
https://fantasiasmiguel.com/pages/servicio-express-y-pick-up, https://fantasiasmiguel.com/collections/productos-para-manualidades/ARTICULOS-PARA-MESA, https://fantasiasmiguel.com/collections/halloween-fm, https://fantasiasmiguel.com/collections/dia-de-los-muertos-fm, https://fantasiasmiguel.com/collections/navidad-fm and https://fantasiasmiguel.com/collections/proyectos and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 197 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
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
1 broken image
1 image failed to load on a phone, for example https://fantasiasmiguel.com/.
187 small tap targets
187 of 616 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.”).
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”.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 1,741 words of copy
The homepage carries about 1,741 words of visible text.
5 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 120 testimonial or review blocks and 2 trust badges.
Analytics in place
Analytics detected: Google Analytics, Microsoft Clarity, Hotjar and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 4 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.
28 cookies set on arrival
28Opening the homepage sets 28 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.
48 other companies contacted
Loading the homepage contacts 48 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 fantasiasmiguel.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
- Shopify
- Analytics
- Google Analytics | Hotjar | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on fantasiasmiguel.com, including 24 speed issues, 1 SEO issue 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.