epify.co website review

Not measured in this review.

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

  +13%

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

• Largest content (LCP) held steady for real visitors

  -2%

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

• Page weight: 4.2 MB

  4.2 MB

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

• 6 images far larger than shown

  721 KiB

  6 images are downloaded at several times the size a phone draws them, for example Anti_Selulit_New_Shopify.webp at 1,080 px wide, shown at 121 px. Resized copies would save about 721 KiB.

  Elements (5)

• 3 images in older formats

  3 images (714 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)

• 6 images below the first screen load straight away

  6 images further down the page (181 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.18 g

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

• 403 images without alt text

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

  View sourceElements (3)

• 28 text elements with low contrast

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

  Elements (3)

• 7 tap targets too small

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

  Elements (3)

• Hidden but focusable

  1 element hidden from screen readers can still receive keyboard focus.

  Elements (1)

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

• 2 links without text

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

  Elements (2)

• Headings skip levels

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

  View sourceElements (2)

• No meta description

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

• Title is short (5 characters)

  Your title is only 5 characters: “epify”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• Structured data has 1 problem

  Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("#")”.

  View source

• No social preview image

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

  View source

• No favicon declared

  No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

• One H1 headline

  Your <h1> is empty.

  View source

• 134 internal links, 6 external

  The homepage links to 134 pages on epify.co and 6 external pages.

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

• 5 pages without a meta description

  /collections/best-seller, /collections/tum-urunler, /collections/en-cok-satan-bakim-setleri, /pages/contact and /pages/hediyeni-ve-indirimini-sec have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (5)

• 4 pages without an H1

  /collections/best-seller, /collections/tum-urunler, /collections/en-cok-satan-bakim-setleri and /pages/contact 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 32 found) and read each the way a search engine does.

• 4 JavaScript errors while loading

  4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'classList')”.

• 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://epify.co/customer_authentication/redirect?locale=tr&region_country=TR.

• 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

  epify.co 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.

• 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 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 2,131 words of copy

  The homepage carries about 2,131 words of visible text.

• DMARC is monitor-only (p=none)

  DMARC is set to p=none, so mail pretending to be epify.co is still delivered. Add a report address, check the reports, then move to quarantine.

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

• 6 trackers load before any consent

  6

  Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity and 1 more (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, 1 of them by other companies (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.

• 24 other companies contacted

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