Website review, no card needed
tiendasmgi.es website review
Visit site (opens in a new tab)Reviewed 22 October 202645 issues · 91 checks
This review found 45 issues worth fixing on tiendasmgi.es, 20 of them high impact, across 91 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
65D- #114,805 of 123,879 reviewed websitesbeats 6%
- #67,211 of 69,698 online storesbeats 3%
- #144 of 176 PrestaShop storesbeats 15%
Closest competitors among PrestaShop stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.6 s |
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 146 ms |
| May 9, 2026 | 146 ms |
| May 16, 2026 | 146 ms |
| May 23, 2026 | 146 ms |
| May 30, 2026 | 148 ms |
| Jun 6, 2026 | 150 ms |
| Jun 13, 2026 | 152 ms |
| Jun 20, 2026 | 153 ms |
| Jun 27, 2026 | 153 ms |
| Jul 4, 2026 | 154 ms |
| Jul 11, 2026 | 154 ms |
| Jul 18, 2026 | 152 ms |
| Jul 25, 2026 | 152 ms |
| Aug 1, 2026 | 151 ms |
| Aug 8, 2026 | 150 ms |
| Aug 15, 2026 | 150 ms |
| Aug 22, 2026 | 150 ms |
| Aug 29, 2026 | 150 ms |
| Sep 5, 2026 | 151 ms |
| Sep 12, 2026 | 152 ms |
| Sep 19, 2026 | 152 ms |
| Sep 26, 2026 | 153 ms |
| Oct 3, 2026 | 153 ms |
| Oct 10, 2026 | 152 ms |
| Oct 17, 2026 | 152 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.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.5 s
4.1 s
4.7 s
Speed
Improve image delivery
12.2 s · 3.9 MB34 images could be 3.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 12.2 s faster on a phone.
Render-blocking requests
3.4 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.4 s.
Reduce unused CSS
1.6 s · 355 KiBAbout 355 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Mobile performance score: 17
17/100Your mobile performance score is 17 (desktop: 55). 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, Cookiebot and Facebook and others), adding 912 KiB and 1.2 s of main-thread time.
Use efficient cache lifetimes
650 ms · 390 KiB19 files are served with short cache lifetimes, so returning visitors download them again (390 KiB).
Google Tag Manager adds 485 ms
485 msGoogle Tag Manager costs a phone 485 ms of main-thread work and 519 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.
Reduce unused JavaScript
504 KiBAbout 504 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 3.3 s
A phone's processor spends 3.3 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Cookiebot adds 305 ms
305 msCookiebot costs a phone 305 ms of main-thread work and 41 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.
1,819 HTML elements
The page has 1,819 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 230 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).
Legacy JavaScript
20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 55 but mobile only 17. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify CSS
7 KiB7 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: 4 ms
4 msYour server sent the HTML in 4 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 CLS: 0.72
0.72For real visitors the layout shifts by 0.72 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 17.6 s
17.6 sYour largest element takes 17.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Vuela a la rutina”.
Time to Interactive: 29.5 s
29.5 sThe page becomes fully interactive after 29.5 s. Good is under 3.8 s.
Speed Index: 13.9 s
13.9 sVisually, the page fills in at 13.9 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.655
0.655The layout shifts by 0.655 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 4.2 s
4.2 sThe first text or image appears after 4.2 s on a phone. Good is under 1.8 s.
Total Blocking Time: 701 ms
701 msScripts block taps and scrolling for 701 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 146 ms to 152 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 161 ms
161 msReal visitors wait 161 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 567 ms
567 msReal visitors wait 567 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 7.3 MB in 113 requests
7.3 MBYour homepage downloads 7.3 MB in 113 requests on a phone: images 5.1 MB (57), scripts 1.5 MB (25) and stylesheets 339 KiB (3). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 2.1 MB together. On a phone connection a single image that size takes seconds.
8 images far larger than shown
2.4 MB8 images are downloaded at several times the size a phone draws them, for example b466de1559fde28f3d492b2c9485a604f565251b_juanita-banner.png at 1,900 px wide, shown at 390 px. Resized copies would save about 2.4 MB.
9 images in older formats
9 images (1.5 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
1920x30 - BARRA FIJA BLANCA.png 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).
About 2.1 g of CO₂ per visit
2.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.07 g of CO₂e: 248.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
4 links without text
4 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 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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.
7 links crawlers can't follow
7 links have no real href, so search engines can't follow them.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
242 internal links, 1 external
The homepage links to 242 pages on tiendasmgi.es and 1 external page.
5 checks passed
Meta description: 127 characters
Your meta description is 127 characters: “Descubre las ofertas de Tiendas MGI. Artículos a 10€, 15€ y 20€ y las mejores promociones en cientos de artículos ✅ ¡Ah…”.
Title: 40 characters
Your title is a healthy 40 characters: “Tiendas MGI - Artículos a 10€, 15€ y 20€”.
Structured data in place
Structured data found: Organization 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.tiendasmgi.es/1_index_sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.tiendasmgi.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.
Opted out of AI training for 1 crawler
robots.txt blocks ClaudeBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (900 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://www.tiendasmgi.es/content/5-pago-seguro and https://www.tiendasmgi.es/content/6-catalogo are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages share a title
/ and https://www.tiendasmgi.es/carrito all use the title “Tiendas MGI - Artículos a 10€, 15€ y 20€”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.tiendasmgi.es/content/6-catalogo and https://www.tiendasmgi.es/tiendas have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.tiendasmgi.es/contactenos and https://www.tiendasmgi.es/blog 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 121 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
9 small tap targets
9 of 32 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 “prestashop.on is not a function e.initEvent (https://www.tiendasmgi.es/modules/rcpgtagmanager/views/js/hook/trackingCli…”.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 369 words of copy
The homepage carries about 369 words of visible text.
3 checks passed
24 short forms
24 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 1 phone link 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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
11 cookies set on arrival
11Opening the homepage sets 11 cookies (measured from a US location before any click).
21 other companies contacted
Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 tiendasmgi.es, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on tiendasmgi.es, including 19 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.