gestisoft.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user LCP: 5.0 s

  5.0 s

  Real visitors wait 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

• Real-user FCP: 4.9 s

  4.9 s

  Real visitors see the first content after 4.9 s (75th percentile). Good is under 1.8 s.

• Real-user CLS: 0.24

  0.24

  For real visitors the layout shifts by 0.24 (75th percentile). Good is under 0.1.

• Largest content (LCP) got 29% slower for real visitors

  +29%

  Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.2 s to 5.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Real-user TTFB: 834 ms

  834 ms

  Real visitors wait 834 ms for your server to start answering (75th percentile). Good is under 800 ms.

• Tap response (INP) got 10% slower for real visitors

  +10%

  Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 117 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• 2 images far larger than shown

  434 KiB

  2 images are downloaded at several times the size a phone draws them, for example magician.webp at 1,337 px wide, shown at 148 px. Resized copies would save about 434 KiB.

  Elements (2)

• About 0.4 g of CO₂ per visit

  0.36 g

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

• 15 text elements with low contrast

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

  Elements (3)

• All page content should be contained by landmarks (2 elements)

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

  Elements (2)

• 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 (1)

• 70 internal links, 4 external

  The homepage links to 70 pages on gestisoft.com and 4 external pages.

• 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.

  View source

• No llms.txt

  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.

• 2 pages share a title

  /en/blog/topic/erp and /en/blog/topic/regulatory-bodies all use the title “CRM, ERP and Business Software Solutions Blog | Gestisoft”. Search engines can't tell which page to show for a search, so each competes with the others.

  Elements (2)

• 2 pages share a meta description

  /en/blog/topic/erp and /en/blog/topic/regulatory-bodies use the same meta description. A description written for each page earns more clicks.

• 2 links to non-canonical URLs

  Your homepage links to 2 pages by a URL that isn't their canonical one, for example /en/blog/topic/erp, whose canonical is /en/blog. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  Elements (2)

• 15 internal pages checked

  We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.

• 6 small tap targets

  6 of 17 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 'register')”.

• 2 redirects before the homepage

  Opening https://gestisoft.com goes through 2 redirects before the homepage loads.

• No Permissions-Policy

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

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• DNSSEC is off

  gestisoft.com'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.

• Phone number is not tap-to-call

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

• 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 1,875 words of copy

  The homepage carries about 1,875 words of visible text.

• Email authentication score: 100/100

  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.

• 6 trackers load before any consent

  6

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

• 6 cookies set on arrival

  6

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

• 19 other companies contacted

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