fsc.org 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: 3.7 s

  3.7 s

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

• Real-user FCP: 2.7 s

  2.7 s

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

• Real-user TTFB: 1.2 s

  1.2 s

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

• Tap response (INP) held steady for real visitors

  0%

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

• Largest content (LCP) held steady for real visitors

  -4%

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

• Page weight: 10.5 MB

  10.5 MB

  Your homepage downloads 10.5 MB on a phone, 9.5 MB of it images (91%). Under 2 MB keeps phones on slow connections fast.

• 4 images over 500 KB

  4 images weigh 6.2 MB together. On a phone connection a single image that size takes seconds.

  Elements (4)

• 37 images in older formats

  37 images (9.0 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)

• 4 images below the first screen load straight away

  4 images further down the page (5.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  Elements (4)

• 4 images far larger than shown

  284 KiB

  4 images are downloaded at several times the size a phone draws them, for example FSC_Lithuania_Bees-4060.JPG at 1,148 px wide, shown at 374 px. Resized copies would save about 284 KiB.

  Elements (4)

• About 3.0 g of CO₂ per visit

  2.97 g

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

• 1 button without a name

  1 button has no accessible name, so screen readers announce just “button”.

  Elements (1)

• 7 text elements with low contrast

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

  Elements (3)

• 4 tap targets too small

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

  Elements (3)

• All page content should be contained by landmarks (1 element)

  All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  Elements (1)

• 5 form fields without a label

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

• Headings skip levels

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

  View source

• 3 H1 headlines

  There are 3 <h1> headlines (“Back from extinction: the ‘underdog’ forest honey…”, “The knowledge keepers” and “The last candelilleros”). One clear main headline is easier for people and search engines.

• Meta description is long (221 characters)

  Your meta description is 221 characters; Google truncates after about 160, so the end of your pitch is cut.

  View source

• Structured data has 1 problem

  Structured data found (Organization and WebPage) but with 1 problem, for example “WebPage: breadcrumb is an empty list”.

  View source

• No X (Twitter) card tag

  No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

• 529 internal links, 88 external

  The homepage links to 529 pages on fsc.org and 88 external pages.

• Organization data is thin (1 of 6 facts)

  Your Organization JSON-LD is missing url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  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.

• 11 pages without a meta description

  /en/about-us, /en/our-history, /en/our-values, /en/leadership, /en/board-of-directors and /en/fsc-policy-and-standards-committee and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (8)

• 15 internal pages checked

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

• 5 small tap targets

  5 of 22 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.

• Short HSTS lifetime

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

• 2 links through redirect chains

  2 links go through two or more redirects, for example https://consultation-platform.fsc.org/.

• 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

  fsc.org 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

  fsc.org'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 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 685 words of copy

  The homepage carries about 685 words of visible text.

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be fsc.org is still delivered. Reports are on, so moving to quarantine is the next step.

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

• 6 other companies contacted

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