fortcore.us 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 CLS: 0.12

  0.12

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

• Tap response (INP) held steady for real visitors

  +3%

  Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 110 ms to 112 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 1.5 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Page weight: 4.3 MB

  4.3 MB

  Your homepage downloads 4.3 MB on a phone, 639 KiB of it images (14%). Under 2 MB keeps phones on slow connections fast.

• 5 images far larger than shown

  231 KiB

  5 images are downloaded at several times the size a phone draws them, for example b_f1.avif at 820 px wide, shown at 152 px. Resized copies would save about 231 KiB.

  Elements (5)

• 5 images below the first screen load straight away

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

  Elements (5)

• About 1.2 g of CO₂ per visit

  1.23 g

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

• ARIA attributes must conform to valid values (1 element)

  ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• 33 text elements with low contrast

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

  Elements (3)

• Elements must only use permitted ARIA attributes (13 elements)

  Elements must only use permitted ARIA attributes: 13 elements on the page fail this check, rated serious by axe-core.

  Elements (3)

• 10 tap targets too small

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

  Elements (3)

• ARIA commands must have an accessible name (8 elements)

  ARIA commands must have an accessible name: 8 elements on the page fail this check, rated serious by axe-core.

  Elements (3)

• 30 images without alt text

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

  View sourceElements (3)

• 4 links without text

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

  Elements (3)

• Elements marked as presentational should be consistently ignored (13 elements)

  Elements marked as presentational should be consistently ignored: 13 elements on the page fail this check, rated minor by axe-core.

  Elements (3)

• ARIA role should be appropriate for the element (8 elements)

  ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

  Elements (3)

• Alternative text of images should not be repeated as text (1 element)

  Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

  Elements (1)

• Headings skip levels

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

  View source

• 50 internal links, 7 external

  The homepage links to 50 pages on fortcore.us and 7 external pages.

• 1 linked page is broken

  Your homepage links to /products/digestive-bundle, which answers with an error. Visitors hit a dead end and search engines drop it.

  Elements (1)

• 1 linked page hidden from search

  /products/gentest is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  Elements (1)

• 3 pages without a meta description

  /pages/contact, /products/nmn-60ct and /collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (3)

• 2 pages without an H1

  /pages/contact and /pages/quiz have no <h1> headline, so visitors and search engines get no clear main topic.

• 15 internal pages checked

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

• 9 small tap targets

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

• 5 JavaScript errors while loading

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

• 1 broken link to your own pages

  1 link from your homepage to your own site is broken, for example https://fortcore.us/products/digestive-bundle (404).

• 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://fortcore.us/customer_authentication/redirect?locale=en&region_country=US.

• 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

  fortcore.us 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.

• 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 direct contact details

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

• About 811 words of copy

  The homepage carries about 811 words of visible text.

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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

• 7 trackers load before any consent

  7

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

• 25 cookies set on arrival

  25

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

• 49 other companies contacted

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