Website review, no card needed
autoescuelagala.com website review
Visit site (opens in a new tab)Reviewed 22 October 202642 issues · 84 checks
This review found 42 issues worth fixing on autoescuelagala.com, 20 of them high impact, across 84 checks. The most urgent: avoid multiple page redirects. 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
59F- #123,613 of 126,458 reviewed websitesbeats 2%
- #69,973 of 70,479 online storesbeats 1%
- #2,930 of 2,972 WooCommerce storesbeats 1%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.0 s |
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 4.0 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.3 s |
| Aug 29, 2026 | 4.4 s |
| Sep 5, 2026 | 4.3 s |
| Sep 12, 2026 | 4.2 s |
| Sep 19, 2026 | 4.1 s |
| Sep 26, 2026 | 3.9 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 156 ms |
| May 9, 2026 | 156 ms |
| May 16, 2026 | 157 ms |
| May 23, 2026 | 157 ms |
| May 30, 2026 | 157 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 158 ms |
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 169 ms |
| Jul 11, 2026 | 174 ms |
| Jul 18, 2026 | 178 ms |
| Jul 25, 2026 | 179 ms |
| Aug 1, 2026 | 176 ms |
| Aug 8, 2026 | 178 ms |
| Aug 15, 2026 | 181 ms |
| Aug 22, 2026 | 180 ms |
| Aug 29, 2026 | 181 ms |
| Sep 5, 2026 | 175 ms |
| Sep 12, 2026 | 172 ms |
| Sep 19, 2026 | 168 ms |
| Sep 26, 2026 | 164 ms |
| Oct 3, 2026 | 161 ms |
| Oct 10, 2026 | 154 ms |
| Oct 17, 2026 | 151 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.3 s
2.5 s
3.8 s
5.1 s
6.3 s
7.6 s
8.9 s
10.2 s
Speed
Avoid multiple page redirects
37.4 sThe page goes through 1 redirect before it starts loading, costing about 37.4 s. Link and advertise the final URL directly.
Reduce unused JavaScript
18.9 s · 1.8 MBAbout 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 18.9 s faster on a phone.
Render-blocking requests
3.5 s40 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.
Mobile performance score: 14
14/100Your mobile performance score is 14 (desktop: 4). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.8 s
A phone's processor spends 8.8 s on main-thread work while loading, 4.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
150 ms · 747 KiB5 images could be 747 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
300 ms · 425 KiB10 files are served with short cache lifetimes, so returning visitors download them again (425 KiB).
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 264 ms. During a long task the page ignores taps.
Google Tag Manager adds 123 ms
123 msGoogle Tag Manager costs a phone 123 ms of main-thread work and 643 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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and salesmanago.pl and others), adding 962 KiB and 125 ms of main-thread time.
Minify CSS
150 ms · 9 KiB9 KiB could be saved by minifying CSS.
Minify JavaScript
150 ms · 7 KiB7 KiB could be saved by minifying JavaScript.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 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: 213 ms
213 msYour server sent the HTML in 213 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.60
0.60For real visitors the layout shifts by 0.60 (75th percentile). Good is under 0.1.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 8.9 s
8.9 sThe first text or image appears after 8.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 51.8 s
51.8 sYour largest element takes 51.8 s to render on a phone. Google's threshold for “good” is 2.5 s.
Speed Index: 19.7 s
19.7 sVisually, the page fills in at 19.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 53.4 s
53.4 sThe page becomes fully interactive after 53.4 s. Good is under 3.8 s.
Cumulative Layout Shift: 1
1The layout shifts by 1 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 670 ms
670 msScripts block taps and scrolling for 670 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 156 ms to 151 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user INP: 157 ms
157 msReal visitors wait 157 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 11.3 MB in 401 requests
11.3 MBYour homepage downloads 11.3 MB in 401 requests on a phone: images 5.3 MB (73), scripts 5.0 MB (176) and stylesheets 597 KiB (88). Under 2 MB keeps phones on slow connections fast.
About 3.2 g of CO₂ per visit
3.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.21 g of CO₂e: 385.7 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
Images must have alternative text (6 elements)
Images must have alternative text: 6 elements on the page fail this check, rated critical by axe-core.
Frames without titles
3 frames have no title, so screen-reader users cannot tell what they contain.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
36 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: 36 passed and 7 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Structured data has 1 problem
Structured data found (BreadcrumbList, ImageObject, Organization and WebPage) but with 1 problem, for example “Organization: url points at a different host (https://autoescuelagala1.c.wetopi.com/)”.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
48 internal links, 45 external
The homepage links to 48 pages on autoescuelagala.com and 45 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Sácate Cualquier Carnet de Conducir en Madrid”.
Title: 57 characters
Your title is a healthy 57 characters: “GALA Autoescuela | Todos los Carnet de conducir en Madrid”.
Canonical URL set
The canonical URL is https://autoescuelagala.com/.
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://autoescuelagala.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://autoescuelagala.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.
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,425 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://autoescuelagala.com/carrito is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://autoescuelagala.com/preguntas_teoricas and https://autoescuelagala.com/carrito have no meta description, so Google writes the search snippet from whatever text it finds.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://autoescuelagala.com/buscador-de-sedes-en-madrid, whose canonical is https://autoescuelagala.com/buscador-de-autoescuelas-en-madrid. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://autoescuelagala.com/preguntas_teoricas has no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://autoescuelagala.com/curso-de-sensibilizacion-y-reeducacion-vial and https://autoescuelagala.com/recupera-2-puntos-curso-de-conduccion-segura-y-eficiente took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 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.
Titles are unique
Every page we checked has its own title.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
5 small tap targets
5 of 19 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 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
Thin social proof
Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 385 words of copy
The homepage carries about 385 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
1 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Clarity and TikTok 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.
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.
26 other companies contacted
Loading the homepage contacts 26 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 autoescuelagala.com, 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 42 issues on autoescuelagala.com, including 21 speed issues, 3 SEO issues and 4 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.