Website review, no card needed
cajasiete.com website review
Visit site (opens in a new tab)Reviewed 29 October 202652 issues · 92 checks
This review found 52 issues worth fixing on cajasiete.com, 22 of them high impact, across 92 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 6.3 s |
| May 16, 2026 | 6.4 s |
| May 23, 2026 | 6.5 s |
| May 30, 2026 | 6.4 s |
| Jun 6, 2026 | 6.2 s |
| Jun 13, 2026 | 5.9 s |
| Jun 20, 2026 | 5.4 s |
| Jun 27, 2026 | 5.2 s |
| Jul 4, 2026 | 5.2 s |
| Jul 11, 2026 | 5.4 s |
| Jul 18, 2026 | 5.4 s |
| Jul 25, 2026 | 5.6 s |
| Aug 1, 2026 | 5.7 s |
| Aug 8, 2026 | 5.1 s |
| Aug 15, 2026 | 5.6 s |
| Aug 22, 2026 | 5.8 s |
| Aug 29, 2026 | 5.8 s |
| Sep 5, 2026 | 6.2 s |
| Sep 12, 2026 | 6.1 s |
| Sep 19, 2026 | 6.1 s |
| Sep 26, 2026 | 6.1 s |
| Oct 3, 2026 | 6.0 s |
| Oct 10, 2026 | 6.1 s |
| Oct 17, 2026 | 6.0 s |
| Oct 24, 2026 | 6.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 222 ms |
| May 16, 2026 | 217 ms |
| May 23, 2026 | 212 ms |
| May 30, 2026 | 210 ms |
| Jun 6, 2026 | 207 ms |
| Jun 13, 2026 | 207 ms |
| Jun 20, 2026 | 212 ms |
| Jun 27, 2026 | 219 ms |
| Jul 4, 2026 | 222 ms |
| Jul 11, 2026 | 227 ms |
| Jul 18, 2026 | 225 ms |
| Jul 25, 2026 | 220 ms |
| Aug 1, 2026 | 218 ms |
| Aug 8, 2026 | 217 ms |
| Aug 15, 2026 | 216 ms |
| Aug 22, 2026 | 220 ms |
| Aug 29, 2026 | 223 ms |
| Sep 5, 2026 | 223 ms |
| Sep 12, 2026 | 227 ms |
| Sep 19, 2026 | 224 ms |
| Sep 26, 2026 | 221 ms |
| Oct 3, 2026 | 223 ms |
| Oct 10, 2026 | 221 ms |
| Oct 17, 2026 | 220 ms |
| Oct 24, 2026 | 220 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.1 s
1.7 s
2.2 s
2.8 s
3.4 s
3.9 s
4.5 s
Speed
Improve image delivery
24.9 s · 5.4 MB21 images could be 5.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 24.9 s faster on a phone.
Render-blocking requests
5.7 s74 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.7 s.
Use efficient cache lifetimes
3.1 s · 893 KiB152 files are served with short cache lifetimes, so returning visitors download them again (893 KiB).
Reduce unused CSS
1.9 s · 371 KiBAbout 371 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Cookiebot and FontAwesome CDN and others), adding 1.4 MB and 957 ms of main-thread time.
Google Tag Manager adds 723 ms
723 msGoogle Tag Manager costs a phone 723 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 430 ms. During a long task the page ignores taps.
Main-thread work: 3.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify CSS
300 ms · 43 KiB43 KiB could be saved by minifying CSS.
Cookiebot adds 234 ms
234 msCookiebot costs a phone 234 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.
Minify JavaScript
150 ms · 8 KiB8 KiB could be saved by minifying JavaScript.
Reduce unused JavaScript
155 KiBAbout 155 KiB of JavaScript is downloaded but never used on this page.
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.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 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: 30.7 s
30.7 sYour largest element takes 30.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Acceso cliente”.
Time to Interactive: 39.3 s
39.3 sThe page becomes fully interactive after 39.3 s. Good is under 3.8 s.
Speed Index: 12.6 s
12.6 sVisually, the page fills in at 12.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.3 s
5.3 sThe first text or image appears after 5.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 663 ms
663 msScripts block taps and scrolling for 663 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: 238 ms
238 msReal visitors wait 238 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
4 images without width and height
4 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 222 ms to 220 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 6.3 s to 6.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.049
0.049The layout barely moves while loading (CLS 0.049, good is under 0.1).
Images and page weight
Page weight: 8.2 MB in 175 requests
8.2 MBYour homepage downloads 8.2 MB in 175 requests on a phone: images 5.8 MB (28), scripts 1.5 MB (52) and stylesheets 480 KiB (77). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 4.4 MB together. On a phone connection a single image that size takes seconds.
9 images far larger than shown
3.3 MB9 images are downloaded at several times the size a phone draws them, for example cabecera-baloncesto.png at 1,920 px wide, shown at 390 px. Resized copies would save about 3.3 MB.
15 images in older formats
15 images (5.4 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.
1 image below the first screen load straight away
1 image further down the page (48 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.3 g of CO₂ per visit
2.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.32 g of CO₂e: 278.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
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.
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.
Contentinfo landmark should not be contained in another landmark (2 elements)
Contentinfo landmark should not be contained in another landmark: 2 elements on the page fail this check, rated moderate by axe-core.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (13 elements)
Alternative text of images should not be repeated as text: 13 elements on the page fail this check, rated minor by axe-core.
1 checks passed
48 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: 48 passed and 12 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
210 internal links, 20 external
The homepage links to 210 pages on cajasiete.com and 20 external pages.
6 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “Somos Cajasiete, una cooperativa de crédito comprometida con las personas, las empresas y el desarrollo de Canarias. De…”.
Title: 64 characters
Your title is a healthy 64 characters: “Cajasiete | Cuentas, hipotecas y servicios bancarios en Canarias”.
Canonical URL set
The canonical URL is https://www.cajasiete.com/.
Structured data in place
Structured data found: Organization.
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.cajasiete.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), 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.
No llms.txt
There is no https://www.cajasiete.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 (1,209 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without a meta description
https://www.cajasiete.com/citaprevia, https://www.cajasiete.com/hazte-cliente, https://www.cajasiete.com/particulares, https://www.cajasiete.com/hazte-cliente-gen8 and https://www.cajasiete.com/particulares/cuenta-online-canarias/cuenta-pago-basica have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.cajasiete.com/hazte-cliente, https://www.cajasiete.com/enplanfacil/menudos and https://www.cajasiete.com/hazte-cliente-gen8 have no <h1> headline, so visitors and search engines get no clear main topic.
5 pages slow to respond
https://www.cajasiete.com/enplanfacil/senior, https://www.cajasiete.com/particulares/cuenta-online-canarias/cuenta-esiete, https://www.cajasiete.com/particulares/cuenta-online-canarias/cuenta-pago-basica, https://www.cajasiete.com/particulares/traslado-cuentas and https://www.cajasiete.com/particulares/tarjeta-platinum-cajasiete took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 158 found) and read each the way a search engine does.
5 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.
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 14 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 31 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'getRegistration') https://www.cajasiete.com/:3:6759”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 737 words of copy
The homepage carries about 737 words of visible text.
2 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
15 cookies set on arrival
15Opening the homepage sets 15 cookies (measured from a US location before any click).
8 other companies contacted
Loading the homepage contacts 8 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 cajasiete.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Drupal
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Radware
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on cajasiete.com, including 22 speed issues, 4 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.