fortunateone.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 INP: 223 ms

  223 ms

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

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

  +37%

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

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

  +38%

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

• Page weight: 5.7 MB

  5.7 MB

  Your homepage downloads 5.7 MB on a phone, 1.4 MB of it images (24%). Under 2 MB keeps phones on slow connections fast.

• 3 images in older formats

  3 images (251 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.

  Elements (3)

• 3 images below the first screen load straight away

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

  Elements (3)

• About 1.6 g of CO₂ per visit

  1.61 g

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

• Scrollable region must have keyboard access (32 elements)

  Scrollable region must have keyboard access: 32 elements on the page fail this check, rated serious by axe-core.

  Elements (3)

• 6 text elements with low contrast

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

  Elements (3)

• Interactive controls must not be nested (5 elements)

  Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.

  Elements (3)

• 2 tap targets too small

  2 tap targets are too small or too close together to hit reliably with a finger.

  Elements (2)

• 14 images without alt text

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

  View sourceElements (3)

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

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

  Elements (3)

• Contentinfo landmark should not be contained in another landmark (1 element)

  Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

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

  Elements (1)

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

• Zoom is disabled

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

  Elements (1)

• 4 links without text

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

  Elements (3)

• 3 form fields without a label

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

  View source

• Headings skip levels

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

  View sourceElements (1)

• No meta description

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

• 2 H1 headlines

  There are 2 <h1> headlines (“Fortunate One US” and “Fortunate One US”). One clear main headline is easier for people and search engines.

  View source

• No social preview image

  No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  View source

• 586 internal links, 13 external

  The homepage links to 586 pages on fortunateone.com and 13 external pages.

• 15 internal pages checked

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

• 30 small tap targets

  30 of 115 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 “Failed to load resource: the server responded with a status of 429 ()”.

• Short HSTS lifetime

  HSTS is set, but max-age is 91 days; one year is the recommended minimum.

• 1 link through redirect chains

  1 link go through two or more redirects, for example https://instagram.com/fortunateone/.

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

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

• No security.txt

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

• No CAA record

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

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

• Thin social proof

  Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

• About 658 words of copy

  The homepage carries about 658 words of visible text.

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

• 5 trackers load before any consent

  5

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Clarity (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.

• 16 cookies set on arrival

  16

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

• 42 other companies contacted

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