casappa.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 TTFB: 2.4 s

  2.4 s

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

• Real-user LCP: 3.1 s

  3.1 s

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

• Real-user INP: 297 ms

  297 ms

  Real visitors wait 297 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

• Real-user FCP: 2.9 s

  2.9 s

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

• Tap response (INP) held steady for real visitors

  +1%

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

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

  +13%

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

• Page weight: 2.7 MB

  2.7 MB

  Your homepage downloads 2.7 MB on a phone, 2.4 MB of it images (90%). Under 2 MB keeps phones on slow connections fast.

• 11 images in older formats

  11 images (1.8 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.

  Elements (5)

• 2 images below the first screen load straight away

  2 images further down the page (52 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (2)

• About 0.8 g of CO₂ per visit

  0.77 g

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

• Unlabelled dropdowns

  1 dropdown has no label.

  Elements (1)

• 11 images without alt text

  11 images have no alt text, which hurts accessibility and image search.

  View sourceElements (1)

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

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

  Elements (3)

• No main landmark

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

  Elements (1)

• 2 links without text

  2 visible links have no text or label, so screen readers cannot say where they go.

  Elements (2)

• 1 form field without a label

  1 form field has no label, so screen readers announce an empty box and autofill guesses.

  View source

• No meta description

  No meta description, so Google writes its own snippet from whatever text it finds.

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

• 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.casappa.com/sitemap.xml, so Google discovers your pages only by following links.

• No robots.txt

  There is no robots.txt at casappa.com/robots.txt, the first file search crawlers ask for.

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is incomplete here.

• 74 internal links, 4 external

  The homepage links to 74 pages on casappa.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.

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

• 4 pages without a meta description

  /en/company/company-profile/about-us, /en/c/history, /en/company/company-profile/holding and /en/company/company-profile/governance have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (4)

• 2 pages slow to respond

  /en/company/company-profile/holding and /en/company/company-profile/governance took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• No mobile viewport

  No viewport meta tag, so phones render the desktop layout zoomed out.

• 11 small tap targets

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

• No Content-Security-Policy

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

• HTTP/1.1 only

  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.

• No clickjacking protection

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

• No Referrer-Policy

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

• No Permissions-Policy

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

• No security.txt

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

• No CAA record

  casappa.com 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.

• DNSSEC is off

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

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

• Thin social proof

  Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

• No analytics detected

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

• 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 277 words of copy

  The homepage carries about 277 words of visible text.

• Email authentication score: 90/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.

• 3 cookies set on arrival

  3

  Opening the homepage sets 3 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.

• 2 other companies contacted

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