Website review, no card needed
surtidor.com website review
Visit site (opens in a new tab)Reviewed 26 October 202645 issues · 84 checks
This review found 45 issues worth fixing on surtidor.com, 21 of them high impact, across 84 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- #100,425 of 120,386 reviewed websitesbeats 14%
- #61,239 of 68,150 online storesbeats 8%
- #109 of 171 PrestaShop storesbeats 34%
Closest competitors among PrestaShop stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.3 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 170 ms |
| May 16, 2026 | 172 ms |
| May 23, 2026 | 174 ms |
| May 30, 2026 | 173 ms |
| Jun 6, 2026 | 173 ms |
| Jun 13, 2026 | 173 ms |
| Jun 20, 2026 | 174 ms |
| Jun 27, 2026 | 177 ms |
| Jul 4, 2026 | 179 ms |
| Jul 11, 2026 | 181 ms |
| Jul 18, 2026 | 179 ms |
| Jul 25, 2026 | 178 ms |
| Aug 1, 2026 | 180 ms |
| Aug 8, 2026 | 185 ms |
| Aug 15, 2026 | 194 ms |
| Aug 22, 2026 | 201 ms |
| Aug 29, 2026 | 203 ms |
| Sep 5, 2026 | 203 ms |
| Sep 12, 2026 | 201 ms |
| Sep 19, 2026 | 201 ms |
| Sep 26, 2026 | 203 ms |
| Oct 3, 2026 | 206 ms |
| Oct 10, 2026 | 213 ms |
| Oct 17, 2026 | 215 ms |
| Oct 24, 2026 | 206 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.1 s
2.3 s
3.4 s
4.6 s
5.7 s
6.8 s
8.0 s
9.1 s
Speed
Improve image delivery
9.4 s · 5.0 MB32 images could be 5.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 9.4 s faster on a phone.
Use efficient cache lifetimes
2.5 s · 1.1 MB114 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).
Render-blocking requests
3.5 s2 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.
Reduce unused JavaScript
2.3 s · 827 KiBAbout 827 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.
Google Tag Manager adds 1.1 s
1.1 sGoogle Tag Manager costs a phone 1.1 s of main-thread work and 591 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 29
29/100Your mobile performance score is 29 (desktop: 67). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.7 s
A phone's processor spends 7.7 s on main-thread work while loading, 4.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,393 HTML elements
The page has 3,393 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, ZenDesk and Facebook and others), adding 1.5 MB and 2.7 s of main-thread time.
Reduce unused CSS
900 ms · 184 KiBAbout 184 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
ZenDesk adds 697 ms
697 msZenDesk costs a phone 697 ms of main-thread work and 474 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 696 ms. During a long task the page ignores taps.
Facebook adds 429 ms
429 msFacebook costs a phone 429 ms of main-thread work and 279 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.
Legacy JavaScript
150 ms · 12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Phones get a much slower page than desktops
Desktop scores 67 but mobile only 29. 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.
1 checks passed
Server response: 15 ms
15 msYour server sent the HTML in 15 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: 22.0 s
22.0 sYour largest element takes 22.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Fachada de Sucursal Monterrey”.
Time to Interactive: 29.0 s
29.0 sThe page becomes fully interactive after 29.0 s. Good is under 3.8 s.
Speed Index: 12.8 s
12.8 sVisually, the page fills in at 12.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.6 s
5.6 sThe first text or image appears after 5.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
Real-user INP: 242 ms
242 msReal visitors wait 242 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 170 ms to 206 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
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: 738 ms
738 msReal visitors wait 738 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.044
0.044The layout barely moves while loading (CLS 0.044, good is under 0.1).
Images and page weight
Page weight: 9.3 MB in 161 requests
9.3 MBYour homepage downloads 9.3 MB in 161 requests on a phone: images 7.0 MB (100), scripts 1.8 MB (28) and fonts 319 KiB (4). Under 2 MB keeps phones on slow connections fast.
17 images far larger than shown
3.2 MB17 images are downloaded at several times the size a phone draws them, for example monterrey.jpg at 2,406 px wide, shown at 392 px. Resized copies would save about 3.2 MB.
2 images over 500 KB
2 images weigh 2.0 MB together. On a phone connection a single image that size takes seconds.
39 images in older formats
39 images (5.9 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.
9 images below the first screen load straight away
9 images further down the page (581 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.6 g of CO₂ per visit
2.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.65 g of CO₂e: 317.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (11 elements).
2 checks passed
Every image has alt text
All 219 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (227 characters)
Your meta description is 227 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.
No XML sitemap
No XML sitemap at https://www.surtidor.com/1_index_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.
667 internal links, 6 external
The homepage links to 667 pages on surtidor.com and 6 external pages.
3 checks passed
One H1 headline
Your main headline reads: “Todo para tus proyectos de construcción, remodelación y mantenimiento.”.
Title: 46 characters
Your title is a healthy 46 characters: “El Surtidor - Compra en línea de forma segura.”.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
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.surtidor.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 (3,220 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.surtidor.com/carrito is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
4 pages share 2 titles
/ and https://www.surtidor.com/modules/srt_filters/display all use the title “El Surtidor - Compra en línea de forma segura.”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://www.surtidor.com/carrito, https://www.surtidor.com/modules/srt_digitalinvoice/display, https://www.surtidor.com/catalogos and https://www.surtidor.com/sucursales have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.surtidor.com/modules/srt_digitalinvoice/display has 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 95 found) and read each the way a search engine does.
3 checks passed
Linked pages load
14 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.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
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.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
50 of 55 tappable elements near the top are at least 24 px.
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.
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 794 words of copy
The homepage carries about 794 words of visible text.
4 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
23 other companies contacted
Loading the homepage contacts 23 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 surtidor.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on surtidor.com, including 22 speed issues, 5 SEO issues and 2 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.