fanka.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 LCP: 2.7 s

  2.7 s

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

• Real-user INP: 328 ms

  328 ms

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

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

  +66%

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

• Real-user FCP: 2.0 s

  2.0 s

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

• Real-user TTFB: 874 ms

  874 ms

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

• Largest content (LCP) held steady for real visitors

  -7%

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

• Page weight: 8.1 MB

  8.1 MB

  Your homepage downloads 8.1 MB on a phone, 1.7 MB of it images (21%). Under 2 MB keeps phones on slow connections fast.

• 4 images below the first screen load straight away

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

  Elements (4)

• About 2.3 g of CO₂ per visit

  2.29 g

  By the Sustainable Web Design model, a visit to your homepage emits about 2.29 g of CO₂e: 274.4 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 names (1 element)

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

  Elements (1)

• Hidden but focusable

  7 elements hidden from screen readers can still receive keyboard focus.

  Elements (3)

• 1 text element with low contrast

  1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (1)

• 31 links without text

  31 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

• Headings skip levels

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

  View sourceElements (1)

• 2 H1 headlines

  There are 2 <h1> headlines (“Fanka” and “Black Friday Early Access”). One clear main headline is easier for people and search engines.

  View source

• 146 internal links, 4 external

  The homepage links to 146 pages on fanka.com and 4 external pages.

• Organization data is thin (3 of 6 facts)

  Your Organization JSON-LD is missing 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

• 10 pages without a meta description

  /collections/all, /pages/holiday-sale, /collections/new-drops, /collections/bottoms, /collections/tops and /collections/accessories and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (8)

• 14 pages without an H1

  /collections/all, /collections/shop-all, /products/body-sculpt-leggings-2-0-reversible-wear, /collections/new-drops, /collections/bottoms and /collections/tops and 8 others 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 49 found) and read each the way a search engine does.

• 9 small tap targets

  9 of 37 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 “Uncaught SyntaxError: Identifier 'STORAGE_KEY_MAI_UTM' has already been declared”.

• Short HSTS lifetime

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

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

• DNSSEC is off

  fanka.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: 26 trust badges. 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.

• A 19-field form

  Your longest form asks for 19 fields (0 required). Every extra field lowers completion.

  View source

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

  The homepage carries about 372 words of visible text.

• DMARC is monitor-only (p=none)

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

• 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: 60/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.

• 9 trackers load before any consent

  9

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

• 37 cookies set on arrival

  37

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

• 77 other companies contacted

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