Website review, no card needed
lasirena.es website review
Visit site (opens in a new tab)Reviewed 2 November 202654 issues · 96 checks
This review found 54 issues worth fixing on lasirena.es, 25 of them high impact, across 96 checks. The most urgent: reduce unused JavaScript. 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
54FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.3 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.1 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.2 s |
| Oct 31, 2026 | 3.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 346 ms |
| May 23, 2026 | 344 ms |
| May 30, 2026 | 353 ms |
| Jun 6, 2026 | 357 ms |
| Jun 13, 2026 | 364 ms |
| Jun 20, 2026 | 368 ms |
| Jun 27, 2026 | 370 ms |
| Jul 4, 2026 | 372 ms |
| Jul 11, 2026 | 371 ms |
| Jul 18, 2026 | 374 ms |
| Jul 25, 2026 | 372 ms |
| Aug 1, 2026 | 368 ms |
| Aug 8, 2026 | 367 ms |
| Aug 15, 2026 | 366 ms |
| Aug 22, 2026 | 363 ms |
| Aug 29, 2026 | 368 ms |
| Sep 5, 2026 | 365 ms |
| Sep 12, 2026 | 372 ms |
| Sep 19, 2026 | 376 ms |
| Sep 26, 2026 | 378 ms |
| Oct 3, 2026 | 383 ms |
| Oct 10, 2026 | 376 ms |
| Oct 17, 2026 | 376 ms |
| Oct 24, 2026 | 371 ms |
| Oct 31, 2026 | 363 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.9 s
1.9 s
2.8 s
3.7 s
4.7 s
5.6 s
6.6 s
7.5 s
Speed
Reduce unused JavaScript
7.2 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.2 s faster on a phone.
Use efficient cache lifetimes
1.5 s · 1.7 MB29 files are served with short cache lifetimes, so returning visitors download them again (1.7 MB).
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 27
27/100Your mobile performance score is 27. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.8 s
A phone's processor spends 5.8 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,151 HTML elements
The page has 3,151 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 (vtexassets.com, Google Tag Manager and ucontactcloud.com and others), adding 5.4 MB and 2.2 s of main-thread time.
Improve image delivery
900 ms · 499 KiB19 images could be 499 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
vtexassets.com adds 903 ms
903 msvtexassets.com costs a phone 903 ms of main-thread work and 2.3 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.
Reduce unused CSS
450 ms · 272 KiBAbout 272 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
ucontactcloud.com adds 328 ms
328 msucontactcloud.com costs a phone 328 ms of main-thread work and 1.3 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.
Google Tag Manager adds 376 ms
376 msGoogle Tag Manager costs a phone 376 ms of main-thread work and 555 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
350 ms · 65 KiBPolyfills for old browsers add 65 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.
Google CDN adds 269 ms
269 msGoogle CDN costs a phone 269 ms of main-thread work and 745 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.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 301 ms. During a long task the page ignores taps.
Render-blocking requests
200 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 200 ms.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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: 92 ms
92 msYour server sent the HTML in 92 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.
First Contentful Paint: 9.8 s
9.8 sThe first text or image appears after 9.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 26.4 s
26.4 sYour largest element takes 26.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Novedades de Navidad”.
Speed Index: 16.7 s
16.7 sVisually, the page fills in at 16.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 40.0 s
40.0 sThe page becomes fully interactive after 40.0 s. Good is under 3.8 s.
Total Blocking Time: 909 ms
909 msScripts block taps and scrolling for 909 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 493 ms
493 msReal visitors wait 493 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.21
0.21For real visitors the layout shifts by 0.21 (75th percentile). Good is under 0.1.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 864 ms
864 msReal visitors wait 864 ms for your server to start answering (75th percentile). Good is under 800 ms.
31 images without width and height
31 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.164
0.164The layout shifts by 0.164 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 346 ms to 363 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 6.9 MB in 188 requests
6.9 MBYour homepage downloads 6.9 MB in 188 requests on a phone: scripts 3.6 MB (66), fonts 1.2 MB (7) and other files 774 KiB (62). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
popup-descarga-app___352fb025dd4062ffac1efd8942f77b4d.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).
2 images in older formats
2 images (132 KiB) 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.
2 images below the first screen load straight away
2 images further down the page (109 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.9 g of CO₂ per visit
1.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.95 g of CO₂e: 233.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
59 tap targets too small
59 tap targets are too small or too close together to hit reliably with a finger.
20 text elements with low contrast
20 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (6 elements)
Interactive controls must not be nested: 6 elements on the page fail this check, rated serious by axe-core.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 10 failed. 5 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.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Structured data has 1 problem
Structured data found (ItemList, Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
380 internal links, 9 external
The homepage links to 380 pages on lasirena.es and 9 external pages.
4 checks passed
Title: 45 characters
Your title is a healthy 45 characters: “La Sirena - Compra congelados al mejor precio”.
Canonical URL set
The canonical URL is https://www.lasirena.es/es/.
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.lasirena.es/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.lasirena.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.
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (904 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
https://www.lasirena.es/es/descarga-la-app-de-la-sirena is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://www.lasirena.es/es/tiendas, https://www.lasirena.es/es/folletos and https://www.lasirena.es/es/la-sirena-club have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.lasirena.es/es/tiendas, https://www.lasirena.es/es/la-sirena-club, https://www.lasirena.es/es/faq, https://www.lasirena.es/es/descarga-la-app-de-la-sirena and https://www.lasirena.es/es/categorias have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages slow to respond
https://www.lasirena.es/es/folletos, https://www.lasirena.es/es/la-sirena-club, https://www.lasirena.es/es/descarga-la-app-de-la-sirena, https://www.lasirena.es/es/categorias, https://www.lasirena.es/es/pescado and https://www.lasirena.es/es/marisco and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 196 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
9 broken images
9 images failed to load on a phone, for example https://bat.bing.net/action/0?ti=138003225&tm=gtm002&Ver=2&mid=69b7e2d1-cd2a-4f4c-8a87-e3a21c8744df&bo=3&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=La%20Sirena%20-%20Compra%20congelados%20al%2.
55 small tap targets
55 of 112 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'register')”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
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 291 words of copy
The homepage carries about 291 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
Social proof on the page
Social proof on the homepage: 29 testimonial or review blocks and 2 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Meta Pixel and 4 mores (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.
18 cookies set on arrival
18Opening the homepage sets 18 cookies (measured from a US location before any click).
44 other companies contacted
Loading the homepage contacts 44 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 lasirena.es, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- CloudFront
Company
- Employees
- 1,200
- Founded
- 1983
- Headquarters
- Viladecavalls
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on lasirena.es, including 28 speed issues, 4 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.