bitexen.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: 564 ms

  564 ms

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

• Real-user FCP: 3.0 s

  3.0 s

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

• Real-user LCP: 4.0 s

  4.0 s

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

• Tap response (INP) held steady for real visitors

  -3%

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

• Largest content (LCP) held steady for real visitors

  -5%

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

• Page weight: 2.0 MB

  2.0 MB

  Your homepage downloads 2.0 MB on a phone, 52 KiB of it images (3%). Under 2 MB keeps phones on slow connections fast.

• 1 image in older formats

  1 image (40 KiB) is 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 (1)

• About 0.6 g of CO₂ per visit

  0.57 g

  By the Sustainable Web Design model, a visit to your homepage emits about 0.57 g of CO₂e: 68.9 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)

• 4 text elements with low contrast

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

  Elements (3)

• Zoom is disabled

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

  Elements (1)

• No H1 headline

  There is no <h1>, so neither visitors nor Google get a clear main headline.

• Title is long (70 characters)

  Your title is 70 characters, so Google will cut it off around 60: “Bitexen - Kolay, Güvenli, Hızlı Bitcoin & Altcoin Alım Satım Platformu”.

  View source

• No canonical URL

  No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

• Structured data has 1 problem

  Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.

  View source

• No robots.txt

  There is no robots.txt at bitexen.com/robots.txt, the first file search crawlers ask for.

• Only 0 internal links

  The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

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

• 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 400 ()”.

• 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 180 days; one year is the recommended minimum.

• 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" always”; 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

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

  bitexen.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 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 calls to action

  We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

• No social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

• Local business without LocalBusiness data

  Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  View source

• No phone number on the homepage

  A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

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

• Only about 68 words

  The homepage has only about 68 words of visible text; thin pages give Google and first-time buyers little to go on.

• No opening hours

  The homepage shows no opening hours. If customers visit or call, show when.

• No form on the homepage

  There is no form on the homepage, so every lead has to click through to another page first.

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

• 4 trackers load before any consent

  4

  Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Meta Pixel and Xandr (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

• 9 cookies set on arrival

  9

  Opening the homepage sets 9 cookies, 2 of them by other companies (measured from a US location before any click).

• 20 other companies contacted

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