financecrowd.tech website review

20 files are served with short cache lifetimes, so returning visitors download them again (717 KiB).

4 images could be 235 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.

Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.

About 175 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 750 ms).

About 14 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

2 third-party services load with your homepage (Google Maps and Google Fonts), adding 406 KiB and 83 ms of main-thread time.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SOFTWARE PARA PLATAFORMAS DE CROWD La solución más económic…”.

The page becomes fully interactive after 7.0 s. Good is under 3.8 s.

Visually, the page fills in at 4.9 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 1.9 s on a phone. Good is under 1.8 s.

1 image have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 image is downloaded at several times the size a phone draws it, for example Logo-Finance-Crowd-2B.png at 3,625 px wide, shown at 156 px. Resized copies would save about 175 KiB.

2 images (248 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.

1 image further down the page (70 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 0.30 g of CO₂e: 35.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

39 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 21 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (h2 → h4 and h3 → h5), which makes the page harder to scan with a screen reader.

There is no <h1>, so neither visitors nor Google get a clear main headline.

The homepage links to 17 pages on financecrowd.tech and 0 external pages.

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.

There is no /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.

Your homepage links to /contacto-fintech-app, which answers with an error. Visitors hit a dead end and search engines drop it.

/crowdlending-app-software-prestamos and /crowdlending-app-software-crowdlending all use the title “Crowdlending App: Software de Gestión de Préstamos Participativos”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/tarifas and /contacto have no meta description, so Google writes the search snippet from whatever text it finds.

/crowdlending-app-software-prestamos and /crowdlending-app-software-crowdlending use the same meta description. A description written for each page earns more clicks.

Your homepage links to 3 pages by a URL that isn't their canonical one, for example /crowdlending-app-software-crowdlending, whose canonical is /crowdlending-app-software-prestamos. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/crowdlending-app-software-prestamos, /crowdfunding-inmobiliario-software, /tarifas, /contacto, /crowdlending-app-software-crowdlending and /crowdfunding-inmobiliario-inversion-inmuebles and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

/crowdlending-app-software-crowdlending, /crowdfunding-inmobiliario-inversion-inmuebles and /crowdfunding-inmobiliario-software-inversion-inmuebles took over 3 s to send their HTML from our server.

We fetched 8 pages linked from your homepage and read each the way a search engine does.

2 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

Chrome logged issues while loading the page (“Mixed content”).

1 resource load over plain http on your https page (for example http://www.financecrowd.tech/wp-content/uploads/2023/09/Logo-Finance-Crowd-2B.png); browsers block or warn about them.

1 link from your homepage to your own site is broken, for example https://www.financecrowd.tech/contacto-fintech-app/ (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

financecrowd.tech has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

financecrowd.tech's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 555 words of visible text.

DMARC is set to p=none, so mail pretending to be financecrowd.tech is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Opening the homepage sets 6 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.