geni.com website review

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

Your mobile performance score is 69 (desktop: 94). Pages that score under 90 lose visitors before the first paint.

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

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.

About 295 KiB of JavaScript is downloaded but never used on this page.

The page has 1,648 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

2 third-party services load with your homepage (Facebook and Google Fonts), adding 134 KiB and 40 ms of main-thread time.

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

Desktop scores 94 but mobile only 69. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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.

Your largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Join Geni for Free! Continue using Google Continue using Ap…”.

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

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

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

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

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

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

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

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

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

6 images (516 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.

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

1 image is downloaded at several times the size a phone draws it, for example trustpilot-logo.png at 3,233 px wide, shown at 192 px. Resized copies would save about 56 KiB.

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

4 elements have a tabindex above 0, which scrambles the keyboard order.

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

All page content should be contained by landmarks: 47 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.

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

5 form fields have no label, so screen readers announce an empty box and autofill guesses.

Table header text should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 5 <h1> headlines (“Join Geni for Free!”, “Try Geni Pro for Free!” and “Log in to Geni”). One clear main headline is easier for people and search engines.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 132 pages on geni.com and 7 external pages.

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.

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.

/people, /projects, /people/Idwal-Foel-ab-Anarawd/6000000002906954937, /people/Charlemagne/6000000002457013227, /people/Felipe-VI/6000000013239216812 and /people/Matt-Damon/6000000007004866701 and 5 others have no <title>, so Google invents the link text in results.

/people, /projects, /people/Idwal-Foel-ab-Anarawd/6000000002906954937, /people/Charlemagne/6000000002457013227, /people/Felipe-VI/6000000013239216812 and /people/Matt-Damon/6000000007004866701 and 5 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/people, /projects, /people/Idwal-Foel-ab-Anarawd/6000000002906954937, /people/Charlemagne/6000000002457013227, /people/Felipe-VI/6000000013239216812 and /people/Matt-Damon/6000000007004866701 and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

/people, /projects, /people/Idwal-Foel-ab-Anarawd/6000000002906954937, /people/Charlemagne/6000000002457013227, /people/Felipe-VI/6000000013239216812 and /people/Matt-Damon/6000000007004866701 and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“document.createEvent('TransitionEvent') is deprecated and will be removed. Use `new TransitionEvent…”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 link to other sites is dead, for example https://bsky.app/profile/geni.com (404).

10 links go through two or more redirects, for example https://www.geni.com/tr8n/language/switch?language_action=switch_language&locale=af.

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.

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

geni.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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 1,506 words of visible text.

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.

Before a visitor clicks anything, the page loads Meta Pixel (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 4 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 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.